00 · TERMS # No signup flow. Every engagement starts here. Pricing is scoped to the deployment and stated in the first conversation, not discovered in a checkout. [Start the first conversation](https://rensei.ai/pricing#contact) [The runtime is open source →](https://rensei.ai/open-source) 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. 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 Current append-path entries are hash-linked and signed with per-workspace Ed25519 keys; retained history can include legacy unsigned entries. The [verification protocol and key discovery endpoints published](https://rensei.ai/.well-known/audit-keys.json) . [/evidence shows how the chain checks independently](https://rensei.ai/evidence#chapter-02) . - 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. 03 · FAQ ## What gets asked first. ### Is there a self-serve tier? Not yet. Self-serve is on the roadmap. The runtime is not gated: [donmai](https://rensei.ai/open-source) 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](https://rensei.ai/security#deployment) ). ### Who do we talk to? The people who build and run the platform. No sales-development queue, no handoffs. 04 · CONTACT ## Start the first conversation. Tell us about the deployment and the audit pressure behind it. The first conversation includes scope and price. --- Canonical: https://rensei.ai/pricing Site index: https://rensei.ai/llms.txt Docs: https://rensei.ai/docs OpenAPI: https://rensei.ai/openapi.json