Backend and data
Use your own backend
Run your app on your own Supabase or Neon project instead of Buildliy hosting, what changes when you do, and how to switch back.
By default, your app's data and accounts live on Buildliy hosting. Buildliy sets it up, runs it and bills it in credits, and you never have to think about it. If you'd rather keep your data in an account you own and pay for directly, you can connect your own Supabase or Neon project instead.
Most people should stay on Buildliy hosting. Connecting your own backend makes sense when:
- you already have a Supabase or Neon project you want this app to use
- you want your data in an account you control, with its own dashboard, backups and billing
- your company needs data stored with a particular provider
Your three choices
Open the Manage tab and choose Backend. You'll see three cards:
| Choice | What it means |
|---|---|
| Buildliy hosting (recommended) | Zero setup. Buildliy hosts and manages your database and sign-in, paid from your credits. |
| Your own Supabase | Use a Supabase project from your own account. You manage it, and Supabase bills you directly. |
| Your own Neon | Use a Neon project from your own account. You manage it, and Neon bills you directly. |
The card your app uses now is marked Current.
Connect your own Supabase
Open the Supabase wizard
In Manage → Backend, click Connect on Your own Supabase.
Copy three values from Supabase
In your Supabase dashboard, open your project (or create a free one), then go to Settings → API. Copy the Project URL (it looks like
https://your-ref.supabase.co), the anon public key and the service_role key.Paste them and test
Paste the three values into the wizard and click Test & connect. Buildliy tests the connection before saving anything, and tells you plainly if a value is wrong.
Connect your own Neon
Open the Neon wizard
In Manage → Backend, click Connect on Your own Neon.
Copy your connection string
In your Neon console, open your project (or create a free one), go to Connection Details and copy the pooled connection string. It starts with
postgresql://and points at aneon.techaddress.Paste it and test
Paste it into Connection string and click Test & connect.
When it works, a Connected banner shows your project's address and "self-managed — billed by Supabase directly" (or Neon).
Your keys and connection string are stored encrypted and used only by your app. The Supabase service_role key and the Neon connection string are kept on the server and never reach visitors' browsers.
What changes when you connect
Your app starts using your own backend from its next build. Here's what's different:
| Your own Supabase | Your own Neon | |
|---|---|---|
| Sign-in | Supabase's own sign-in. By default, new users must click a link in a confirmation email before they can sign in. You can turn that off in your Supabase dashboard under Authentication → Providers → Email. | The same built-in email and password sign-in as Buildliy hosting, with accounts stored in your Neon database. |
| New tables | Buildliy can't create tables in your Supabase project. The AI gives you a short piece of SQL to run once in your Supabase dashboard's SQL Editor. Until you run it, that part of your app has no data to show. | The AI creates tables directly in your Neon database. |
| Where you manage data and users | Your Supabase dashboard | Your Neon console. Manage → Database can show, search and download your data, but changes are made in Neon. |
| AI data tools | The AI can't read or change your data from the chat. | The AI can read your data, but tells you what to change instead of changing it. |
| Backups and data rewind | Not available in Buildliy. Use your provider's own backups. | Not available in Buildliy. Use your provider's own backups. |
Buildliy doesn't copy data between backends. If your app already saved data on Buildliy hosting, that data stays there and your app won't see it after you switch.
If your app already has sign-in or saved data, the code that talks to the database has to change for the new backend. After you connect, ask the AI to update your app for it, then test sign-up and saving data in the preview before you publish.
I've connected my own Supabase project. Update the app's sign-in and data pages to use it, and tell me any SQL I need to run.
When you publish, your live app uses your own backend too.
What it costs
With your own backend, its database doesn't use your Buildliy credits. Supabase or Neon bill you directly under your own plan with them. Building with the AI still uses credits as usual. See Credits and usage.
The Overview in Manage shows Your Supabase or Your Neon with your project's address, and a Manage backend button that takes you to the Backend section.
Switch back or change backends
To go back to Buildliy hosting, click Disconnect on the Connected banner, or Use Buildliy hosting on the Buildliy hosting card, and confirm. Buildliy forgets your connection details and your app goes back to its Buildliy database, with whatever data it had there before you connected, or empty if it never had one. Your data stays in your Supabase or Neon project, and nothing there is deleted, but the app won't see it unless you reconnect.
To move from one provider to the other, click Connect on the other card. As with any switch, ask the AI to update your app afterwards and test it in the preview.
Only the project's owner can connect or disconnect a backend.
Related
Still stuck? Read the FAQ or contact us.
