Lovable Cloud
First met in aicp-c3-basecamp-02 · Backend, hosting & code · Vibe-coding platforms
Lovable CloudFirst met in aicp-c3-basecamp-02 · Backend, hosting & code · Vibe-coding platforms
Lovable's own bundled back end — database, auth, storage and AI models with zero setup, in exchange for living inside Lovable.
You want the MVP working today and lock-in is an acceptable price — pick Supabase instead the moment the app matters.
Zero configuration: no separate account, no keys, no SQL editor
AI models included, so a generated app can call an LLM without you buying API credits
It's what Lovable actively steers you toward — the BC2 trainer pivoted to it mid-demo
Provisions database, auth and storage inside the Lovable project
Supplies AI model access out of the box
Removes the whole Supabase connect-and-migrate step from the build
Doesn't give you portable infrastructure — the escape route is worse than plain Postgres
Doesn't expose the same control surface as Supabase (RLS, SQL editor, edge functions)
MVP and demo builds where speed beats ownership. Anything with real users should be on infrastructure you control.
Backend, hosting & code · Vibe-coding platforms
No Lovable project; the lock-in is the wrong trade for anything Paul would keep.
Useful as a cautionary example when evaluating any 'batteries included' platform: ask what the exit costs before the demo ends.
current
supabase: the trade-off is speed vs lock-in; BC2 showed the Supabase path being abandoned live
lovable: only exists inside Lovable
| Session | Coverage | Moment | What happened |
|---|---|---|---|
| Basecamp 2: Vibe Coding | demonstrated | 1:52:04 | Mid-session pivot target; full back end + AI models out of the box; 'what they are pushing so badly' |