Menu

1 / 11

One Supabase Project per Customer: Apply a Template, Catch Hand-Made Changes With a Schema Fingerprint, Hand Over, and Split the Costs

DEV Community: postgres·Tomo·about 5 hours ago
#0asK3JgP
#devtopostgresql#devto#dev#project#customer
Reading 0:00
15s threshold

If you give every customer their own Supabase project, the hard part is not creating them. It is keeping them the same, knowing who owns each one, and handing one over. I tried the first two on two free projects and the third in a limited way, then built a small console page. Everything is from my run on 2026-10-27, and prices change.

How this was made: I wrote this with Claude's help: it drafted, and I ran every step, edited the text, and checked the results. The mistakes are mine. This is a personal learning project, not an official guide, and I don't work for Supabase.

The non-technical version (two owners, drift, hand-over checks): https://medium.com/p/50275a612b87

The code: https://github.com/tomozilla/customer-env-console-en-demo

What I did and did not do

I applied one SQL template to two free projects , compared a schema fingerprint , made a hand change, and applied a second version to one project.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.