Vybe
Lovable for internal apps
347 followers
Lovable for internal apps
347 followers
Vybe turns natural language into secure, production-ready internal apps that connect to your real data. No long backlogs, no glue code, no fragile prototypes. Auth, roles and deployments are built in. Plug in Postgres, Salesforce, Jira and 3,000 integrations. Start from scratch or remix templates used by world-class operators and make them your own in seconds. Internal tools that actually ship.
Vybe
👋 Hey PH! Today we’re launching Vybe to the world and announcing our $10M Seed round to make vibe-coding actually work inside companies.
We built Vybe because every fast-growing company ends up duct-taping operations together with rigid SaaS, spreadsheets, and manual hacks. Engineers are stretched thin, so internal tools never reach the top of the backlog, leaving teams blocked and processes fragile.
Meanwhile, vibe-coding has exploded in creativity… but it still falls short when you try to build *secure, data-connected, team-ready* internal apps. We built Vybe to change that -> Build secure, connected internal apps with natural language
How do you empower business teams to move fast without creating chaos, and without turning engineers into bottlenecks?
Every fast-growing company hits the same wall.
-> Marketing needs dashboards. Ops needs workflows. CS needs internal tools.
-> Engineering wants to help… but also needs to ship the actual product.
Historically, teams had two bad options:
1. Business builds their own tools
→ using spreadsheets, Coda, Notion, or lightweight AI builders.
Fast at first… until it becomes unmaintainable, impossible to debug, and impossible for engineering to support.
2. Engineering builds everything
→ professional, scalable, secure…
but slow, costly, and instantly becomes a backlog of “Can you change this button?” or “We need a new field for tomorrow’s launch.”
Both models fail
Our vision: A third model: shared ownership.
A world where:
1. Engineers own the foundation
- Secure data access
- Integrations
- SQL definitions / metrics alignment
- Permissions & access control
- Git, review, and oversight
- The initial scaffold of the app
Business teams own the surface area
- Workflow steps
- Buttons, fields, logic
- Iterating on what they need day-to-day
- Shipping changes without needing an engineer every time
Both groups operate in the same system:
- Real code under the hood
- Real GitHub repos
- Real access controls
- Real integrations
Vybe lets anyone inside a company describe what they want, and instantly generate real production-grade software!
@qhoang09 Excited about natural language surfaces
@qhoang09 Hey Quang, can you use internal design system / components library with Vybe to achieve the UX / UI and visual consistency with our other apps?
Snippets AI
Vybe
@svyat_dvoretski We do!
even better, they come from the best Operators , like Lenny Rachitsky, CTO 23andMe, VP Engineering Pagerduty etc.!
https://www.vybe.build/templates
Snippets AI
Wow, Vybe looks amazing! The natural language to internal app generation is mind-blowing. How does the role-based access control handle complex hierarchical org structures? Super curious!
@jaydev13 Thanks so much! 🙌 We designed our access control to be both powerful and intuitive. You get flexible role assignments (owner, admin, editor, viewer) combined with granular app-level permissions, so you can easily control who sees what without the complexity headache.
At co2ai.com, we have built with Vybe a complete internal tool that replaces a big part of our CRM, analytics dashboards, Notion pages, calendar syncing systems, weekly reportings, task managements... Something absolutely incredible and just unthinkable 6 months ago!
The most exciting part is that the end users themselves can fix/improve the app when needed, which is a total new game.
Vybe
@florian_jourda1 Thanks Floriam, was a pleasure to work together with your CS team on this!!
RiteKit Company Logo API
Wow
Congrats for the launch!
The Truth SQL feature seems awesome, do you have more examples to share?
Vybe
@skelz0r Thanks @skelz0r
Yeah definitely - this feature allows IT and Eng team to set up query "definitions".
A common one is "MAUs" => you could vibe code that and ask the AI to figure out the query yourself but most companies, as they grow to a certain size have very particular definitions of "Active".
With our feature, we would allow a data engineer to input the MAU sql query into Vybe once and for all and call it "Monthly Active Users".
Then when a PM wants to build app let's say, they can simply refer to this query using "@Monthly Active Users" (with auto complete) and be sure to have reliable data.
And if the definition changes, just update the query definition!
Hope this helps @skelz0r
UX Masterclass.design
I’ve been prototyping with Vybe since a few weeks and I must say that the off the shelves integrations are a game changer to build internal apps. Need to prototype more with it!
Great job team!
Vybe
@mickatouillaud Thanks @mickatouillaud for the kind words.
Indeed, no internal application lives in its silo. Whether it's pulling data, updating records or simply notifying, it's hard to think of a *good* internal app that is not connected to the rest of the organization tool stack in some way.
We hope we can make that smoother!