01 — Overview
Most internal tools start with a Postgres table and a question nobody can answer without SQL. Connect the database once, then describe the tool in a sentence: an order lookup for support, a refund queue for finance, a stock adjuster for the warehouse. The Bench reads your schema, including foreign keys and enums, and builds screens that match it. Start with one table and one team, then add screens to the same app as people ask for them.
Every write goes through a parameterized query that the Logbook records with the user, the values and the time. Add a Sign-off to any write that should never happen alone, like a balance change or a deleted account. Read replicas can serve heavy screens while writes go to the primary. Chamfer works with self-hosted Postgres and with managed hosts such as Amazon RDS, Aurora, Cloud SQL, Azure Database for PostgreSQL, Supabase and Neon.
02 — What you can do
Schema-aware builds
The Bench reads tables, keys and enums, so dropdowns, joins and validation match your data.
Writes you can trace
Inserts, updates and deletes run as parameterized queries, each logged with who, what and when.
Row-level access
Limit each role to the rows it should see, like a region or account, with a rule in plain English.
03 — FAQ
Before you connect PostgreSQL
Does Chamfer copy our Postgres data?
Which Postgres hosts can we connect?
Can a prompt change our production tables?
How do Chamfer permissions relate to Postgres roles?
04 — Pairs well with
Teams often connect these next
05 — Used in
Give support, finance and ops a safe way to look up and change production records, without console access.
Dashboards on warehouse data that people can act on, with access by team, region or site written as one rule.
Route refunds, discounts, vendor changes and releases to a named approver, with the diff and the decision on record.
Turn the shared sheet everyone is afraid to touch into an app with validation, roles and a named owner.
