Sanctum Runtime: free start guide (console + SDK in one session)
Sign in, connect your first agent, gate one real action, and approve it from the console — a practical path from zero to production-ready controls.
You do not need a procurement cycle to validate runtime trust. Sanctum is open-core (MIT SDK) with a hosted console for operators — sign in, connect one agent, and gate one action in a single working session.
Key takeaways
- Console handles policies, approvals, fleet pause, and audit without custom admin UI.
- SDK stays in your repo; policies can be tuned from the console as you learn.
- Mobile PWA lets you approve held actions without building an app.
Implementation checklist
- Open console.sanctumruntime.com and sign in.
- Agents → create agent → copy connect snippet.
- Shield Rules → add verify on your riskiest action name.
- Trigger the action from dev → approve on Overview.
People also ask
How fast can we get value from Sanctum Console?
Most teams gate their first high-risk action the same day: create an agent in Agents, add a Shield Rule, and approve a held action on Overview. Open the console at console.sanctumruntime.com to start free.
Do we need a sales call before trying it?
No. Sign in, connect an agent with the SDK snippet, and run verifyAction on a staging action. Upgrade when you need fleet controls, compliance exports, or higher volume — not to prove the workflow.
What should we buy first — gateway or runtime trust?
Start free at the console, then add npm install @sanctum-runtime/sdk when you are ready to wire verifyAction in code.
Related: Sign up and run your first AI agent approval workflow in 5 minutes, Your first production agent gate this weekend (checklist).
More: all posts · runtime trust layer · open Sanctum Console