Deploy Code: source, records, GitHub, database

Click Publish in the builder. Go live is the default. Deploy Code is the other tab — download this app, download records, push to GitHub, or use a database you own.

The website stays on Beeflower. Your custom domain stays yours. Connecting Supabase only changes where new records save.

Push is a one-way copy of the source into a repo you own. It is not a deploy path. Auto-commit after Publish is optional.

Optional. Connect a Supabase you own from Deploy Code. Hosting and your custom domain stay on Beeflower. New records save in that project. App users may need to sign in again. Beeflower keeps a 14-day snapshot so you can undo.

Prefer a new empty Supabase project. Paste a service role key only if OAuth is unavailable.

Deploy Code lists collections and counts (sample vs live). Download records as CSV/JSON. Password hashes are never exported. Free plans can see counts; download and attach stay on paid plans.

You still publish on Beeflower. Downloaded source is yours to keep. Running that zip on your own servers is a separate project — the live site and custom domain stay here.