Vybe - Lovable for internal apps

@marwannas  Thanks! A great milestone today and so much more ahead of us!

@benln Thanks a lot!
Big week indeed: GA Launch, fundraising announcement and rebranding... pfiou!

@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

@abod_rehman Quite convinced it will! (or at least, that's what we are working towards :) )
Any particular chaos we could help you have in mind right now? ;)

@imraju Thanks for the shout!

Some thoughts on your question about performance scale.
1 - we have been working with customers with such volume for dashboard usecases and it has worked well so far... for their usecases. Which makes me confident that we can handle huge volumes of data today already
2 - also, one big realization over the past few months working with our customer base is that for many internal applications, you only need a subset of data to work with - ex: if you create processes around salesforce or Jira, you generally only need let's say "records created in the last 3 months" as working data.
Our integrations infrastructure and specifically our "Data Queries" feature allows you to define such dataset to avoid bloating all apps with millions of unnecessary rows
3 - Also let's face it, we have not yet stress tested our system to humongous volumes but it is definitely a priority of ours to enable those customers over time.

And about the private infrastructure:
Not available today but it does come up on all our enterprise conversations so definitely on the roadmap!

@govindsajit Great minds think alike @govindsajit :)
I could not have said it better.

One big learning over the past few months is that engineering, despite not wanting to own those internal products, wants to stay in the loop at all phases: setup (privacy, data connections...), building (setting up foundations, checking the work...), iterations (debugging, data model updates...)
Instead of fighting this, we want to enable those teams to work together on 1 unified platform.

@taro_f Thanks a Taro!
and yes, so many great usecases for investors with Vybe such as:
- deal management
- LP management
- data gathering and transformation
- outreach
- meeting management
...

@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.