Open Source AI Agent Framework for Enterprise
Built for multi-user AI agent deployment, governed by enterprise permissions, and designed for real AI application delivery.
AtlasClaw helps enterprises move beyond personal agents with multi-user AI agent deployment, SSO-based access to enterprise systems in standalone mode, Skill-based system integration, and enterprise-approved model providers.
Built for multi-user AI agent deployment, governed by enterprise permissions, and designed for real AI application delivery.
Personal agents solve personal workflows. AtlasClaw solves enterprise ones.
Personal agents are useful for individuals. AtlasClaw is built for organizations that need a multi-user AI agent, governed execution, system integration, and model control.
Multi-user deployment
Each user configures their own agent stack, tools, and access separately.
One multi-user AI agent deployment can serve users across the organization.
Controlled execution
Unsafe or over-permissive execution is hard to standardize and govern.
Execution stays permission-governed to reduce unsafe operations.
Enterprise system access
Individual tools rarely map cleanly onto internal enterprise systems.
Webhook entrypoints and skill-based Providers let observability, ITSM, OA, CRM, and other enterprise systems gain AI capability without rewriting them.
Model governance
Model access is often ad hoc and chosen per user.
Connect through enterprise-approved LLM providers and controlled deployment rules.
The core enterprise requirements are built in from the start.
AtlasClaw is designed for organizations that want AI capabilities to live inside actual enterprise products, workflows, and system boundaries.
Multi-user AI agent deployment
Run one multi-user AI agent deployment across teams instead of repeating personal setup for every employee.
Permission-controlled execution
Keep execution under authenticated user permissions so unsafe actions are less likely to slip through.
Skill-based multi-system integration
Connect observability, ITSM, OA, CRM, and other internal systems through webhook entrypoints, Skills, and Providers so enterprise software can gain AI capability.
Enterprise-approved model access
Route AI requests through enterprise-controlled LLM providers instead of ad hoc user-by-user model choices.
Two deployment shapes. One execution model.
Embedded Agent Mode
Embed AtlasClaw inside an enterprise application and reuse the host system's identity, context, and UI.
Standalone Agent Mode
Run AtlasClaw as a multi-user AI agent layer where users authenticate through SSO and access enterprise systems under governed permissions.
A clear path from user intent to governed system execution.
The framework stays modular: the core handles orchestration, while providers carry the system-specific contracts that make execution reliable.
- Channels route requests into the AtlasClaw core.
- The agent engine selects skills and orchestrates execution.
- Providers translate work into target-system operations.
- Enterprise systems remain the source of truth for auth and audit.
Click to enlarge Overall architecture
Access channels feed the core, which delegates execution to providers and downstream systems.
Access channels feed the core, which delegates execution to providers and downstream systems.
Click to enlarge Core components
The reusable core centers on the API layer, agent engine, sessions, tools, and provider registry.
The reusable core centers on the API layer, agent engine, sessions, tools, and provider registry.
Provider runtime
Shows how a provider carries auth, skills, scripts, and downstream system execution.
Shows how a provider carries auth, skills, scripts, and downstream system execution.
Choose the way you want to understand AtlasClaw.
Understand the core architecture
See how channels, core services, skills, and providers become one execution model.
Study the provider model
Learn how AtlasClaw packages integrations into reusable provider boundaries.
Explore current and planned integrations
See what exists today, what serves as reference architecture, and where the ecosystem is going.
Step into the code and the docs.
The website gives structure. The repositories give implementation detail. Together they form the open-source entrypoint.