Skip to main content
If you’ve built on Lovable and want to move to vly, this guide covers the differences and the porting steps.

​
What’s similar

Both ship full-stack output with built-in auth and a managed backend. Both expose the generated code for editing. Both support custom domains and integrations.

​
What’s different

​
Porting steps

1

Document your Lovable schema

Export Supabase schema as SQL or JSON. Note RLS policies (you’ll re-implement as auth-aware Convex queries).
2

Start a new vly project with the same prompt

Re-prompt the original spec into vly. Use Plan mode to verify the shape matches.
3

Port custom code

Lovable Edge Functions → Convex actions. SQL queries → Convex queries with .withIndex().
4

Migrate data (if needed)

Export from Supabase as JSON; import into Convex via a one-shot mutation.
5

Re-set up integrations

Re-paste API keys for Stripe, Resend, etc.
6

Cut over the domain

Update DNS to point at the new vly app.

​
Prompt-style differences

Lovable’s prompts are similar to vly’s. Two notable shifts:
  • vly’s Convex backend is reactive; you don’t ask for “real-time updates” — they’re automatic.
  • vly supports three agents; you can name a specific agent for a task.

​
Tips

Don’t skip Plan mode for the first prompt. Even if your Lovable spec was solid, Plan mode catches schema differences early.

Quickstart

Build your first vly app.

Compare

vly vs Lovable / v0 / Bolt.

Convex overview

The new backend.
Last modified on April 18, 2026