Cloud & backend

Supabase development

How does AonHive use Supabase?

Supabase development for Postgres-backed product foundations.

Supabase is the Postgres foundation on Sevenco, TripGlide, and Reycona. On Sevenco the ride row is the record both apps write, and the site reads operational_geofence from app_settings, using a fallback ring when that row is missing. On TripGlide, members, messages, expenses, and photos hang off the trip, and row-level security sits on those tables. On Reycona the product row is the price. checkout_cart writes the order from the cart, and each account reads only its own bag, wishlist, and orders. On the Sevenco admin desk get_admin_dashboard_stats is the aggregate, and is_admin() is the gate for both staff roles. The OpenAI key for the TripGlide assistant stays in the edge function.Discuss this stack

How we use it

Postgres is the record. Access is a policy.

  1. 01

    Put the rule on the row

    A policy decides who can read a public trip, a private trip, or a ride. The client cannot render a row the database would refuse.

  2. 02

    Call the database for the decision

    A fare, an accept, and a join are writes with a condition. Two phones can tap. One row wins.

  3. 03

    Keep privileged work in a function

    A service key does not ship in the app. An edge function holds it and checks the caller's token before it reads or calls a model.

Supabase

Bring the system this has to fit.

Tell us the product, the estate you already run, and what your team needs to own. We will say whether this belongs in the stack.