Pilot and packages
The reader is free. The writer is what you pay for.
Every origin receipt you send reaches someone who can check it at no cost, forever. Companies pay for the side that signs orders and governs agents. The pilot program is opening, and we're looking for design partners.
The pilot
30 days. One workflow. One policy. One counterparty.
Small on purpose. A pilot ends with origin receipts a real counterparty has checked, and a written result you can take to your own customers.
- One workflow: an agent task on your OpenShell whose output leaves the building.
- One policy under orders: signed by your officer; nothing else installs.
- One counterparty: a customer, auditor or partner who receives the output and verifies its receipt.
- The receipts and the record: in your store, exportable, free to keep.
- A written result: what was refused, what verified, what each line showed, what to do next.
- An OpenShell environment (a workstation or a test cluster is enough).
- An engineer for setup, and an officer to sign the order.
- One counterparty willing to check what they receive.
- Candid feedback on what the receipt should say, and to whom.
Week 1 · Install and authorize
Add the two OpenShell extensions. Your officer signs the workflow's policy as the first order. An unsigned install is refused, on your own system.
Week 2 · Run
The workflow runs unchanged, and every result carries its origin receipt.
Week 3 · Verify
Your counterparty checks receipts with the free verifier, offline, with nothing to install.
Week 4 · Write it up
A written result, and a decision about what comes next.
Packages
Five ways in.
Pricing is set with design partners during the pilot program; nothing on this page is a price list.
Rootz Verify
The verifier, in a browser and on the command line. Offline, no account.
Free, always. Never gated.
Rootz Receipts Developer
Order signing, the interceptor, the middleware and a local session log, for one OpenShell sandbox on a workstation.
Free for one sandbox
Rootz Receipts Pilot
One policy under orders, one agent workflow issuing receipts, one counterparty verifying, and a written result.
Fixed scope, agreed up front
Rootz Receipts Enterprise
On your OpenShell or Kubernetes: integration with your company's registered keys, hardware-key order signing, a receipt store, and support.
For governed agents across teams
Rootz Receipts Cloud
Managed OpenShell with Rootz Receipts inside a confidential VM Rootz cannot read into. We run it, and the Process line is designed to show that Rootz could not read into it or tamper with it.
Follows the pilot program
What stays free
Verifying a receipt. Exporting your own receipts and logs. The number of receipts a recipient checks.
Priced: the writer side only
Seeking design partners.
Tell us about the OpenShell workflow whose output leaves your building, and who receives it.