u/pvdyck

Looking for beta testers who actually build automations.

what it does: you publish an n8n-compatible agent, set a per run price, people pay each time it runs. you keep 100% of your price, 10% only when you cash out. AI cost gets billed to the caller so your margin survives. buyers just use email and pay as you go.

what i need from testers: publish a real agent, try to break the billing, tell me what confused you. not chasing signup numbers, chasing the first honest "this part sucks."

beta runs through august, full launch september. chat.indie.money

founder of indie.money here, i answer everything.

Months of building, beta opened this week.

the idea: publish an n8n-compatible agent, set a per run price, get paid every time someone runs it. you keep 100% of your price, the only cut is 10% when you cash out. AI cost is billed to the caller, not you, so token spend stops eating your margin. buyers sign in with email, pay as they go, no crypto needed.

=> basically: sell the template once for 29 bucks, or get paid every run. i wanted the second option to exist.

its rough in places, its a beta. looking for builders who'll tell me where it breaks: chat.indie.money

founder of indie.money , ask me anything.

spent months building this and the beta just opened, so i want honest feedback. especially the "this wont work because" kind.

you publish an n8n-compatible agent, set a per run price, and people pay each time it runs. you keep 100% of your price, the only cut is 10% when you cash out. the part i think actually matters: the AI cost is billed to the caller, not you. token cost stops eating your margin, you can even mark it up.

most of us sell the template once for 29 bucks and thats it. this is the other option: get paid every run.

its rough, its a beta, i want builders who break things. link in my profile if you want to poke at it. im the founder, ask me anything.

Every week someone announces a new Python/TS framework for AI agents.

Retry logic, tool routing, memory, logging... cool, we've seen this before.

n8n has had all of this for years tbh. With a UI, 500+ integrations, self-hostable, actively maintained. And the thing people sleep on: you can visually debug exactly where your agent blew up, inspect the payload at every step, and replay it. Try doing that with your custom LangChain script... I tried, it was a nightmare.

I get it, rolling your own feels more serious. More "real". But at some point you're just rewriting plumbing that already exists and calling it architecture. And when your agent silently fails in prod you'll wish you had a visual trace.... something n8n offers.

Yes self hosting n8n has its moments, queue modes, worker configs, webhook tunnels... not gonna pretend it's plug and play. But it's a one time pain vs rewriting retry logic forever.

The one thing i'll grant: n8n's code node has limits, and if your agent logic is genuinely complex you'll hit them. But for 90% of what people are actually building? it's overkill to go custom.

Is the "real engineers write their own orchestration" thing still a take worth having in 2026?

Genuinly curious. What are you building that n8n can't handle? Happy to be wrong here.