About Chamfer
Named for the cut that makes a part safe to handle
We take the sharp edges off AI-built apps before anyone relies on them.
2021
Founded in Brooklyn, New York
140
People in New York, London and Lisbon
1,400
Companies building on Chamfer
46
Countries with a Chamfer app in production
What customers built first
Four teams, four industries, one set of controls on every app.
Why we named it after an edge
Our founders’ letter on the 45° cut a machinist puts on every part, and why AI-built software needs the same finishing step before a company can rely on it.
Dana Okafor
Finance Operations Lead, Kettleby Freight
We replaced 14 spreadsheet processes in one quarter, and every app had a named approver before it went live.
Marit Solberg
Head of IT Risk, Halden Mutual
Our auditor asked who could see claims data. We exported the answer from the Logbook before the meeting ended.
Ines Albrecht
Support Operations Lead, Tessaly
We described our refunds queue in one paragraph on Monday. By Thursday, 40 agents were working it behind SSO, and every action was logged.
Callum Reid
Head of Field Operations, Brackwater Energy
Our inspection app went from prompt to 60 technicians in nine days, and it runs Onsite inside our own network.
Theo Marchetti
VP Engineering, Quenby
Engineering stopped owning admin panels. We review the Specs, approve the permissions and get back to the product.
Priya Raman
Director of Data, Fennimore Health
Clinic managers build their own rota tools on Stockroom, and the row-level rules mean nobody sees a patient outside their site.
Customers set the spec
Most Chamfer features began as a request from a team that runs something physical: a loading dock, a clinic rota, a round of turbine inspections. We sit with those teams before we write the first line of code.
Today 1,400 companies build on Chamfer, from a 3-person ops team in Lisbon to a 31-clinic network in Colorado. Every one of their apps has answered to the same four controls since its first version.
Small team.
Close to the work.
Everyone at Chamfer ships something in their first month, from support engineers to our finance lead. Our own expense approvals, hiring pipeline and on-call rota run on Chamfer, under the same Tolerances our customers use.
We hire people who like finishing things: engineers who read a Logbook closely, designers who care about the empty state, and security staff who would rather say yes with conditions than no.
Values
How we decide what ships
01
Finish the edge
We don’t release the rough version and promise a fix later. Every feature ships with its permissions, its log entry and its docs.
02
Show the receipts
Every number on our site has a source, and every change in our product has a name. We hold ourselves to the Logbook we sell.
03
Sit with the operators
Each quarter our engineers spend a day on a customer’s floor: a dock, a claims desk, a clinic front office. The roadmap comes back with them.
04
Respect the reviewer
The person who can say no is a customer too. We write for the security lead as carefully as we write for the builder.
The people behind the Bench
Backed by people who’ve run operations
We raised a $42M Series B in 2025, led by Tidewright Ventures, to take Chamfer Onsite into regulated industries.
Plus 30 angels who have run ops, security and finance teams