For Engineering teams
Admin panels off the backlog, with every change on record
Describe the panel your team keeps asking for. Chamfer builds it on your production database with roles, row-level access and a Logbook in place, and engineers review each release instead of writing it.
Scoped to the job
Each role gets the records and actions it needs, and nothing else. Support can edit an address without seeing card data, and only finance can issue a credit.
Built on live data
Panels read and write your own Postgres, MySQL, MongoDB or API directly, so nobody works from an export that was out of date by lunchtime.
Reviewed like code
Every change ships through a Sign-off with a diff, and apps can sync to your GitHub repo, so engineers review panels the way they review everything else.
01 — In production
How Quenby took admin work off its product roadmap
“Engineering stopped owning admin panels. We review the Specs, approve the permissions and get back to the product.”
Theo Marchetti
VP Engineering, Quenby
Read the story
02 — Example apps
Panels that replaced a ticket to engineering
03 — What it includes
What every Chamfer admin panel ships with
Search across sources
Find a customer by email, ID or phone across Postgres, Stripe and your own API from one search box.
Forms that match your schema
Field types, enums and foreign keys come from the database, so a form can't submit a value the table would reject.
Bulk actions with a preview
Update hundreds of rows at once after checking exactly which ones will change. Anything above your cap waits for approval.
Masked by rule
Write "never show full card numbers" once as a Spec, and every panel that touches the column masks it.
Undo from the Logbook
Every write records the old and new values, so a mistaken edit can be found and reversed in minutes.
Staging before production
Build against a staging database, then promote the panel to production with a named approver.
05 — FAQ
What teams ask about admin panels
How long does a first admin panel take?
Do support agents need database access?
Can engineers edit the generated code?
How do we stop someone deleting the wrong record?
Can one panel combine several data sources?
What happens when our schema changes?
