The setting
is an open-source backend platform built on Postgres. Its runs as a hosted service that Supabase manages, or as packaged images that customers host themselves.
Tomorrow's launch promises compete with growth headroom for databases already in production.
Enterprise dates protect planned launches, while unreserved compute protects existing applications from a ceiling they have not yet reached.
Who you’d be doing this for
“We sent our growth dates last month. Now I've got a launch review tomorrow and nobody will confirm whether the database can grow with us.”
Mathilde Svensson · Backend Engineering Lead · a character in this brief
Runs an existing production application whose planned expansion competes with new enterprise reservations.
What is at stake
A region has 120 compute units left against 155 requested for launches and growth. You must weigh firm enterprise dates against headroom for existing applications before reservations lock for 90 days.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- enterprise launch dates vs growth for existing applications
- reserved certainty vs idle compute
- customer-specific allocation vs a predictable admission rule
- forecast demand vs irreversible commitments
Why Supabase
PostgreSQL projects and enterprise launches through AWS PrivateLink depend on the same regional compute, but six launches cannot move elsewhere.
Written with these in mind
Not your kind of problem? 27 more at Supabase, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Supabase. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Product Manager - Administration & Governance (opens in a new tab)
- Define what success looks like, instrument it end to end, and let the data guide what gets built next—from time to first project and self-service adoption to production usage and expansion across the company.
- Define the path from experiment to production, including project ownership, access, and the guardrails that change as an application becomes important to the business.
- Product Manager - Spark (opens in a new tab)
- Shape packaging and pricing with Engineering, Growth, and Finance so Spark is economical at very large scale.
- Some of these projects will be small and short-lived while others will grow and graduate to larger instances on Supabase.
- Product Manager - Strategic Partner Integrations (regular travel to Bay Area) (opens in a new tab)
- Build with what you own, using the surfaces on your roadmap the way a Partner would: standing up an auth flow, calling the Data API, deploying a database, wiring Supabase into another product.
- Product Lead - Infrastructure (opens in a new tab)
- You lead product for the platform under every Supabase product: compute, disks, networking, the API gateway, capacity and regions.
- You also own what enterprises build and buy on top of it: read replicas https://supabase.com/docs/guides/platform/read-replicas, custom domains https://supabase.com/docs/guides/platform/custom-domains, PrivateLink, Bring Your Own Cloud, and the security and compliance controls they need before they sign.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about an irreversible change forced by a fixed date.
A region is nearing CPU and bandwidth limits while the only remaining rack build slot is about to close.
You have to weigh immediate headroom against the production proof needed to place traffic safely.
A fixed contract and launch date require a data-residency deployment option in a named region, but compatibility summaries disagree.
You decide what ships, what counts as proof, and who is eligible.
Mission video slows when simultaneous incidents draw traffic through the existing regional path.
You must weigh a hard-to-reverse cutover against the evidence needed to protect restricted operational data.
The same setting, from another role
Each is set around Supabase’s Supabase Postgres Database, written for a different role. They’re separate briefs, not the same scenario.
Engineers are reopening deployment alerts because the evidence needed to judge severity is scattered.
You must decide what AI gathers, what it may suggest, and where an engineer must review it.
Repeated Nix packaging failures are holding PostgreSQL releases while engineers reread the same build evidence.
You must decide what the system can verify itself and where an engineer must take over.
Recovery investigations repeatedly produce competing explanations from the same logs and failed tests.
You must decide what evidence the system can assemble and what an engineer must still confirm.