Governance first. Decisions stay local.

PermDock Cloud is a decision log sold as evidence, a hosted AuthZEN ADS, an approval inbox, and a SCIM relay into a DirectoryStore you own. Every hosted capability has an in-process default in the MIT package.

Open Cloud Cloud adapter

Decision log as evidence

Signed batches with typ permdock-decisions+jwt. A sink never changes an outcome.

Approval inbox

Humans resume. The token is bound to permission, resource, subject and actor.

SCIM relay

Provisioning into a DirectoryStore you own. The Cloud holds no authoritative directory copy.

Human gates stay in the run

The same approval-required Decision the agent runtime already halted on. Cloud hosts the inbox; decide() still runs in your process.

Refused MCP scope stays refused

A missing grant is denied, not a boolean false with no reason. The table is an illustration of protectServer, not a live PDP.

PermDock Cloud

Governance when you want it

Dashboard at app.permdock.com. API at api.permdock.com. Read-only MCP at mcp.permdock.com. The in-process defaults stay in the MIT package either way.

Open Cloud