Build an explicit
authorization boundary.
Start with a working local policy. Then choose your integration and make its trust boundaries visible.
Build and operate
Your first decision ↗
Build, narrow a policy, compare allow and deny, and verify an audit chain.
Local development ↗
Set up the pinned Rust, Node, pnpm, protobuf, Docker, and clean-checkout workflow.
Authorization & policies ↗
Understand request inputs, Cedar semantics, schemas, and policy lifecycle.
Policy authoring ↗
Write, validate, simulate, review, activate, and safely roll back Cedar policies.
Architecture & deployment ↗
Choose embedded, sidecar, or shared PDP boundaries.
Production deployment ↗
Deploy the PDP and console with Docker and Kubernetes, including health and storage boundaries.
Kubernetes operations ↗
Apply, verify, back up, upgrade, and roll back the supported deployment topology.
Console deployment ↗
Configure OIDC, roles, sessions, shared rate limiting, and operator workflows.
API, SDKs & CLI ↗
Use current request formats and integration signatures.
API reference map ↗
Find the Rust, TypeScript, CLI, HTTP, protobuf, and configuration surfaces.
Identity & delegation ↗
Separate standalone features from verification primitives.
Audit & observability ↗
Verify evidence, export records, and connect telemetry.
Configuration reference ↗
Find settings and the exact surface that reads them.
Operations & troubleshooting ↗
Diagnose policy, network, identity, and audit failures.
Troubleshooting guide ↗
Resolve readiness, auth, reload, audit, console, and delegation failures.
Backups & retention ↗
Preserve policy, audit, secrets, and recovery evidence.
Upgrades & rollback ↗
Roll out immutable images and recover safely in Kubernetes.
Incident response ↗
Contain authorization failures and preserve verifiable evidence.
Security model ↗
Review enforcement responsibilities and current limitations.
Compatibility policy ↗
Understand supported runtimes, deployment modes, and breaking changes.
Brand system ↗
Use the selected identity and semantic color system consistently.
OSS governance ↗
Contribute, report security issues, and run the release gate.
Project status
These guides map to the checked-in release surface. The security model and production guide state the supported topology and the boundaries that remain operator-managed. See the changelog, support policy, and security response process.