Context from your schema
Generate the context agents need from the database model you already trust.
Synctable generates typed rows, Zod validation, request clients, and baseline UI from one model—then keeps reads, writes, and CDC events on the same governed path.
Generate the context agents need from the database model you already trust.
Keep people, apps, and agents current without hand-rolled reconciliation.
Give agents deliberate, observable actions—not raw access to production data.
1create table public.users (2 id uuid primary key,3 email text not null,4 plan text not null,5);1{2 "type": "User",3 "id": "6b8f1c9e-…",4 "email": "ada@example.com",5}1mutation createInvoice($input:2 invoice_create_input!) {3 createInvoice(input: $input) {4 id status total5} }1POST /actions/createInvoice 2002auth user:ada@example.com ok3check policy:invoice.create ok4write invoices okChoose your path
Run the open-source runtime on your own Postgres. When the operational work becomes the constraint, add managed control and governance without changing the model.
For teams that want to operate their own boundary.
For teams that want help operating the runtime.
No. Postgres stays authoritative. Synctable adds the runtime boundary around it: typed context, correct sync, and governed actions for people and agents.
In Postgres, where the engine expects it. Synctable generates the typed clients, schemas, and action contracts around your model—the TS, server, and frontend stay thin.
Yes. Start with typed context, add realtime sync, then introduce governed actions where a bad write would be expensive. The public packages compose without forcing a rewrite.
Yes. The open-source runtime and core packages are the supported path today. Hosted signup and billing stay out of the product until their separate launch gates pass.
Bring the workflow that cannot be allowed to drift, leak, or corrupt data.