Governance Control Plane
OpenProdkt Governance helps teams control sensitive actions with a single product workflow.
The product is API-first, dashboard-friendly, and designed to be easy to adopt. Every decision request returns one clear outcome: allow, approval_required, or deny.
Control plane and data plane
- Control plane: API, console, and worker
- Data plane: SDKs and the decision point, which is still TBD
- The data plane only carries metadata and does not handle customer payloads
- Decision outcomes and customer governance state stay in the control plane
What it helps with
- deciding whether a request should proceed
- routing risky actions into an approval flow
- keeping policy and access control visible in one place
- giving teams a consistent API and dashboard experience
Modules
The product is organized into modules so customers can understand each part independently:
- Identity and workspace
- Governance decisions
- Inventory
- Approvals and history
- Access and permissions
- Delivery and integrations
- Console experience
See Architecture for the module map.
Core product loop
The SDKs are part of the data-plane surface. The decision point is planned but not yet implemented.
- Create an organization.
- Sign in with a one-time code.
- Add groups and assets that describe what you want to govern.
- Create policies that define when approval is needed.
- Validate outcomes in Decision Playground.
- Invite members with role-based access.
- Create API keys for application or agent usage.
- Track approvals, usage, and decision history.
Documentation
Product principles
- Keep the workflow understandable without requiring implementation knowledge.
- Keep human sign-in separate from machine credentials.
- Keep the dashboard focused on product actions, not system internals.
Sandbox endpoints
| Surface | URL |
|---|---|
| API | https://api.sandbox.openprodkt.com |
| Console | https://console.sandbox.openprodkt.com |
| API docs | https://api.sandbox.openprodkt.com/swagger |