// DEPLOYMENT GUIDE

How Deployment Works

Under the hood, ClawHost automates a multi-step process to deploy your bot in an isolated Docker container. Here's exactly what happens when you click "Deploy".

7-PHASE DEPLOYMENT

PHASE 1
Payment Processing

Stripe processes your 30€/month subscription. Once confirmed, deployment begins automatically.

PHASE 2
Bot Record Creation

We create a database record for your bot with a unique ID, generate a gateway token, and assign a port.

PHASE 3
Configuration Generation

Your bot's OpenClaw configuration is generated: AI provider settings, proxy endpoint, gateway token, and personality defaults.

PHASE 4
Docker Image Pull

The latest OpenClaw Docker image (alpine/openclaw:latest) is pulled from Docker Hub if not already cached.

PHASE 5
Container Creation

An isolated Docker container is created with your configuration, network isolation, and resource limits (1GB RAM, dedicated port).

PHASE 6
Health Checks

We monitor the container startup. The bot needs ~2 minutes to initialize, connect to Telegram, and become responsive.

PHASE 7
Credits Assigned

Once healthy, 10€ in AI credits are added to your account. Your bot is now live and ready to chat.

WHAT YOUR BOT GETS

// CONTAINER SPECS
MEMORY1 GB
CPUShared
NETWORKIsolated
STORAGEPersistent

STATUS REFERENCE

PENDING_PAYMENTWaiting for Stripe payment confirmation
DEPLOYINGContainer is being created and configured
RUNNINGBot is live and responding to messages
STOPPEDBot has been manually stopped by the user
ERRORDeployment failed — check logs for details
SUSPENDEDAccount suspended due to policy violation

COMMON ISSUES

Deployment takes longer than 5 minutes

Check your dashboard for status updates. If stuck, try stopping and restarting the bot.

Bot doesn't respond on Telegram

Verify your bot token is correct. Make sure you haven't revoked it in BotFather.

Health check fails

The bot needs ~2 minutes to start. Wait for the health check to complete before testing.

Container shows error status

Check the container logs in your dashboard. Common causes: invalid token, network issues.