00 · TERMS
No signup flow. Every engagement starts here.
Rensei is in its design-partner phase. Pricing is scoped to the deployment and stated in the first conversation, not discovered in a checkout.
REC 00 ▸ sha256:ff0c…dc24 ▸ prev 985c…0579 ▸ build 2026-06-12T03:34Z
01 · PHASES
What the first ninety days look like.
Each phase produces artifacts you keep, and the final phase sets the ongoing terms; you keep the artifacts if you walk.
Phase 01
Map the environment
The first conversation covers your agent surface, the systems it touches, and the audit requirements your compliance team already carries. Cedar policy scope and egress boundaries are drawn here, and the price is stated here.
Phase 02
Run a structured pilot
A bounded deployment against real work in your environment, typically a quarter. The pilot produces the six deliverables below, on your infrastructure, reviewable by your auditors.
Phase 03
Govern ongoing operations
After the pilot, the policy set, the audit chain, and the provenance records stay in place and keep accruing. Ongoing terms are scoped from what the pilot measured.
REC 01 ▸ sha256:c9a0…8e89 ▸ prev ff0c…dc24 ▸ build 2026-06-12T03:34Z
02 · DELIVERABLES
Six deliverables, and you keep them if you walk away.
Six deliverables ship with a pilot.
- 01
Cedar policy set
Policies authored for your tool surface and data boundaries, evaluated in the hot path of every agent action.
- 02
Hash-chained audit trail
Every event signed with per-workspace Ed25519 keys, with the verification protocol and key discovery endpoints published. /evidence shows how the chain checks independently.
- 03
Fail-closed egress configuration
Per-callsite enforcement on every outbound tool call; a missing or failed ruling denies by default.
- 04
Provenance records
Every decision bound to the model version, prompt, context, and policy ruling that authorized it.
- 05
Framework mapping
A documented mapping from the deployed posture to the frameworks your auditors name, with each status declared.
- 06
Audit-readiness review
A structured walk of the audit trail with your compliance team at pilot close.
REC 02 ▸ sha256:2ee9…64b7 ▸ prev c9a0…8e89 ▸ build 2026-06-12T03:34Z
03 · REFERENCE
Design-partner reference.
Design partners · In evaluation
Design-partner reference: evaluations are underway and nothing is signed. An anonymized reference will be published here the day a pilot converts.
REC 03 ▸ sha256:2d7c…d095 ▸ prev 2ee9…64b7 ▸ build 2026-06-12T03:34Z
04 · FAQ
What gets asked first.
Is there a self-serve tier?
Not yet. Self-serve follows the design-partner phase. The runtime is not gated: donmai is MIT and installable today.
What does a pilot cost?
Scoped to the deployment and stated in the first conversation. No surprise line items.
How long is a pilot?
Typically a quarter: map, run, review.
What do we keep if we walk away?
Everything the engagement produced: the Cedar policy set, the audit trail and its keys, the egress configuration, provenance records, and the mapping documents.
Do you run on-prem?
Cloud today. VPC and on-prem are on the published roadmap, in that order (see /security, deployment).
Who do we talk to?
The founder. One person, one inbox; we respond to every message.
REC 04 ▸ sha256:eaed…4f30 ▸ prev 2d7c…d095 ▸ build 2026-06-12T03:34Z
05 · CONTACT
Start the first conversation.
Tell us about the deployment and the audit pressure behind it. The first conversation includes scope and price.
REC 05 ▸ sha256:c55e…a74c ▸ prev eaed…4f30 ▸ build 2026-06-12T03:34Z