Getting Started

Read this section first if you are evaluating Crawbl, reviewing the architecture, or exploring how the platform works before integrating it into your infrastructure.

What this section should answer

• what the control plane is responsible for
• where isolated runtime work happens
• how trust, secret handling, and approvals are enforced
• which technologies the platform depends on
• how the system can be deployed and owned

Read this section in order

1. Start with the 60-Second Platform Tour for the shortest useful mental model.
2. Continue to Technology Stack to see the major building blocks.
3. Read Architecture Overview for the three-layer system shape.
4. Read Security Model to understand trust boundaries and secret handling.
5. Use Integrations and Deployment Options when you need the external-system or packaging story.

Architecture at a Glance

Crawbl follows a three-layer architecture:

┌─────────────────────────────────────────────────────────┐
│                    Client Interface                      │
│           Mobile App | REST API | WebSocket             │
└─────────────────────────────────────────────────────────┘
                          │
                          ▼
┌─────────────────────────────────────────────────────────┐
│                  Orchestration Layer                     │
│    Auth | User Management | LLM Routing | Integrations  │
│              Audit & Compliance | GitOps                 │
└─────────────────────────────────────────────────────────┘
                          │
                          ▼
┌─────────────────────────────────────────────────────────┐
│                    Runtime Layer                         │
│   Isolated ZeroClaw Containers | Per-User Workspaces    │
│            Resource Isolation | Auto-Scaling             │
└─────────────────────────────────────────────────────────┘

Explore the Platform

Topic	Description
60-Second Platform Tour	The shortest path to the client → orchestrator → runtime mental model
Technology Stack	Core technologies: Go orchestrator, ZeroClaw runtime, Kubernetes
Architecture	Three-layer design: client, orchestration, runtime
Security Model	Zero-trust networking, secret management, compliance
Integrations	OAuth, external services, LLM providers
Deployment Shape	Self-hosted, cloud, and hybrid packaging options

What comes next

Once you have the platform shape, continue to Core Concepts for deeper architecture details or Deployment Shape to understand how Crawbl fits into your infrastructure.