Hey Product Hunt community!
I want to share the real story behind why we built Runa because it comes from a frustration I kept seeing over and over again.
The problem we couldn't ignore: Every week, SaaS founders spend thousands on great products beautiful UI, powerful features, solid engineering. But users still churn. Still flood support inboxes. Still drop off during onboarding.
Why? Because the gap between "I want to do X" and "I know how to do X in this product" is enormous.
Congrats on your launch! Working at a startup, I see firsthand how much users struggler to find features they actually need. Runa sounds like it could fix that whole problem. Does it work across different types of apps or is it built for specific use cases?
@aya_vlasoff Thank you soo much ! 🙏 yes it works across all apps
You can connect Runa by just adding the widget on top of your UI. No codebase access required, no deep backend integration, no engineering sprint.
Just add this
Would love to show you a quick demo 🙌 I will connect with via an email 🚀
What types of tasks does the AI agent handle autonomously versus ones that still need human approval? Curious about the automation boundaries, congrats on launching!
@borrellr_ Thanks so much! 🙏
Great question on the autonomy boundaries this is something we thought hard about.
Runa handles read and write actions autonomously things like fetching data, sending data through apis, updating settings, triggering apis. Anything your API already supports, Runa can execute on behalf of the user instantly. ⚡
For sensitive or irreversible actions like deleting data, making payments, or bulk operations you stay fully in control. As the product owner, you define which actions require confirmation and which can run freely. It's configurable at the tool level when you upload your OpenAPI spec.
Think of it like giving your users a capable assistant that knows exactly where the guardrails are. 🎯
Happy to walk you through how the permission layer works if you want a deeper look! 🙌
Congrats on the launch! The "how do I.." support ticket is one of the most expensive things a SaaS product deals with. It's not just the ticket, it's the churn that happens when users give up before ever submitting one. An agent that actually executes the action instead of explaining how to do it is a different category of solution. How much setup does it take to connect Runa to an existing product? Does it need access to the codebase or does it work on top of the UI?
@simonk123 Thank you so much! 🙏 And you nailed it the silent churn before the ticket is the real killer. Most products never even see it coming.
Setup is intentionally lightweight. You connect Runa by just adding the widget on top of your UI. No codebase access required, no deep backend integration, no engineering sprint.
Just add this
It works on top of your existing app so if your product already has an API (which most SaaS products do), Runa is essentially plug-and-play. Tools get auto-generated from your spec, and users can start interacting through chat immediately.
No UI scraping. No codebase access. No middleware rebuilds.
Just your existing app doing what it already does except now users can trigger it through natural language instead of navigating your UI.
The whole idea was to make this something a non-technical founder could set up in an afternoon 🚀
Would love to show you a quick demo 🙌 I will connect with via an email 🚀