Fixed price · One week · Your infrastructure
I move apps built on Lovable, Bolt and v0 from Supabase Cloud onto a server you own. Same database, same policies, same front-end code. The bill stops.
Scope
auth.uid() reads a session variable; recreate that correctly and every policy you wrote keeps working word for word.Evidence
A multi-tenant B2B SaaS with real customers: 99 tables, 10,407 rows, 228 RLS policies, 230 foreign keys, a non-Latin interface. Schema rebuilt twice by independent routes and compared. Zero orphaned rows.
Along the way I found a storage policy that had been exposing every tenant's documents to anyone holding the public key — for seven months. Reading your policies carefully is part of the job, not an extra.
The full technical write-up is here, including the three failures that produce no error at all. Read it before hiring me; it will tell you more than this page can.
Your side
Downtime is a few minutes, scheduled when you choose. Your old project stays untouched until you tell me to switch, and switching back is changing one hostname.
Fit
A working product with real users, a Supabase bill somewhere between a few hundred and a few thousand a month, and a founder who would rather pay once than keep paying monthly.
And who it isn't for
You have nothing to save yet. Come back when the bill is real.
I hand you infrastructure you own and operate. I can stay on for support, but the point of this is that you stop renting.
Self-hostable, but it is a separate piece of work and I will quote it separately rather than pretend it comes free.
Getting started
Send me your table count, your monthly bill, and whether the app talks to the database directly from the browser. That is enough for me to quote a fixed price, usually the same day.
Philip Sagalovich. I run three Kubernetes clusters and around twenty services in production across Postgres, MySQL, Redis and object storage.