Setting Up Your Database
Your database stores your app's data — users, posts, settings. Vibecheck connects one for you automatically. If your app doesn't have a database, you can skip this.
What Happens
Vibecheck scans your project for database config, then asks who manages your database right now. Your answer determines the path: migrate from a platform, connect an existing project, enter a connection string for another provider, or skip for now. Then you pick automatic or guided setup.
It's Not Working
I already have a Supabase project from Lovable or Bolt›
Choose "It's locked in my platform." Vibecheck will walk you through migrating your data to a project you control. Your tables stay intact.
I chose the wrong option — how do I go back?›
Click the back arrow at the top left. You can go all the way back to the ownership choice.
Automated Setup
Claude creates your Supabase project, waits for provisioning, and grabs the credentials. You just watch the progress steps. You need a free Supabase account and the Supabase CLI logged in — Vibecheck checks for both before starting.
It's Not Working
The automated setup seems stuck or failed›
Database creation can take several minutes — long pauses between steps are normal. If the spinner is still going, give it time. If you see a red error or it's been more than 10 minutes with no progress, click "Having trouble? Switch to manual setup" at the bottom of the screen. Vibecheck will walk you through the rest.
"Not logged into Supabase"›
Open a terminal and run supabase login, then click "Try again."
I don't see my organization in the picker›
Make sure you're logged into the Supabase CLI with the same account that owns the org. Run supabase login in a terminal to re-authenticate.
"You've reached your Supabase project limit" ›
Free accounts can have 2 active projects. Go to your Supabase dashboard, pause or delete one you're not using, then try again.
Guided Setup
If you skip automation or it doesn't work, Vibecheck walks you through each step itself — tailored to where you're coming from (Lovable, Bolt, Replit, or fresh). You'll create or connect your project and paste the credentials back.
It's Not Working
I can't find the export button in Lovable›
Open your project → Cloud tab → Database. Click a table name, then the export/CSV button. Do this for each table.
What does "Claim in Supabase" mean? (Bolt)›
It moves your database ownership to your Supabase account. Your Bolt app keeps working exactly the same. This is permanent — once claimed, you can't undo it.
Entering Credentials
When Vibecheck asks for credentials, go to your Supabase dashboard. The Project URL is under Integrations → Data API. The keys are under Settings → API Keys → Legacy tab — copy the anon public key and the service_rolekey. Paste them into Vibecheck and click "Test Connection."
It's Not Working
Where do I find my API keys?›
Supabase dashboard → your project → Integrations → Data API for the Project URL. For keys: Settings → API Keys → Legacy tab → copy anon public and service_role.
It says "Invalid API key"›
Keys are long and easy to truncate. Click into the field in Supabase, Cmd+A to select all, copy, then paste fresh into Vibecheck.
The connection test fails›
Three things to check:
- URL starts with
https://and looks likehttps://xxxxx.supabase.co - You're using the
anon publickey, not theservice_rolekey - Project is done provisioning — new projects can take several minutes
My Supabase project is "paused"›
Free tier projects pause after 1 week of inactivity. Go to your dashboard, find it, and click "Restore project." Takes about a minute.
Development Database
After connecting prod, Vibecheck asks about a dev database — a separate copy just for building and testing. "Create one for me" is the easiest option. You can also paste credentials for an existing one, or skip and work against prod for now.
It's Not Working
What's the difference between dev and prod?›
Dev = a test database just for you. Break things freely. Prod = the live database your real users hit.
Dev database creation failed›
Check the error message — it's usually a project limit (free accounts get 2 active projects) or a timeout. For limits, pause or delete an unused project at supabase.com/dashboard. For timeouts, try again — provisioning can be slow.
What happens if I skip the dev database?›
You'll test changes directly on your production data. Fine for getting started, but be careful — mistakes affect real users. You can always create a dev Supabase project manually and add its credentials to .env.development.local in your project later.
Other Providers
If you chose "I use something else," you'll enter a connection string instead of Supabase credentials. Find it in your provider's dashboard — usually under Connection Details or Variables.
It's Not Working
What's a connection string?›
A URL that tells your app where to find the database. Looks like postgresql://user:password@host:5432/dbname. Your provider gives you this — look for "Connection Details" in their dashboard.
Still stuck? Contact us →