Deployment

Choose the deployment shape, then wire providers.

AtlasClaw supports two practical shapes: embedding into an existing product, or running as a standalone agent layer above multiple systems.

Modes

Embedded and standalone.

Embedded deployment

Best when an existing enterprise application wants to add AI capability without moving users into a separate product surface.

Standalone deployment

Best when the enterprise needs one multi-user AI agent entry point above multiple systems.

Configuration basics

The runtime is anchored around providers_root.

{
  "providers_root": "../atlasclaw-providers/providers",
  "service_providers": {
    "jira": {
      "cloud": {
        "base_url": "https://company.atlassian.net",
        "token": "${JIRA_API_TOKEN}"
      }
    },
    "smartcmp": {
      "prod": {
        "base_url": "https://cmp.corp.com/platform-api",
        "cookie": "${CMP_COOKIE}"
      }
    }
  }
}

Operational notes

Preserve governance boundaries.

Use `providers_root` to load provider folders from the external providers repository.
Keep secrets in environment variables, not committed JSON.
Use webhook mode for fire-and-forget system-to-system invocation with constrained skills.
Keep target-platform auth and audit in the provider and the downstream platform.

Deep reference on GitHub

Core repo README Providers repo README