OpenClaw Deployment
Create an independent OpenClaw container instance for each Application. By default, a base image with a fixed release version is used, preserving native functionality; the platform provides purchase, renewal, persistent storage, and deployment management.
¶ Creation and Purchase
- Open OpenClaw Deployment and create an Application.
- Select a duration plan on the purchase page and complete payment.
- Return to the configuration page, where you can select a platform chat model from the drop-down list and view the current model price. The platform will create independent API credentials for this instance; you can also disable platform access and configure it yourself in the native console.
- Choose to automatically generate access credentials, or set your own strong password/Token; select A2A and EnvarPay as needed, then confirm to begin deployment. Access credentials and model API credentials are independent of each other.
- After the instance is ready, obtain the access address and login credentials from the management page.
- Log in to the native console to configure channels. If platform model access was disabled during deployment, you must also configure the model provider and credentials yourself before chat can be used.
Deployment fees are charged according to the plan duration; specific USD prices and durations are subject to the purchase page. Model invocation fees are charged separately; purchasing deployment duration does not include model credits. When platform access is enabled, the dedicated API credentials only expose the chat interface corresponding to the selected model, and usage is billed separately from your platform balance. Each Application is purchased, renewed, and managed separately.
¶ Passwords, Credentials, and Subsequent Configuration
Access credentials are set before the first startup. The automatically generated option uses random credentials, custom passwords must be at least 16 characters, and OpenClaw Tokens must be at least 32 characters. Drafts do not save passwords; you may need to re-enter them after switching pages. After deployment, only the Application owner and administrators can view the access credentials.
The model API credentials of each instance are not reused, their validity is extended with deployment renewals, and they are revoked when the instance is deleted. If the platform model was not connected during the initial deployment, you can select a platform model on the configuration page of that Application and redeploy; the platform will update the default model while preserving conversations and other native settings. Afterwards, modify models and channels in the native console; if you select a model from another service, first adjust the authorization for the corresponding interface in platform credential management, or use the appropriate credentials. Normal redeployment does not overwrite native settings. Deployment environments that have not passed release verification will temporarily reject new deployments; please contact support.
¶ Optional Deployment Components
After selecting A2A, the deployment template will enable native OpenClaw A2A and provide an owner token on the management page. Selecting EnvarPay will additionally install an independent service container and persistent ledger, and requires A2A to be enabled first. EnvarPay initially has only owner access credentials, with no service or payee identity, and will not automatically charge fees or purchase on your behalf. Neither option automatically registers the instance with Envar; existing instances can enter configuration from the management page, enable them, and redeploy. Enabled components cannot currently be disabled in this wizard.
After A2A is enabled and the instance is ready, the access address card on the management page will display a copyable Agent Card address. The Agent Card for native OpenClaw A2A is on the same domain as the console, but its address includes /.well-known/agent-card.json; please copy the complete URL. If EnvarPay is also enabled, the management page will additionally display the corresponding “Envar Access Address”; when connecting to the Envar access service, copy this URL first.
¶ Versions and Data
The configuration page displays the currently released image version. New instances use the service's currently released version; existing instances will not be automatically replaced when the catalog is updated. Redeployment applies the current service version; please back up first and confirm the upgrade requirements of the version in use.
Each instance provides 1 CPU, a 2 GiB memory limit, and 10 GiB of persistent storage by default. Instance data is retained after restart. Actively deleting a deployment or reclamation after expiration will delete storage; please export any data that needs to be retained in advance.
¶ Renewal and Expiration
Renew on the purchase page of the current Application, and the validity period will be extended according to the platform's existing duration rules. After expiration, access entry is suspended, and renewing during the grace period restores access; after the grace period, the instance and data will be reclaimed. Refer to the expiration time, billing status, and deletion notices on the management page.
¶ Initial Browser Pairing
OpenClaw retains native device pairing. Enter the instance Token displayed on the management page into the OpenClaw console; if prompted for pairing, execute the following in the instance terminal on the platform deployment management page:
node /app/openclaw.mjs devices list
node /app/openclaw.mjs devices approve <requestId>
Replace <requestId> with the ID corresponding to the browser request just made, approve only your own device, and then refresh the console. There is no need to disable device authentication.
¶ Frequently Asked Questions
- Why can't a new instance respond yet? Deployment completion only means the container is ready. If platform model access was disabled during deployment, select a platform model on the configuration page and redeploy, or configure the model and credentials yourself in the native interface.
- Are additional plugins preinstalled? None are added by default. You can configure them as needed in the management interface.
- How do I update an existing instance? The existing Application and order are retained. The current service version is used when redeploying; back up your data and check version compatibility before upgrading.
- What should I do if startup fails? First, review the deployment logs and events, and configure the model only after confirming that the instance is ready. Do not expose instance passwords or keys in public comments or screenshots.
