Export and lock-in: what you own when you build on Floot, Base44, or Lovable

Estimated reading time: 6 minutes. Last verified: August 2026.

Key takeaways

• Assume hosting lock-in is real even when marketing says "your code is yours."
• Lovable documents Git sync early; paid plans add download.
• Floot and Base44 emphasize owned IP; verify current export steps in docs before you bet the company.
• Hercules allows download/self-host with limited support for self-hosted setups.
• Practical rule: schedule an export drill in week two, not month twelve.

Table of contents

1. What lock-in actually means
2. Vendor snapshot
3. Exit checklist
4. FAQ

What lock-in actually means

Three layers:

1. Code (can you get source?)
2. Data (can you dump the database cleanly?)
3. Runtime (do auth, jobs, and file storage port, or only the UI?)

Most AI builders are honest about (1) and fuzzy about (3).

Vendor snapshot

Vendor	Code path	Notes
Lovable	Git sync; download on paid	Strongest "engineer takeover" story
Floot	IP ownership claims; confirm export docs	SEO/hosting value is platform-tied
Base44	Ownership claims; GitHub on higher plans	Growth tools are platform-tied
Hercules	Download supported; self-host unsupported officially	Cloud is the supported path

Exit checklist

• Monthly DB export
• Auth provider strategy (stay portable)
• Secrets stored outside the builder
• One "rebuild critical path in Cursor/Replit" spike completed
• Domain and DNS under your account

FAQ

Is lock-in a reason to avoid AI builders?

No. It is a reason to practice exports. Speed still wins early.

Who is least locked in?

Teams that keep Git as source of truth (Lovable/Replit-style) usually leave cleaner than teams that only ever click Publish.