Twitter/X

Tyler Bruno (@tylerbruno05) says Lovable provides code portability via two-way…

2026-07-14 · 17:59 UTC ·@antonosika ·0 min read

Brief

Tyler Bruno argues Lovable removes common vendor-lockin objections: code export is handled by two-way git sync with full history, data is exportable as real Postgres with repo-stored migrations or via bring-your-own Supabase, and hosting is flexible—frontend on Netlify/Cloudflare and backend movable so you can mix and match.

Why it matters

Tyler Bruno (@tylerbruno05) says Lovable provides code portability via two-way git sync with full history and can run anywhere.

Key details

  • He claims data portability: real Postgres exports, migrations stored in your repo, or the option to bring your own Supabase from day one.
  • He emphasizes hosting flexibility: frontends can be hosted on Netlify, Cloudflare, or elsewhere, and you can move the backend while keeping the frontend (mix-and-match).
Source evidence

Seriously though, why would you host anywhere else?

If there's still something missing, tell me so we can fix it.

Tyler Bruno (@tylerbruno05)

people keep saying you can't leave Lovable:

"you can't get your code out" → two-way git sync, full history, runs anywhere

"your data is trapped" → real postgres export, migrations in your repo. or bring your own supabase from day one

"you have to host with them" → frontend on netlify, cloudflare, wherever. or move the backend and keep the frontend. mix and match

why would you though

— https://nitter.net/tylerbruno05/status/2077072367541711206#m