Free
$0 forever
For anyone who sets a standard or checks a proof.
- Set standards from supported requirements, read back in plain English, signed in your browser
- Check any result, no account
- The demo, and the open gateway on your own machine
Start
Free to set a standard. Paid to meet one.
Setting standards and checking results are free for everyone, forever. The work that has to prove itself to someone else pays per workflow: one standard in force, with unlimited agents, approvers, and recipients, support included. Founding-team pricing; scope and terms are agreed before activation.
Team
$200 per workflow per month
For work that has to prove itself to someone else. Fourteen days free.
A workflow is one standard in force: one recurring kind of work under one set of requirements, however many agents or people do it.
- Checks enforced and recorded for every action in the workflow
- Results anchored in the public log, so a recipient can check they existed when you say
- Check links you can send to anyone; approvers and recipients unlimited and free
- Email and call support on business days
The fourteen days start when your first standard is signed. We set the first teams up by hand while self-serve billing is built, and we count the trial as working once a recipient, inside or outside your organisation, has checked a result.
Design partner
$500 per month, month to month
The first five teams. Team for one workflow, plus us in the room. Cancel any month.
- Everything in Team, for one workflow
- A weekly working session with the founder
- A say in what gets built next
- A case study you approve before anything is published
- Custom integration scoped and priced separately
Setting up
Three plain steps.
- 1
Write the standard
Choose the requirements that matter: limits, named people, deadlines, the evidence you want. Legate reads the standard back in plain English and lists the checks it supports; you confirm and sign with a key you keep. Write one now.
- 2
Point the work at it
Install the open gateway where the agent runs, or compare two records in the browser. Start in observation. Enforcement changes the execution path only on the routes you switch on, and the result names those routes.
- 3
Share the result, keep the data
Send the result, not the data. You review what is released before it goes. The other side checks it on its own machine, no account needed.
Details: what installs where, and what it touches
The gateway is an open-source process that sits between an agent and its tools. It reads your signed standard, checks each tool call against it, and writes proofs locally. Raw prompts and payloads never need to leave your machine. Comparing records installs nothing. Anchoring (Team) sends a digest of each proof to a public log, never the proof itself.
npm install -g protect-mcp protect-mcp trial --open
A tool call that bypasses the gateway is not governed, and the proof says so: coverage is declared per route, never assumed. The gateway is MIT licensed on npm.
Details: connect a source system
For a team that has started, an evidence source (a CSV export, an API, or a signed file delivery) can be described once so its proofs carry the source's own confirmation. Nothing is trusted until a reviewer confirms the mapping. Prepare a source connection.
Details: what a design-partner engagement covers
One real question your team cannot close today, bounded to one period and one source. Week one fixes the standard with the person who must rely on the answer and connects one read-only source. Week two produces the proof, tests the evidence for staleness, gaps, and alteration, and ends in a signed decision: accept, reject, or request inspection. A signed "not established" is a valid outcome.
Historical, read-only evidence. Point in time, never continuous. Not continuous assurance. Enforcement on live routes is a separate, later step you switch on.