Vendo - Let your users build their own features inside your product

by•
Vendo is an open-source customization layer in your product that lets every customer add the features and micro-apps they need, just by describing what they want. Until now software has been rigid, and every customer had to adapt to it. Vendo makes it dynamic, so your product shapes itself around each customer, built on your own API and inside the guardrails you set.

Add a comment

Replies

Best
Maker
šŸ“Œ
Hey Product Hunt šŸ‘‹ I'm Nour, cofounder of Vendo (YC S26). Vendo embeds an agent inside your product that lets each of your customers build their own features and micro-apps directly on top of it, just by describing what they want. We built it because every SaaS team we talked to had the same problem. Every customer wants the product to work a little differently, the requests never stop, and no roadmap can keep up. Most teams answer that with a chatbot bolted to the corner of the screen. Software has always been rigid, and every customer had to adapt to it. Now it's dynamic, and your product shapes itself around each customer. Everything runs on your existing API, renders natively in your own theme and components, and never touches your source code. You can plug Vendo into an agent you already have, or deploy a production-ready one that takes actions in the product, generates UI, connects hundreds of external tools, and draws on a built-in knowledge base. It's open source and installs with a single command. šŸ‘‰ Try it at and check out the repo:

I found navigating many SaaS UIs (e.g., Rippling) frustrating. They're built to serve every possible customer, so the UI is crowded with features and buttons that have nothing to do with what I came to do. As an end user, being able to personalize the UX will be super useful!

Ā We think so too, thanks Ray!

Ā That's been the experience of a lot of people that we've spoken to! And companies are finding it hard to keep up with all the requests. We think Vendo can be a game-changer for them!

This is super cool! What happens if my software is also being updated for all users? Do you resolve conflicts and how?

Ā Great question Zach, and this is a problem we have worked hard to solve! We have a smart conflict resolution process that tries to re-apply the same user edits to the updated code and tries to resolve it as much as it can itself. If it is unable too though, we surface it to the user and let them know.

interesting - can def see adv of this as a way to add val to customers. hows it sandboxed tho ?

Ā Great question! We have two layers. For quick screens where there is no need for a backend, we have a QuickJS-based sandbox that runs everything and generates the UI for the user (this happens instantly, and it looks native on your site). For features/apps that need a backend or more advanced capabilities, we spawn an ephermeral sandbox where everything runs from.

Ā ok how does this impact latency?

Ā For the first layer (the QuickJS-based sandbox) it does not affect latency at all, and it is instant. This is since it is in-process so there is no noticeable delay. For more advanced applications requiring an ephermeral sandbox, there is a slight increase in latency (still sub-second). But we keep a warm pool to minimize this!

Ā nice!

Let us know if you have any questions, we'll be here answering everything!

Very Interesting! Can this pull in data from tools outside our product, or is it only our own data?

Ā Thanks! Both, actually. It runs on your API and data, and anything it generates is built from your own components so it doesn't invent anything. On top of that, your users can connect their own outside tools (we support hundreds of integrations), so the agent can pull from those too.

Very interesting guys. I really like the idea, but I am curious to howthis really work in practice. Does the user request really buid a feature in realtime for just that particular customer? Have seen some cool demos of the new gimini for this lately. Definetly some potential here. Congrats on the launch!