Skip to main content
An instance is an isolated Azure Container App running OpenClaw. Each instance has its own container, filesystem, database records, and encryption keys. Instances are fully independent — one instance cannot access another’s data or configuration.

​
Instance limits by plan

PlanMax instances
Basic1
Pro5
Max20

​
Instance statuses

Instances move through the following statuses:
StatusDescription
provisioningContainer and storage are being set up. Takes about 30 seconds.
activeInstance is running and connected to channels.
suspendedInstance has been paused due to subscription cancellation or payment failure.
inactiveInstance has been manually stopped or is pending deletion.
The typical lifecycle is provisioning → active. Instances only move to suspended or inactive through billing events or manual action.

​
Creation flow

When you create an instance from the dashboard:
  1. Capacity check — Operator verifies your plan allows another instance.
  2. Database record — A record is created with status provisioning.
  3. Background provisioning — In parallel:
    • An API key is generated for the instance (used internally for Spider authentication).
    • A default openclaw.json configuration is created.
    • An Azure Container App is provisioned with the latest OpenClaw image.
    • An Azure Files volume is created at /{instanceId}/ and mounted into the container.
  4. Configuration sync — The generated config is written to the Azure Files volume.
  5. Active — The status moves to active and the OpenClaw process starts.
The entire process takes about 30 seconds. You can start configuring channels as soon as the instance is active.

​
Configuration

Instance configuration is managed through the Operator dashboard. When you make changes — adding a channel, enabling a skill, updating an agent persona — the following happens:
  1. The dashboard validates your changes.
  2. Updated configuration is encrypted and stored in Postgres.
  3. A new openclaw.json is generated and synced to the instance’s Azure Files volume.
  4. The container restarts to pick up the new configuration.
You never edit configuration files directly. All sensitive values (tokens, keys) are encrypted at rest and redacted in the dashboard UI.

​
Upgrading OpenClaw version

When a new version of OpenClaw is available, a notification appears in the dashboard on your instance page. To upgrade:
  1. Review the release notes linked in the notification.
  2. Click Upgrade to pull the new container image.
  3. The container restarts with the new version. Your configuration and data are preserved.
Upgrades are per-instance. You can upgrade instances independently if you want to test a new version before rolling it out everywhere.

​
Deleting an instance

Deleting an instance from the dashboard:
  1. Stops the OpenClaw process.
  2. Deprovisions the Azure Container App.
  3. Deletes the Azure Files volume and all stored data.
  4. Removes the database record and associated API keys.
This action is permanent. Channel connections are severed immediately and conversation history is deleted.

​
Suspension

Instances are suspended when your subscription is cancelled or a payment fails. The suspension process:
  1. Grace period — You have 14 days after the billing period ends or payment fails. Instances keep running normally during this time.
  2. Snapshot — After the grace period, Operator creates a snapshot of each instance’s configuration.
  3. Suspend — The container is paused. Channel connections are dropped. The instance status moves to suspended.
To restore suspended instances, reactivate your subscription or resolve the failed payment. Operator restores the snapshot and restarts the container.

​
Next steps

  • Channels — Connect messaging platforms to your instance.
  • Plans & Billing — Understand plan limits and subscription lifecycle.
  • Security — How instance data is encrypted and isolated.