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.
A selectable read replica looks like a usable connection.
Keeping replica choices visible preserves discovery, while making connection requirements explicit protects developers from retracing setup.
Who you’d be doing this for
“I picked the replica, then had to go back to our network person to find out whether the app could actually reach it.”
Arunee Prasert · Backend Developer · a character in this brief
Adds read capacity to an application whose database traffic uses AWS PrivateLink.
What is at stake
Seven of twelve developers choose a replica connection their application cannot use. You have to weigh clearer requirements against filtering choices out of the flow, with only one interface change available this week.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- visible capabilities vs constrained choices
- concise guidance vs technical precision
- first-attempt completion vs architectural exploration
- one release slot vs two credible approaches
Why Supabase
Read replicas and AWS PrivateLink meet in the same PostgreSQL setup journey, where database availability and application reachability mean different things.
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 the path from experiment to production, including project ownership, access, and the guardrails that change as an application becomes important to the business.
- Make getting started self-service, whether someone creates a project in Supabase, through an internal developer portal, or with an agent.
- Product Manager - Spark (opens in a new tab)
- Own the product strategy and roadmap for Spark projects, from early MVP through general availability.
- Define the path from experiment to production, including how projects get claimed, upgraded, and grown into the full Supabase platform.
- 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 stand up a read replica, put a custom domain in front of a project, route traffic through PrivateLink and deploy onto BYOC.
- 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 turns on easing someone in at the cost of understanding.
Developers are abandoning service setup when OAuth permissions and environments become unclear.
You must weigh a faster connection path against the access details that protect production workloads.
Guests miss required choices in 19% of observed ordering attempts.
You weigh explicit interactions against defaults within one release slot.
Only 31% of 180 invited developers return in week two after their first agent session.
You must weigh broad repository-context enablement against a deeper workflow for one flagship service.
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.