What are system containers?
EasyClaw uses Incus system containers — lightweight Linux environments that run a full operating system, not just a single process. Each container has its own filesystem, networking, and process tree. This lets EasyClaw run a complete AI assistant environment (agent, messaging bridges, browser, tools) inside each one.Incus is a modern, open-source container manager built on Linux container technology. It’s maintained by Linux Containers and used in production for lightweight, secure virtualization.
Why system containers?
EasyClaw containers aren’t stateless services. Each one is a persistent, stateful environment with:- A full filesystem where your AI stores files, memory, and credentials
- Multiple long-running processes (ZeroClaw, messaging bridges, browser)
- Persistent network connections (WebSocket bridges to WhatsApp, Signal, etc.)
- The ability to freeze and resume state instantly
Template images
Every container is cloned from a template image — a pre-built environment (~135MB) that contains everything an AI assistant needs:- ZeroClaw agent framework and default configuration
- Messaging bridges for all supported channels
- Headless browser for web browsing and automation
- System tools — shell, text editors, common utilities
- Networking — Pre-configured DNS, certificates, proxy settings
Container lifecycle
Spawn
When you start a session, the fleet clones the template and starts your container. ZeroClaw boots, bridges connect, and your AI is ready.
Active
While you’re using EasyClaw, your container is running. Messages flow in real-time, your AI processes requests, and state is saved to disk.
Freeze
When you’re inactive, EasyClaw freezes your container. All processes are suspended in place — like closing a laptop lid. Zero CPU usage, state preserved.
Restore
When you send a new message, the fleet restores your container. All processes resume exactly where they left off — bridges reconnect, ZeroClaw picks up your conversation.
Persistent storage
Each container has persistent storage:Networking
Each container gets:- A private IP on an internal network
- A reverse proxy route for HTTPS access
- A DNS record for WebSocket connections from the browser
- Outbound internet access for AI API calls and web browsing
Resource limits
Each container has resource limits based on your plan:| Resource | Free | Pro | Ultra |
|---|---|---|---|
| CPU | 1 core | 2 cores | 4 cores |
| RAM | 512MB | 1GB | 2GB |
| Storage | 1GB | 5GB | 10GB |
Security isolation
Containers provide strong isolation through multiple layers:- Process isolation — your container can’t see other containers
- Network isolation — each container gets a private IP, no cross-container access
- Access control — mandatory profiles restrict what containers can do
- Unprivileged mode — container root maps to a non-root user on the host
Read more about security
Encryption, authentication, and infrastructure security.

