The best Hacker News stories from Show from the past day

from

All Show

from the past*

day week month

with these search terms:

Create follow Go back

Latest posts:

Show HN: C++ Compiler Support Page

Hi HN,<p>I have created a webpage that displays all C++ features since C++20 in a simple, searchable table.<p>It is intended to serve as a quick reference for C++ developers, whether as support for cross-platform development or simply to track the current support status out of curiosity.<p>I created it as a simpler, more structured, and more up-to-date alternative to the cppreference compiler support site. Please note that the page intentionally does not list LWG and CWG papers. This might change as I am continually updating the site and trying out new ideas.<p>Questions, feedback and suggestions are appreciated, either here or in the form of GitHub issues.

Show HN: C++ Compiler Support Page

Hi HN,<p>I have created a webpage that displays all C++ features since C++20 in a simple, searchable table.<p>It is intended to serve as a quick reference for C++ developers, whether as support for cross-platform development or simply to track the current support status out of curiosity.<p>I created it as a simpler, more structured, and more up-to-date alternative to the cppreference compiler support site. Please note that the page intentionally does not list LWG and CWG papers. This might change as I am continually updating the site and trying out new ideas.<p>Questions, feedback and suggestions are appreciated, either here or in the form of GitHub issues.

Show HN: I made a generative online drum machine with ClojureScript

After two years of development, I'm super excited to release Beat Maker! This is my take on what I hope is the best free, web-based drum machine.<p>My goal was to build something that was not only fun and easy to use for beginners but also powerful enough for serious producers. I did extensive research on existing drum machines, analyzed their UX, and tried to build something that adds something new.<p>It's a nearly 100% client-side app, written in ClojureScript, and is a PWA so you can install it to your home screen for an app-like experience.<p>Besides the standard grid editor, Beat Maker has some unique features that I think HN readers might find interesting:<p>- Procedural sample generation. One annoying thing about writing beats is searching through folders full of samples. I wanted to improve this and so I added the ability to generate new samples with a single click, giving you an infinite supply of unique drum samples. * Generative beat creation. If you're looking for inspiration, Beat Maker can generate entire patterns for you as a starting point. You can then edit and tweak the beat to your liking. Great for solving the "blank canvas" problem and giving you something good to start from. * Advanced export options. This is where it really shines for producers. You can export your work as: * A standard WAV loop * Individual stems (ZIP) * A MIDI file * A ZIP file of all your samples as WAVs * A SoundFont (.sf2) drum kit from your generated samples * An Impulse Tracker (.it) file for use in trackers like Renoise, OpenMPT or a Polyend * Pocket Operator/Volca sync. It can output a sync signal on the left audio channel to sync with these hardware devices for perfect timing. * Per-Note FX. You can add effects like volume slides, repeats, and start volume changes to individual notes for more complex drum phrases incorporating flam and roll.<p>As an old school tracker guy, I'm particularly excited about the Impulse Tracker export mode. I was surprised to discover how many DAWs (including hardware like Polyend) can import this format. Of course, you can also pull up Impulse Tracker on DOSBox, or the more modern re-implementation, Schismtracker for that retro experience.<p>By the way, the beat generator feature is not trained on any artists or anything like that. It's an algorithm I built from scratch myself.<p>The audio engine is built on a declarative audio graph (using `virtual-audio-graph`), inspired by React's virtual DOM, which makes managing the Web Audio API much cleaner. If you're building web based audio apps I highly recommend checking out this library.<p>I'd love for you to try it out and let me know what you think. Feedback (and the inevitable bug reports) most welcome! Thank you!<p>P.S. Also, here's a video summary: <a href="https://youtu.be/qVmEn9z3H24" rel="nofollow">https://youtu.be/qVmEn9z3H24</a>

Show HN: I made a generative online drum machine with ClojureScript

After two years of development, I'm super excited to release Beat Maker! This is my take on what I hope is the best free, web-based drum machine.<p>My goal was to build something that was not only fun and easy to use for beginners but also powerful enough for serious producers. I did extensive research on existing drum machines, analyzed their UX, and tried to build something that adds something new.<p>It's a nearly 100% client-side app, written in ClojureScript, and is a PWA so you can install it to your home screen for an app-like experience.<p>Besides the standard grid editor, Beat Maker has some unique features that I think HN readers might find interesting:<p>- Procedural sample generation. One annoying thing about writing beats is searching through folders full of samples. I wanted to improve this and so I added the ability to generate new samples with a single click, giving you an infinite supply of unique drum samples. * Generative beat creation. If you're looking for inspiration, Beat Maker can generate entire patterns for you as a starting point. You can then edit and tweak the beat to your liking. Great for solving the "blank canvas" problem and giving you something good to start from. * Advanced export options. This is where it really shines for producers. You can export your work as: * A standard WAV loop * Individual stems (ZIP) * A MIDI file * A ZIP file of all your samples as WAVs * A SoundFont (.sf2) drum kit from your generated samples * An Impulse Tracker (.it) file for use in trackers like Renoise, OpenMPT or a Polyend * Pocket Operator/Volca sync. It can output a sync signal on the left audio channel to sync with these hardware devices for perfect timing. * Per-Note FX. You can add effects like volume slides, repeats, and start volume changes to individual notes for more complex drum phrases incorporating flam and roll.<p>As an old school tracker guy, I'm particularly excited about the Impulse Tracker export mode. I was surprised to discover how many DAWs (including hardware like Polyend) can import this format. Of course, you can also pull up Impulse Tracker on DOSBox, or the more modern re-implementation, Schismtracker for that retro experience.<p>By the way, the beat generator feature is not trained on any artists or anything like that. It's an algorithm I built from scratch myself.<p>The audio engine is built on a declarative audio graph (using `virtual-audio-graph`), inspired by React's virtual DOM, which makes managing the Web Audio API much cleaner. If you're building web based audio apps I highly recommend checking out this library.<p>I'd love for you to try it out and let me know what you think. Feedback (and the inevitable bug reports) most welcome! Thank you!<p>P.S. Also, here's a video summary: <a href="https://youtu.be/qVmEn9z3H24" rel="nofollow">https://youtu.be/qVmEn9z3H24</a>

Show HN: I made a generative online drum machine with ClojureScript

After two years of development, I'm super excited to release Beat Maker! This is my take on what I hope is the best free, web-based drum machine.<p>My goal was to build something that was not only fun and easy to use for beginners but also powerful enough for serious producers. I did extensive research on existing drum machines, analyzed their UX, and tried to build something that adds something new.<p>It's a nearly 100% client-side app, written in ClojureScript, and is a PWA so you can install it to your home screen for an app-like experience.<p>Besides the standard grid editor, Beat Maker has some unique features that I think HN readers might find interesting:<p>- Procedural sample generation. One annoying thing about writing beats is searching through folders full of samples. I wanted to improve this and so I added the ability to generate new samples with a single click, giving you an infinite supply of unique drum samples. * Generative beat creation. If you're looking for inspiration, Beat Maker can generate entire patterns for you as a starting point. You can then edit and tweak the beat to your liking. Great for solving the "blank canvas" problem and giving you something good to start from. * Advanced export options. This is where it really shines for producers. You can export your work as: * A standard WAV loop * Individual stems (ZIP) * A MIDI file * A ZIP file of all your samples as WAVs * A SoundFont (.sf2) drum kit from your generated samples * An Impulse Tracker (.it) file for use in trackers like Renoise, OpenMPT or a Polyend * Pocket Operator/Volca sync. It can output a sync signal on the left audio channel to sync with these hardware devices for perfect timing. * Per-Note FX. You can add effects like volume slides, repeats, and start volume changes to individual notes for more complex drum phrases incorporating flam and roll.<p>As an old school tracker guy, I'm particularly excited about the Impulse Tracker export mode. I was surprised to discover how many DAWs (including hardware like Polyend) can import this format. Of course, you can also pull up Impulse Tracker on DOSBox, or the more modern re-implementation, Schismtracker for that retro experience.<p>By the way, the beat generator feature is not trained on any artists or anything like that. It's an algorithm I built from scratch myself.<p>The audio engine is built on a declarative audio graph (using `virtual-audio-graph`), inspired by React's virtual DOM, which makes managing the Web Audio API much cleaner. If you're building web based audio apps I highly recommend checking out this library.<p>I'd love for you to try it out and let me know what you think. Feedback (and the inevitable bug reports) most welcome! Thank you!<p>P.S. Also, here's a video summary: <a href="https://youtu.be/qVmEn9z3H24" rel="nofollow">https://youtu.be/qVmEn9z3H24</a>

Show HN: I made a generative online drum machine with ClojureScript

After two years of development, I'm super excited to release Beat Maker! This is my take on what I hope is the best free, web-based drum machine.<p>My goal was to build something that was not only fun and easy to use for beginners but also powerful enough for serious producers. I did extensive research on existing drum machines, analyzed their UX, and tried to build something that adds something new.<p>It's a nearly 100% client-side app, written in ClojureScript, and is a PWA so you can install it to your home screen for an app-like experience.<p>Besides the standard grid editor, Beat Maker has some unique features that I think HN readers might find interesting:<p>- Procedural sample generation. One annoying thing about writing beats is searching through folders full of samples. I wanted to improve this and so I added the ability to generate new samples with a single click, giving you an infinite supply of unique drum samples. * Generative beat creation. If you're looking for inspiration, Beat Maker can generate entire patterns for you as a starting point. You can then edit and tweak the beat to your liking. Great for solving the "blank canvas" problem and giving you something good to start from. * Advanced export options. This is where it really shines for producers. You can export your work as: * A standard WAV loop * Individual stems (ZIP) * A MIDI file * A ZIP file of all your samples as WAVs * A SoundFont (.sf2) drum kit from your generated samples * An Impulse Tracker (.it) file for use in trackers like Renoise, OpenMPT or a Polyend * Pocket Operator/Volca sync. It can output a sync signal on the left audio channel to sync with these hardware devices for perfect timing. * Per-Note FX. You can add effects like volume slides, repeats, and start volume changes to individual notes for more complex drum phrases incorporating flam and roll.<p>As an old school tracker guy, I'm particularly excited about the Impulse Tracker export mode. I was surprised to discover how many DAWs (including hardware like Polyend) can import this format. Of course, you can also pull up Impulse Tracker on DOSBox, or the more modern re-implementation, Schismtracker for that retro experience.<p>By the way, the beat generator feature is not trained on any artists or anything like that. It's an algorithm I built from scratch myself.<p>The audio engine is built on a declarative audio graph (using `virtual-audio-graph`), inspired by React's virtual DOM, which makes managing the Web Audio API much cleaner. If you're building web based audio apps I highly recommend checking out this library.<p>I'd love for you to try it out and let me know what you think. Feedback (and the inevitable bug reports) most welcome! Thank you!<p>P.S. Also, here's a video summary: <a href="https://youtu.be/qVmEn9z3H24" rel="nofollow">https://youtu.be/qVmEn9z3H24</a>

Show HN: Making a cross-platform game in Go using WebRTC Datachannels

Show HN: Making a cross-platform game in Go using WebRTC Datachannels

Show HN: Robot MCP Server – Connect Any Language Model and ROS Robots Using MCP

We’ve open-sourced the Robot MCP Server, a tool that lets large language models (LLMs) talk directly to robots running ROS1 or ROS2.<p>What it does - Connects any LLM to existing ROS robots via the Model Context Protocol (MCP) - Natural language → ROS topics, services, and actions (And the ability to read any of them back) - Works without changing robot source code<p>Why it matters - Makes robots accessible from natural language interfaces - Opens the door to rapid prototyping of AI-robot applications - We are trying to create a common interface for safe AI ↔ robot communication<p>This is too big to develop alone — we’d love feedback, contributors, and partners from both the robotics and AI communities.

Show HN: CrabCamera – Cross-platform camera plugin for Tauri desktop apps

After building several Tauri desktop apps, I kept hitting the same wall: there's no reliable way to access cameras across Windows, macOS, and Linux. Every project meant reinventing camera integration, dealing with platform-specific APIs, and debugging permission issues.<p><pre><code> So I built CrabCamera – a Tauri plugin that handles all the camera complexity for you. What it does: - One API, three platforms: Same Rust code works on Windows (DirectShow), macOS (AVFoundation), and Linux (V4L2) - Permission handling: Automatically requests camera permissions on each platform - Format conversion: Takes care of the messy bits between platform formats and what your app needs - Error handling: Proper Rust error types instead of mysterious crashes - Hot-plugging: Detects when cameras are connected/disconnected The problem it solves: Before CrabCamera, adding camera support to a Tauri app meant: 1. Writing separate native code for each platform 2. Managing three different permission systems 3. Handling format conversions manually 4. Debugging platform-specific edge cases 5. Maintaining it all as OS APIs change Now it's just: use crabcamera::Camera; let camera = Camera::new()?; let frame = camera.capture_frame().await?; Why I built it: I was working on a plant monitoring app (botanica) that needed reliable camera access for time-lapse photography. Existing solutions were either abandoned, platform-specific, or required complex native bindings. The Tauri ecosystem is growing fast, but camera support was this obvious gap. Every desktop app eventually needs camera access – video calls, document scanning, AR features, security monitoring. Technical highlights: - Uses nokhwa for the heavy lifting but wraps it in Tauri-friendly APIs - Proper async/await support throughout - Memory-efficient streaming for video capture - Built-in image processing pipeline - Extensible plugin architecture What's next: - WebRTC integration for video calls - Built-in barcode/QR code scanning - Face detection hooks - Performance optimizations for 4K streams The crate is MIT licensed and available on crates.io. I'd love feedback from other Tauri developers who've wrestled with camera integration. Links: - Crates.io: https://crates.io/crates/crabcamera - GitHub: https://github.com/Michael-A-Kuykendall/crabcamera - Documentation: https://docs.rs/crabcamera</code></pre>

Show HN: CrabCamera – Cross-platform camera plugin for Tauri desktop apps

After building several Tauri desktop apps, I kept hitting the same wall: there's no reliable way to access cameras across Windows, macOS, and Linux. Every project meant reinventing camera integration, dealing with platform-specific APIs, and debugging permission issues.<p><pre><code> So I built CrabCamera – a Tauri plugin that handles all the camera complexity for you. What it does: - One API, three platforms: Same Rust code works on Windows (DirectShow), macOS (AVFoundation), and Linux (V4L2) - Permission handling: Automatically requests camera permissions on each platform - Format conversion: Takes care of the messy bits between platform formats and what your app needs - Error handling: Proper Rust error types instead of mysterious crashes - Hot-plugging: Detects when cameras are connected/disconnected The problem it solves: Before CrabCamera, adding camera support to a Tauri app meant: 1. Writing separate native code for each platform 2. Managing three different permission systems 3. Handling format conversions manually 4. Debugging platform-specific edge cases 5. Maintaining it all as OS APIs change Now it's just: use crabcamera::Camera; let camera = Camera::new()?; let frame = camera.capture_frame().await?; Why I built it: I was working on a plant monitoring app (botanica) that needed reliable camera access for time-lapse photography. Existing solutions were either abandoned, platform-specific, or required complex native bindings. The Tauri ecosystem is growing fast, but camera support was this obvious gap. Every desktop app eventually needs camera access – video calls, document scanning, AR features, security monitoring. Technical highlights: - Uses nokhwa for the heavy lifting but wraps it in Tauri-friendly APIs - Proper async/await support throughout - Memory-efficient streaming for video capture - Built-in image processing pipeline - Extensible plugin architecture What's next: - WebRTC integration for video calls - Built-in barcode/QR code scanning - Face detection hooks - Performance optimizations for 4K streams The crate is MIT licensed and available on crates.io. I'd love feedback from other Tauri developers who've wrestled with camera integration. Links: - Crates.io: https://crates.io/crates/crabcamera - GitHub: https://github.com/Michael-A-Kuykendall/crabcamera - Documentation: https://docs.rs/crabcamera</code></pre>

Show HN: HumanAlarm – Real people knock on your door to wake you up

I built HumanAlarm because I'm a heavy sleeper who's missed important things despite multiple phone alarms.<p>It's exactly what it sounds like - you book a wake-up time, we send someone to knock on your door for 2 minutes. If you don't answer, they wait 3-5 minutes and knock again. Simple as that.<p>We're live in select cities.<p>Would love feedback on the concept and execution!

Show HN: HumanAlarm – Real people knock on your door to wake you up

I built HumanAlarm because I'm a heavy sleeper who's missed important things despite multiple phone alarms.<p>It's exactly what it sounds like - you book a wake-up time, we send someone to knock on your door for 2 minutes. If you don't answer, they wait 3-5 minutes and knock again. Simple as that.<p>We're live in select cities.<p>Would love feedback on the concept and execution!

Show HN: Small Transfers – charge from 0.000001 USD per request for your SaaS

Hi HN,<p>I built <i>Small Transfers</i>, a payments platform for SaaS / API makers who want to bill customers per request instead of pushing them into subscriptions or pre-buy packages.<p>*Why?*<p><pre><code> - Many customers hate subscriptions and/or want to use a service occasionally. - Traditional payment processors add a fixed fee to every charge, making charges below 1 USD impractical. - Stripe UBB tracks usage, but you still need to write your own auth, add spending limits, and each merchant charges cards separately (extra fees for customers). </code></pre> *How it works?*<p><pre><code> - Each merchant has a Small Transfers account linked to their Stripe account via Stripe Connect, which is used to transfer payouts to merchants. - Each customer has a Small Transfers account where we verify them using Google Sign-In, 3-D Secure, and Stripe Radar to minimise the chances of a customer not paying their balance. - Customers allow your service to identify and charge them via platform's own OAuth. This also removes the need for your service to implement its own auth. (Simple services don't even need their own database.) - Merchants call a simple REST API to authorize and capture a charge with a minimum amount of 0.000001 USD. Note that you can authorize more than you capture, allowing you to authorize the max amount your request might use, and then capture your actual cost plus margin (great for many use cases, e.g., AI). - The platform takes care of charging customers and sending payouts to merchants. - Merchants pay a flat 3% fee. Customers pay payment processing fees when they pay for their balance. </code></pre> There's a Next.js Starter project (<a href="https://github.com/smalltransfers/nextjs-starter" rel="nofollow">https://github.com/smalltransfers/nextjs-starter</a>) and a live demo (<a href="https://nextjs-starter.smalltransfers.com/" rel="nofollow">https://nextjs-starter.smalltransfers.com/</a>).<p>I've been dog-fooding the platform with my own service (<a href="https://unattach.com/" rel="nofollow">https://unattach.com/</a>) and would love your feedback, specifically:<p><pre><code> - The general approach and whether there is anything I should do differently. - Any concerns and how I could mitigate them. - Any other feedback. </code></pre> I'm also looking for more merchants to try out the platform, and can help you with the integration.<p>Thank you for your time! Happy to answer questions here.

Show HN: Small Transfers – charge from 0.000001 USD per request for your SaaS

Hi HN,<p>I built <i>Small Transfers</i>, a payments platform for SaaS / API makers who want to bill customers per request instead of pushing them into subscriptions or pre-buy packages.<p>*Why?*<p><pre><code> - Many customers hate subscriptions and/or want to use a service occasionally. - Traditional payment processors add a fixed fee to every charge, making charges below 1 USD impractical. - Stripe UBB tracks usage, but you still need to write your own auth, add spending limits, and each merchant charges cards separately (extra fees for customers). </code></pre> *How it works?*<p><pre><code> - Each merchant has a Small Transfers account linked to their Stripe account via Stripe Connect, which is used to transfer payouts to merchants. - Each customer has a Small Transfers account where we verify them using Google Sign-In, 3-D Secure, and Stripe Radar to minimise the chances of a customer not paying their balance. - Customers allow your service to identify and charge them via platform's own OAuth. This also removes the need for your service to implement its own auth. (Simple services don't even need their own database.) - Merchants call a simple REST API to authorize and capture a charge with a minimum amount of 0.000001 USD. Note that you can authorize more than you capture, allowing you to authorize the max amount your request might use, and then capture your actual cost plus margin (great for many use cases, e.g., AI). - The platform takes care of charging customers and sending payouts to merchants. - Merchants pay a flat 3% fee. Customers pay payment processing fees when they pay for their balance. </code></pre> There's a Next.js Starter project (<a href="https://github.com/smalltransfers/nextjs-starter" rel="nofollow">https://github.com/smalltransfers/nextjs-starter</a>) and a live demo (<a href="https://nextjs-starter.smalltransfers.com/" rel="nofollow">https://nextjs-starter.smalltransfers.com/</a>).<p>I've been dog-fooding the platform with my own service (<a href="https://unattach.com/" rel="nofollow">https://unattach.com/</a>) and would love your feedback, specifically:<p><pre><code> - The general approach and whether there is anything I should do differently. - Any concerns and how I could mitigate them. - Any other feedback. </code></pre> I'm also looking for more merchants to try out the platform, and can help you with the integration.<p>Thank you for your time! Happy to answer questions here.

Show HN: Small Transfers – charge from 0.000001 USD per request for your SaaS

Hi HN,<p>I built <i>Small Transfers</i>, a payments platform for SaaS / API makers who want to bill customers per request instead of pushing them into subscriptions or pre-buy packages.<p>*Why?*<p><pre><code> - Many customers hate subscriptions and/or want to use a service occasionally. - Traditional payment processors add a fixed fee to every charge, making charges below 1 USD impractical. - Stripe UBB tracks usage, but you still need to write your own auth, add spending limits, and each merchant charges cards separately (extra fees for customers). </code></pre> *How it works?*<p><pre><code> - Each merchant has a Small Transfers account linked to their Stripe account via Stripe Connect, which is used to transfer payouts to merchants. - Each customer has a Small Transfers account where we verify them using Google Sign-In, 3-D Secure, and Stripe Radar to minimise the chances of a customer not paying their balance. - Customers allow your service to identify and charge them via platform's own OAuth. This also removes the need for your service to implement its own auth. (Simple services don't even need their own database.) - Merchants call a simple REST API to authorize and capture a charge with a minimum amount of 0.000001 USD. Note that you can authorize more than you capture, allowing you to authorize the max amount your request might use, and then capture your actual cost plus margin (great for many use cases, e.g., AI). - The platform takes care of charging customers and sending payouts to merchants. - Merchants pay a flat 3% fee. Customers pay payment processing fees when they pay for their balance. </code></pre> There's a Next.js Starter project (<a href="https://github.com/smalltransfers/nextjs-starter" rel="nofollow">https://github.com/smalltransfers/nextjs-starter</a>) and a live demo (<a href="https://nextjs-starter.smalltransfers.com/" rel="nofollow">https://nextjs-starter.smalltransfers.com/</a>).<p>I've been dog-fooding the platform with my own service (<a href="https://unattach.com/" rel="nofollow">https://unattach.com/</a>) and would love your feedback, specifically:<p><pre><code> - The general approach and whether there is anything I should do differently. - Any concerns and how I could mitigate them. - Any other feedback. </code></pre> I'm also looking for more merchants to try out the platform, and can help you with the integration.<p>Thank you for your time! Happy to answer questions here.

Show HN: Small Transfers – charge from 0.000001 USD per request for your SaaS

Hi HN,<p>I built <i>Small Transfers</i>, a payments platform for SaaS / API makers who want to bill customers per request instead of pushing them into subscriptions or pre-buy packages.<p>*Why?*<p><pre><code> - Many customers hate subscriptions and/or want to use a service occasionally. - Traditional payment processors add a fixed fee to every charge, making charges below 1 USD impractical. - Stripe UBB tracks usage, but you still need to write your own auth, add spending limits, and each merchant charges cards separately (extra fees for customers). </code></pre> *How it works?*<p><pre><code> - Each merchant has a Small Transfers account linked to their Stripe account via Stripe Connect, which is used to transfer payouts to merchants. - Each customer has a Small Transfers account where we verify them using Google Sign-In, 3-D Secure, and Stripe Radar to minimise the chances of a customer not paying their balance. - Customers allow your service to identify and charge them via platform's own OAuth. This also removes the need for your service to implement its own auth. (Simple services don't even need their own database.) - Merchants call a simple REST API to authorize and capture a charge with a minimum amount of 0.000001 USD. Note that you can authorize more than you capture, allowing you to authorize the max amount your request might use, and then capture your actual cost plus margin (great for many use cases, e.g., AI). - The platform takes care of charging customers and sending payouts to merchants. - Merchants pay a flat 3% fee. Customers pay payment processing fees when they pay for their balance. </code></pre> There's a Next.js Starter project (<a href="https://github.com/smalltransfers/nextjs-starter" rel="nofollow">https://github.com/smalltransfers/nextjs-starter</a>) and a live demo (<a href="https://nextjs-starter.smalltransfers.com/" rel="nofollow">https://nextjs-starter.smalltransfers.com/</a>).<p>I've been dog-fooding the platform with my own service (<a href="https://unattach.com/" rel="nofollow">https://unattach.com/</a>) and would love your feedback, specifically:<p><pre><code> - The general approach and whether there is anything I should do differently. - Any concerns and how I could mitigate them. - Any other feedback. </code></pre> I'm also looking for more merchants to try out the platform, and can help you with the integration.<p>Thank you for your time! Happy to answer questions here.

Show HN: Small Transfers – charge from 0.000001 USD per request for your SaaS

Hi HN,<p>I built <i>Small Transfers</i>, a payments platform for SaaS / API makers who want to bill customers per request instead of pushing them into subscriptions or pre-buy packages.<p>*Why?*<p><pre><code> - Many customers hate subscriptions and/or want to use a service occasionally. - Traditional payment processors add a fixed fee to every charge, making charges below 1 USD impractical. - Stripe UBB tracks usage, but you still need to write your own auth, add spending limits, and each merchant charges cards separately (extra fees for customers). </code></pre> *How it works?*<p><pre><code> - Each merchant has a Small Transfers account linked to their Stripe account via Stripe Connect, which is used to transfer payouts to merchants. - Each customer has a Small Transfers account where we verify them using Google Sign-In, 3-D Secure, and Stripe Radar to minimise the chances of a customer not paying their balance. - Customers allow your service to identify and charge them via platform's own OAuth. This also removes the need for your service to implement its own auth. (Simple services don't even need their own database.) - Merchants call a simple REST API to authorize and capture a charge with a minimum amount of 0.000001 USD. Note that you can authorize more than you capture, allowing you to authorize the max amount your request might use, and then capture your actual cost plus margin (great for many use cases, e.g., AI). - The platform takes care of charging customers and sending payouts to merchants. - Merchants pay a flat 3% fee. Customers pay payment processing fees when they pay for their balance. </code></pre> There's a Next.js Starter project (<a href="https://github.com/smalltransfers/nextjs-starter" rel="nofollow">https://github.com/smalltransfers/nextjs-starter</a>) and a live demo (<a href="https://nextjs-starter.smalltransfers.com/" rel="nofollow">https://nextjs-starter.smalltransfers.com/</a>).<p>I've been dog-fooding the platform with my own service (<a href="https://unattach.com/" rel="nofollow">https://unattach.com/</a>) and would love your feedback, specifically:<p><pre><code> - The general approach and whether there is anything I should do differently. - Any concerns and how I could mitigate them. - Any other feedback. </code></pre> I'm also looking for more merchants to try out the platform, and can help you with the integration.<p>Thank you for your time! Happy to answer questions here.

Show HN: Small Transfers – charge from 0.000001 USD per request for your SaaS

Hi HN,<p>I built <i>Small Transfers</i>, a payments platform for SaaS / API makers who want to bill customers per request instead of pushing them into subscriptions or pre-buy packages.<p>*Why?*<p><pre><code> - Many customers hate subscriptions and/or want to use a service occasionally. - Traditional payment processors add a fixed fee to every charge, making charges below 1 USD impractical. - Stripe UBB tracks usage, but you still need to write your own auth, add spending limits, and each merchant charges cards separately (extra fees for customers). </code></pre> *How it works?*<p><pre><code> - Each merchant has a Small Transfers account linked to their Stripe account via Stripe Connect, which is used to transfer payouts to merchants. - Each customer has a Small Transfers account where we verify them using Google Sign-In, 3-D Secure, and Stripe Radar to minimise the chances of a customer not paying their balance. - Customers allow your service to identify and charge them via platform's own OAuth. This also removes the need for your service to implement its own auth. (Simple services don't even need their own database.) - Merchants call a simple REST API to authorize and capture a charge with a minimum amount of 0.000001 USD. Note that you can authorize more than you capture, allowing you to authorize the max amount your request might use, and then capture your actual cost plus margin (great for many use cases, e.g., AI). - The platform takes care of charging customers and sending payouts to merchants. - Merchants pay a flat 3% fee. Customers pay payment processing fees when they pay for their balance. </code></pre> There's a Next.js Starter project (<a href="https://github.com/smalltransfers/nextjs-starter" rel="nofollow">https://github.com/smalltransfers/nextjs-starter</a>) and a live demo (<a href="https://nextjs-starter.smalltransfers.com/" rel="nofollow">https://nextjs-starter.smalltransfers.com/</a>).<p>I've been dog-fooding the platform with my own service (<a href="https://unattach.com/" rel="nofollow">https://unattach.com/</a>) and would love your feedback, specifically:<p><pre><code> - The general approach and whether there is anything I should do differently. - Any concerns and how I could mitigate them. - Any other feedback. </code></pre> I'm also looking for more merchants to try out the platform, and can help you with the integration.<p>Thank you for your time! Happy to answer questions here.

Show HN: Small Transfers – charge from 0.000001 USD per request for your SaaS

Hi HN,<p>I built <i>Small Transfers</i>, a payments platform for SaaS / API makers who want to bill customers per request instead of pushing them into subscriptions or pre-buy packages.<p>*Why?*<p><pre><code> - Many customers hate subscriptions and/or want to use a service occasionally. - Traditional payment processors add a fixed fee to every charge, making charges below 1 USD impractical. - Stripe UBB tracks usage, but you still need to write your own auth, add spending limits, and each merchant charges cards separately (extra fees for customers). </code></pre> *How it works?*<p><pre><code> - Each merchant has a Small Transfers account linked to their Stripe account via Stripe Connect, which is used to transfer payouts to merchants. - Each customer has a Small Transfers account where we verify them using Google Sign-In, 3-D Secure, and Stripe Radar to minimise the chances of a customer not paying their balance. - Customers allow your service to identify and charge them via platform's own OAuth. This also removes the need for your service to implement its own auth. (Simple services don't even need their own database.) - Merchants call a simple REST API to authorize and capture a charge with a minimum amount of 0.000001 USD. Note that you can authorize more than you capture, allowing you to authorize the max amount your request might use, and then capture your actual cost plus margin (great for many use cases, e.g., AI). - The platform takes care of charging customers and sending payouts to merchants. - Merchants pay a flat 3% fee. Customers pay payment processing fees when they pay for their balance. </code></pre> There's a Next.js Starter project (<a href="https://github.com/smalltransfers/nextjs-starter" rel="nofollow">https://github.com/smalltransfers/nextjs-starter</a>) and a live demo (<a href="https://nextjs-starter.smalltransfers.com/" rel="nofollow">https://nextjs-starter.smalltransfers.com/</a>).<p>I've been dog-fooding the platform with my own service (<a href="https://unattach.com/" rel="nofollow">https://unattach.com/</a>) and would love your feedback, specifically:<p><pre><code> - The general approach and whether there is anything I should do differently. - Any concerns and how I could mitigate them. - Any other feedback. </code></pre> I'm also looking for more merchants to try out the platform, and can help you with the integration.<p>Thank you for your time! Happy to answer questions here.