One mature, open database that every cloud runs managed, that the client can move between clouds, and that handles the record, the audit log and the reports without a second system.

Can our own staff query it?

Yes, with a read-only role, from the tools they already use. Reports in the system are built on the same tables, so a figure on a report can be traced to the rows it came from.

What about Supabase for client systems?

Supabase is a managed Postgres with auth and an API; it runs KYN’s own dashboard and some demos. Client production systems default to RDS or Cloud SQL inside the client’s cloud account; Supabase is used where the client chooses it.

How are deletions handled?

Rows other rows depend on are never deleted by an agent. A deletion request waits for a person, is logged with the actor, and backups cover the window if a mistake is made.

One record, in Postgres, in your account.

A customer, an order and a stock item each live once, in Postgres, in the client’s account. Every agent reads and writes through a role scoped to its job. Migrations are versioned and reversible. A person approves any deletion.

Get a quote →All integrations

The agent reads
- The tables each role is granted, nothing else
The agent writes
- Rows through the application, with the actor recorded on every change
- Versioned schema migrations
- Nightly exports where the client keeps a copy elsewhere
A person approves
- Deleting rows that other rows depend on
- Dropping or renaming a table
- Granting a new role

Setting it up.

Where	RDS on AWS, Cloud SQL on Google Cloud, or Supabase where the client prefers a managed Postgres with auth; always in the client’s account.
Roles	One role per agent and per app surface; row-level security where more than one client or department shares a database.
Backups	Managed, 35 days by default, restore tested on handover.
Access from outside	Through a pooler or a bastion; never a public database port.

Builds that use it.

Eleven systems to three, one AWS account →Receipts, expense claims and GST →Reply desk →Build library →

Questions buyers ask

Why Postgres?: One mature, open database that every cloud runs managed, that the client can move between clouds, and that handles the record, the audit log and the reports without a second system.
Can our own staff query it?: Yes, with a read-only role, from the tools they already use. Reports in the system are built on the same tables, so a figure on a report can be traced to the rows it came from.
What about Supabase for client systems?: Supabase is a managed Postgres with auth and an API; it runs KYN’s own dashboard and some demos. Client production systems default to RDS or Cloud SQL inside the client’s cloud account; Supabase is used where the client chooses it.
How are deletions handled?: Rows other rows depend on are never deleted by an agent. A deletion request waits for a person, is logged with the actor, and backups cover the window if a mistake is made.