Hands-on Labs
Guided labs for building with Dome
Every tutorial runs in a sandbox workspace and ends with a governed call you can verify in the audit trail. Follow the guided path in order, or jump to the track that matches your role.
Get started
Four tutorials, in sequence. Each one builds on the workspace the one before it left behind.
Govern your first agent
Allow, redact, and deny tool calls from Cursor, Claude, or curl.
Call a model through a pool
Route chat through a model pool with failover and server-side keys.
Build a governed app
Wire model and tool calls in one app. Watch allow, redact, and deny.
Govern per end user
Give each user different tool access and answers from the same agent.
Choose your role
What developer, security, operator, and platform admin each own on Dome, with a guided sandbox walk for each.
Developer
Register an agent, call tools through a Gateway, and confirm allow and deny.
Security
Author and simulate Cedar, redact sensitive fields, prove denials, and export evidence.
Operator
Attach tools, expose a Gateway, grant access, and watch audit.
Platform Admin
Set who may administer Dome, check platform health, and export an audit snapshot.
Production
Take what you built in the sandbox and run it for real.
Use Dome as an MCP gateway
Let Cursor, Claude Code, or Codex sign in with your own Dome account and call MCP tools, individually audited.
Use Dome as a model broker
Hold the provider key server-side and let Cursor, Claude Code, or Codex call any model, not just their own.
Govern callers with OIDC
Authorize a shared assistant from each employee's verified identity, then inspect every caller.
Deploy an always-on agent
Build and deploy a governed HTTP service that stays ready for requests.
Deploy an event-driven agent
Build and deploy a governed handler that wakes for an event and exits.
Examples
Working applications you can clone and adapt.