Raven

Platform architecture.

Raven is a single platform with three composable layers: Muninn, Huginn, and Sleipnir. They share a common data, identity, and audit substrate.

Three layers, one stack

Every workload on Raven travels through three logical layers. You can adopt one and stop, or run the entire path:

Data plane

The data plane is built around four invariants:

Control plane

The control plane manages workspaces, identity, policy, and quotas. It is the only path through which authority is granted, revoked, or delegated.

Identity

Raven supports SSO via SAML 2.0 and OIDC, and integrates with most common identity providers — Okta, Azure AD, Google Workspace, JumpCloud, and others. Users map to roles; roles map to scoped capabilities.

Policy

Policy is code. Customers define policies in our policy DSL and apply them across workspaces, datasets, agents, and workflows. Policies are evaluated at every relevant boundary — including inside Sleipnir workflows, where they can hold an action pending human approval.

policy
policy "high-impact-actions" {
  applies_to = "field.actions"
  when       = action.impact >= "high"
  require    = "human.approval"
  approver   = role:incident-commander
}

Deployment options

Raven is offered in three deployment modes, in the region of your choice. Choose based on data sensitivity, regulatory profile, and your operational preferences.