Skip to main content

VaultysClaw

VaultysClaw is an open-source, enterprise-grade platform for deploying, orchestrating, and governing AI agents across your organisation. It provides a central control plane that coordinates any number of distributed agent controllers — each capable of using different LLM providers — while enforcing security policies through cryptographically-verified decentralised identity.

Why VaultysClaw?

Running AI agents at enterprise scale introduces problems that most frameworks ignore:

ProblemHow VaultysClaw solves it
Who authorised this action?Every intent is signed by the issuer's VaultysId key — tamper-evident, non-repudiable
Can I trust this agent?Agents carry non-transferable DID identities; impersonation is cryptographically impossible
How do I revoke access?Capability grants and policies are revoked instantly from the control plane and pushed to agents
LLM vendor lock-inPer-agent LLM configuration: OpenAI, Anthropic, Gemini, Ollama, or any OpenAI-compatible endpoint
Multi-team isolationRealms provide hard boundaries between teams; role-based access from member to global admin
Audit trailEvery intent, result, and approval is logged and cryptographically attributable

Core components

Control Plane (Next.js + WebSocket hub)
├── REST API — manage agents, users, policies, workflows
├── Dashboard — live visibility across the fleet
└── WS Hub — bidirectional real-time channel to agents

Agent Controller (Node.js)
├── Identity — VaultysId (non-transferable DID)
├── LLM engine — multi-provider, per-agent config
├── Executor — policy-checked action execution
└── Signer — signs results before returning them

Key concepts

  • VaultysId — The decentralised identity system at the heart of VaultysClaw. Every participant (user, control plane, agent) has a cryptographic key pair. All messages are signed and verified using these keys. See VaultysId Security.

  • Agent — A process running the agent controller package. It connects outbound to the control plane WebSocket hub, receives signed intents, and executes them within its granted capabilities.

  • Intent — A signed, structured request to execute an action on one or more agents. Intents are the primary unit of work.

  • Policy — A signed document pushed from the control plane to an agent that defines which capabilities the agent is allowed to use, resource limits, and optional time windows.

  • Realm — An organisational scope (team, department, project) that groups agents, users, and workflows with isolated access control.

  • Capability — A specific permission granted to an agent, such as file_access, internet_access, or code_execution.

  • Skill — A named unit of reusable agent behaviour attached to a realm. Skills carry Markdown instructions that are automatically injected into agent system prompts at runtime — no code changes required. Skills can be authored manually or imported from the public skills library.

Next steps