03 Services

Backend and infrastructure

Postgres schemas and migrations, authentication, edge functions and account management. We build access rules around each product and test how data is separated between accounts.

01 ScopeSupabase, Postgres, edge functions, row-level security.

What this covers.

We build and operate the backends our products need: Postgres on Supabase, authentication, edge functions and subscription webhooks. The architecture follows the product, from an app that works without an account to one that needs synchronized data across devices.

Access control is part of the schema. A mobile app's client key is public, so private user data needs policies that enforce who can read or change each record. We develop row-level security alongside the data model and check both permitted and denied requests.

The rest is unglamorous and load-bearing: migrations that roll forward on a live database with users on it, an account deletion path that actually deletes, and a schema that survives the day the product changes shape.

  • Postgres schema and migrations
  • Auth, accounts and account deletion
  • Edge functions and webhooks
  • Row-level security audited row by row
02 ExamplesFrom the apps we build and run

Where this has already been done.

Bite AI, a food log that has to survive a new phone

Every meal is tied to an account rather than to a device, which is the difference between an app people use for a week and one they keep for a year. That is Postgres, auth and sync on the server, with HealthKit on the phone so the same numbers also land in Apple Health.

Bite AI

Order Fit, the data lives on the server

Order Fit matches restaurant meals near you against a calorie target, so the catalog behind it sits on the server and can change without an App Store release. The app asks a question; the backend answers it. That split is a decision made at schema time, not a refactor.

Order Fit

Row-level security written for a leaked key

Policies are written around each table's purpose, including reads, writes and deletes. For private user data, access is tied to the authenticated owner rather than possession of a client key.

Account deletion that actually deletes

Apple requires an in-app way to delete an account, and signing the user out does not count. We build the server half — the rows, the stored objects and the subscription record — so that what the app promises and what the database does are the same thing.

03 ProcessStart to ship

How we run it.

  1. 01

    Model the data first.

    Tables, relationships and the queries the app will actually make, before screens get built on top of a shape everyone regrets in month three.

  2. 02

    Write the policies with the schema.

    Row-level security goes in table by table as the schema is written, not in a pass at the end when nobody remembers what each column was for.

  3. 03

    Ship changes as migrations.

    Every change is a migration that can be applied to a live database with users on it. Nothing gets fixed by hand in a console and forgotten.

  4. 04

    Wire the edges.

    Edge functions and webhooks for the work a phone cannot do or cannot be trusted to do: purchase verification, scheduled jobs, and anything holding a secret.

  5. 05

    Attack it before launch.

    Every policy is exercised with a key that should be refused. A policy nobody has tried to break is a policy nobody has tested.

04 QuestionsAnswered before you ask

Common questions.

Can you work with a backend we already have?
Yes. We use Supabase for the products that need a hosted backend, and can work with an existing API or a backend maintained by your team.
Our app is already live. What should we check first?
Whether your client key can read another user's rows. Assume the key is public, because it is: a shipped binary can be unpacked by anyone. If the answer turns out to be yes, everything else on your roadmap is less urgent than that.
Whose accounts does this run in?
Yours, if you want it that way. We can build inside your own Supabase organization and your own service accounts from the first day, so there is nothing to migrate and no credential to hand over later.

Tell us what you are building.

A paragraph about the app, the feature or the thing that is stuck is enough, plus roughly when you need it and the budget range you are working with. One piece of this on its own is fine, and so is the whole thing. Our team reads every message and answers, usually within one business day.