Buy infrastructure without outsourcing the rules
Use Supabase when its building blocks fit the product and the team can own the application rules around them. Add a custom backend where business operations need an explicit boundary. These choices can coexist; treating them as competing products produces an unhelpful comparison.
Supabase provides a full Postgres database, with services such as Auth, Storage, Realtime and Edge Functions built around it. That describes infrastructure capabilities, not a completed business application. Supabase database overview
An illustrative booking product might use that database while keeping reservation rules in a separately deployed service. The meaningful question is not whether the backend is custom. It is where a booking becomes valid, who may change it, and how that decision is tested.
Start with the permission boundary
A simple interface can conceal a complicated permission model. Account membership, delegated administration and access to shared records need a consistent policy, regardless of which platform stores the data.
Supabase documents Row Level Security as the mechanism for securing database access from clients. Its presence does not mean the correct policies appear automatically. Supabase Row Level Security
Write permission tests from the user's perspective. An account member should not gain access by changing a record identifier. A removed member should not retain access through a background operation. Decide which actions are safe for direct client access and which require a server-owned operation.
The SaaS tenancy guide is a useful companion: a tenant identifier in a table is not the same thing as an enforced boundary.
Locate transactions and external side effects
A custom service becomes useful when an operation coordinates systems, applies complex policy or must be retried without repeating a business effect. The purpose is to make that behaviour explicit, not to hide a database behind unnecessary endpoints.
Consider a hypothetical account cancellation that must revoke access, stop future charges and schedule deletion. A database update alone does not express every outcome. The system needs durable progress, ownership of retries and a clear response when an external service is unavailable.
Putting this coordination in code also creates responsibilities: deployment, observability, incident response and regression tests. If the application is straightforward record management, adding a separate service for every operation may purchase complexity without adding a useful boundary.
Compare operational ownership, not labels
Managed infrastructure and self-hosted infrastructure distribute work differently. Supabase's self-hosting documentation explicitly assigns maintenance, backups, security and monitoring responsibilities to the operator. Self-hosting is an option, not automatic freedom from operational cost. Supabase self-hosting guide
A custom backend on managed services still depends on those services. A self-hosted platform still depends on people capable of restoring it. Compare recovery procedures, update ownership, access controls and realistic staff availability before comparing subscription charges.
Portability deserves a specific rehearsal. Exporting a database does not establish that authentication flows, file references and application jobs will work after a move. Write down the dependencies that travel separately.
Draw the boundary this week
Select a representative business operation and diagram its reads, writes, permissions and external effects. Implement the smallest credible version and test unauthorised access, a repeated request and an interrupted dependency.
Then choose a division of responsibility: platform-managed primitives, application-owned rules and explicitly operated services. Name an owner for migrations and restoration, even if a provider performs the underlying backups.
Clodron's web platform engineering can include Supabase where it fits. The recommendation is to own the product's behaviour while buying useful infrastructure, not to rebuild infrastructure for the sake of calling the result custom.
