OpenClaw VPS Hosting. A home for your AI assistant.
OpenClaw comes preinstalled on Ubuntu 24.04. Connect your model account, configure your channels, and give your assistant a private server for ongoing tasks.
OPENCLAW PREINSTALLEDConnect your model and channels after deployment.First steps ↗
YOUR SERVER CONNECTIONVPS network speeds up to 1 Gbps, depending on the location and plan.
PREINSTALLED / READY TO CONFIGURE
From first login to your first task.
The application is installed for you. You connect your own model account and decide which channels and tools your assistant can use.
Open your application. Use the HTTPS URL and application login supplied with your AwakeHost service. These credentials are separate from your Client Area and SSH login. Initial setup can take a few minutes; retry once it finishes.
Configure a model connection. In OpenClaw's configuration, select a supported model provider and model, then add your own API key or the provider's supported authentication. Check your account's billing and usage limits.
Test a simple conversation. Open Chat and send a short message. If it fails, check the connection status and logs for authentication or model errors before adding more integrations.
Connect one channel. Follow the chosen channel's setup guide for its bot token, account pairing, and any required plugin. Restrict access to intended users and send a test message through that channel.
Add tools gradually. Review each skill's permissions, test one small task, and inspect the result. Keep recoverable backups of configuration and workspace data before making changes.
The gateway, browser processes, and local files use VPS resources. External model usage has its own service limits and charges.
Starting points for an external-model setup; measure your own workload before scaling.
Your workload
Plan to evaluate
What to check
Light trials
2 GB / 1 shared vCPU
Try simple tasks with a small workspace. Check memory pressure and response time before relying on ongoing automation.
Personal assistant
4 GB / 2 shared vCPU
Our recommended starting point for a personal setup. Leave headroom for the Gateway, integrations, and operating system.
Multiple channels
8 GB / 4 shared vCPU
Evaluate with your actual channels and browser tools. Watch peak memory and CPU when tasks overlap.
More concurrent work
16–32 GB
Choose from measured demand for jobs, supporting processes, and larger workspaces. A memory tier does not guarantee an agent count.
Large retained workspaces
64–96 GB
Review working memory, retained files, and backup size. Set retention rules so logs and artifacts do not fill the disk.
Model inference runs at your chosen external service. These plans list no GPU allocation; local-model inference needs a separate capacity review. Compare all plan resources ↗
PRIVATE GATEWAY / INTENDED CONNECTIONS
Plan access before connecting channels.
The Gateway holds workspace state and integration credentials. Choose how you will reach it and which services it can contact.
Use the supplied HTTPS application address. Keep its login protected. Preserve authentication and firewall protection around the underlying Gateway and administrative services when changing network settings.
Allow the integration connections you need. Model APIs and channel services need the outbound access described in their setup guides. Check DNS and connection requirements for the selected integrations.
Configure inbound callbacks deliberately. If a channel requires a public webhook, follow its authenticated HTTPS setup. That callback requirement does not require exposing the Gateway's whole control interface.
Administrator access gives you control of the server. You configure the assistant's accounts, integrations, and permissions.
Scope credentials and tools.
Limit integration credentials to the required work, and review skills and plugins before enabling their tools. File and command tools can affect the environment they run in. Keep application and editor credentials private.
Verify sandboxing.
OpenClaw documents sandboxing as off by default. Check the installed policy and verify isolation for enabled tools, including reachable files and credentials.
Keep the OS and OpenClaw updated, retain protected backups of state and workspace data, and test recovery. External model APIs, subscriptions, software licences, and other third-party services are separate from the VPS.
A private VPS can run your OpenClaw assistant, scheduled tasks, and connected tools without keeping your own computer running.
Is OpenClaw preinstalled?
OpenClaw is preinstalled on Ubuntu 24.04. You configure your model account, channel connections, and tool permissions after deployment; external accounts and usage are separate.
What should I do after deployment?
Open the application URL supplied with your service and sign in with its application credentials. Allow the initial setup to finish if the page is not yet available. Configure a model connection, send a test message, then connect one channel and restrict access to intended users. The setup guide on this page explains the sequence.
Are AI model subscriptions included?
The listed plans cover the VPS resources. External model APIs, subscriptions, software licences, and other third-party services are separate.
Who manages the assistant and its data?
You have administrator access to configure your software, integrations, and permissions. Keep backups and protect the credentials used by connected tools.
How should I size the gateway and its tools?
Start with 4 GB RAM and 2 shared vCPU for a personal assistant using an external model service; evaluate 8 GB RAM and 4 shared vCPU for multiple channels. The 2 GB plan has 1 shared vCPU and suits light trials. Browser processes, concurrent jobs, and retained files can require more capacity. Monitor representative workloads before choosing a larger tier. No GPU allocation is listed; local-model inference needs a separate capacity review.
How do I access the Gateway securely?
Use the supplied HTTPS application URL and application credentials for browser access. Keep the underlying Gateway and administrative services protected by authentication and firewall rules. Allow the connections required by your chosen model and channels; follow each channel guide for any webhook or pairing requirements.
Does preinstallation also configure tool permissions?
Preinstallation provides the application. You still choose which accounts, skills, and tools it may use. Review the installed execution policy and verify sandbox settings before enabling file or command tools. OpenClaw documents sandboxing as off by default; check the actual deployment rather than assuming isolation is enabled.
How much bandwidth is included?
Each plan includes the monthly bandwidth allowance shown in its pricing card and the resource comparison. The allowance measures data transferred per month. Monitor outbound data for your workload, and confirm any additional-usage charges with AwakeHost before ordering.