Supabase integration

Vibe coding on your own Supabase

Every Blaubok site keeps its logins and records in a Supabase project that belongs to you. You connect it once, the build sets up the tables, and your site talks to your database directly.

Start building free All integrations

What it sets up

Everything your site stores, in your project

The engine’s features come with their database already designed. The build creates what you need on your Supabase, with your keys.

Logins

Email and password, magic links and password resets, all on Supabase Auth in your project. Add Google sign-in by turning on the provider in Supabase.

Tables with row-level security

Each feature brings its own tables, created by migrations run through the Supabase Management API. Every table ships with access rules.

Tracked migrations

A tracker table on your database records each migration that has run, so a rebuild never applies the same one twice.

Your business records

Leads, bookings, orders, payments and staff roles are rows in your database. Open them in Supabase Studio whenever you like.

Content

Blog posts, pages and settings your admin edits are stored in the same project, next to everything else.

Scheduled jobs

Reminders and digests run as Vercel cron jobs on your account and read and write your Supabase directly.

Your part

Four values to paste, once

Copy them from your Supabase dashboard into the project’s Connections tab. They are encrypted at rest and never shown in the browser.

Project URL

https://abcd1234.supabase.coSupabase → Settings → API → Project URL

Anon key

eyJhbGciOiJI…Settings → API → Project API keys → anon public

Service role key

eyJhbGciOiJI…Settings → API → Project API keys → service_role (keep it secret)

Management token

sbp_a8f9c1e2…supabase.com/dashboard/account/tokens, used to apply migrations

When you click Build

What happens on your database

1
Checked when you save
The Connections tab validates your keys against your project before saving them, encrypted with AES-256-GCM.
2
Tables for your features
When you click Build, the migrations for the features you chose run on your project. Ones that already ran are skipped.
3
Wired into your site
Your Supabase URL and keys are set on your Vercel project for you. From then on, your site talks to your database directly.

Out of the way

Your data never passes through us

Your visitors’ requests go from your site on Vercel straight to your Supabase. Blaubok is not in between.
Your keys are used only to build, deploy and update your site, and you can disconnect or rotate them at any time.
Supabase bills you directly. Blaubok never sees or pays your Supabase invoice.

FAQ

Supabase questions

What Supabase plan do I need?

The free plan is enough to start, and most small business sites stay on it for a long time. Supabase lists its current limits on its pricing page. Upgrade only when your site outgrows them.

Why does Blaubok need my service role key and a management token?

The management token lets the build create your tables and access rules through the Supabase Management API. The service role key is what your site’s server code uses to read and write data. Both are stored encrypted and never shown in the browser.

Can I use an existing Supabase project?

You can, but a new, empty project is the safest choice. The build adds its own tables and records each migration it runs, so starting clean avoids clashing with tables you already have.

Can I edit the data or the schema in Supabase Studio?

Yes. It is your database. Edit records, export them or add your own tables. Keep row-level security turned on for any table you add, or anyone holding your site’s public key can read it.

What happens to my data if I stop using Blaubok?

Nothing. It stays in your Supabase project, and your site keeps reading and writing it. If your plan and credits run out, your site keeps running on your own accounts.