Fabien (Wolfia, S22) and myself (Plato, W16), are back to building again and today, we’re excited to share what we've been cooking for the past few months! And we’re part of the current batch!

We’re building a Lovable for internal apps. We come with pre-built building blocks: Integrations, SSO, and AI tools so anyone in a company can build and launch internal apps.

https://youtu.be/jaB3EnuU_cI

I included 5-6 other examples of things I built to run Vybe on vybe below :)

The unsolved problem:

Fast‑growing teams drown in _glue work_—onboarding trackers, launch calendars, status bots, one‑off scripts. Each steals engineering time, rots when its owner leaves, and derails sprints.

It leaves companies with three bad options:

• Rigid enterprise SaaS – inflexible, forces your process to fit the tool.
• Spreadsheets & docs – endless copy‑paste, no live data, fragile at scale.
• DIY glue & drag‑and‑drop no‑code – a tangle of scripts and widgets that collapse when owners leave.

Why current vibe coding tools aren’t enough:

Vibe coding is dramatically lowering the barrier for non-technical users to create full web apps. Lovable, Replit, Bolt, Google, Canva, Figma all launched their vibe-coding platforms. People love them. They're great for prototyping, but it's difficult to roll out inside a company for internal use cases for those reasons:

• Data: If you want to connect your existing data (e.g. Salesforce, Gmail, Jira), you'd need to rebuild the API auth, pagination, etc.
• SSO: If you build 20 apps, you'll have 20 different logins…
• Security: AI-built apps have the massive risk of exposing data, especially if built by non-developers

Cursor and Windsurf are not adapted either. They’re built for devs, hard to use for non-technical folks. My Head of HR doesn’t know how to deploy an app in Netlify or Vercel.

Why old no-code tools are solutions of the past:

• Airtable / Retool / Coda: No‑code and low‑code platforms showed you can build dashboards faster than hand‑coding React—but you're still dragging rectangles, hunting for SQL, and rebuilding the same CRUD table for the hundredth time.
• Large‑language models have changed the game. Code‑gen IDEs already write production‑grade functions from chat—so why are we still moving boxes to connect Salesforce to a launch‑approval form?

We’d love your help:

1. Companies: Design partners: Pick a painful process internally in your company, let us rebuild it in a more robust way.
2. Users: -> Join the waitlist: https://www.vybe.build/ and we’ll accept you as fast as we can! Comment "waitlist" or re-post, and we'll bump you to the top of the list!

Here are some nice examples of things I built on Vybe:

A daily briefer of my day, an AI is doing a web search on every single person I’m meeting every day:

A weekly goals tracker with a count down until YC demo day:

Our backlog/roadmap of things to ship:

Our DB Admin fed by our production database (postgres) built in 10 mins:

A simple to-do i created with routines, timer and link to my tech backlog so i can easily add tasks to myself from the roadmap

**A nice CRM (**no, i don’t use Salesforce, Hubspot or any other CRM) that is connected to my postgres so i can monitor deals and usages at the same place

And check tens of other examples: https://www.vybe.build/examples

It’s time to build 💪 Join the waitlist: https://www.vybe.build/ and we’ll accept you as fast as we can! Comment "waitlist" and we'll bump you to the top of the list!