Three steps, each priced before it starts. The Agent Exposure Audit at a fixed fee. A pilot that turns the findings into policy, with a letter of intent that locks your rate. Then an annual subscription quoted to fleet size, in the band you already budget for endpoint protection. No usage metering, no token billing, on your own machines at every tier.
Interpose in transparent mode on your Claude Code fleet, deployed inside your boundary, ending with the Rollout Evidence Report: the signed record of what ran, what reached what, and what policy would have caught. The fee is fixed and agreed in writing before we start, and the report is yours whatever you decide next.
An annual subscription quoted to the size of the fleet, in the band you already budget for endpoint protection. Central policy the security team owns, the console across every session, the signed trail, quarterly evidence reports, support and SLA. The pilot between audit and subscription locks this rate by letter of intent.
For consultancies and build partners shipping agents to their clients. Deployed inside client engagements on their infrastructure, one integration carried across every client, a share of the engagement instead of a per endpoint bill. Set per partner.
Custom integrations are scoped and quoted separately from the license. Claude Code is the live integration today.
A developer tool protects the developer who chose it, one machine at a time. A control covers everyone, from a policy none of them can edit, with evidence the security team holds.
The audit is a fixed fee agreed in writing before we start. The pilot that follows is agreed the same way, and a letter of intent signed during it states the annual rate you would pay in production. That number does not move as the fleet grows.
Annual, quoted to the size of the fleet, in the band security teams already budget for endpoint protection. Volume pricing applies at scale. We are early and price each engagement from the audit and pilot, so there is no public list price.
Those are utilities a developer installs for themselves, and they are good at that job. Interpose is a control a security team deploys over everyone: policy pushed from an admin owned path that no developer or agent can edit, a fleet console, quarantine with forensics, and signed evidence a reviewer can verify. The price gap is the difference between a tool and a control.
No. Interpose is deployed by Tuent during a pilot, inside your boundary. There is no public download.
On your machines, under your keys, at every tier. Optional model escalation uses an endpoint you host, and credentials never escalate. Nothing about your agents, code, or actions reaches Tuent.
A founder on the other end during the pilot and the first term. Response times and an SLA are written into the enterprise agreement.
Thirty minutes to scope the audit. A fixed fee in writing, two weeks inside your boundary, and the report is yours. The pilot that follows locks the production rate by letter of intent.