How to Set Up OpenClaw (Even If You Have Never Opened a Terminal)

Most OpenClaw setup guides assume you know Linux, Docker, and API configuration. This one does not. This guide walks through every step in plain English, with time estimates so you can decide at each stage whether to continue DIY or hand it off to a professional.

Before You Start: What You Need and What It Costs

OpenClaw needs 4 things to run. None of them are complicated on their own. The complexity comes from connecting them together and making sure nothing is exposed to the internet without proper security.

1. A server to run on (a VPS you rent for $5 to $13 per month)
2. An AI model to think with (Claude, GPT-4, or DeepSeek, paid per usage at $15 to $30 per month)
3. A messaging channel to talk through (WhatsApp, Telegram, Slack, or email)
4. Skills that tell OpenClaw what to do (free from ClawHub, or custom-built)

Total ongoing cost after setup: $20 to $43 per month. Full cost breakdown in the OpenClaw setup cost guide.

Total DIY setup time: 20 to 40 hours depending on your technical comfort level. Here is roughly how that time breaks down:

Tip: Read through the entire guide first before starting. If steps 5, 6, and 7 feel over your head, that is the decision point where hiring professional help makes financial sense. Your time at $100/hour means DIY "free" setup costs $2,000 to $4,000 in labor.

Step 1: Get a Server (30 Minutes)

OpenClaw needs a computer that stays on 24/7. Your laptop will not work for this because it sleeps, restarts, and moves between networks. You need a VPS (Virtual Private Server), which is a small computer in a data center that runs around the clock.

For business OpenClaw workflows, you need at least:

• 2 vCPUs (processing power)
• 8 GB RAM (memory for the Gateway and AI context)
• 100 GB storage (for skills, memory files, and logs)

Three providers that work well for OpenClaw:

• Hostinger KVM 2: ~$6/month. Best value. They also offer a one-click OpenClaw installer.
• Contabo Cloud VPS S: ~$7/month. More storage and CPU for slightly more money.
• Hetzner CX22: ~$5/month. Cheapest option but only 4 GB RAM (tight for 3+ workflows).

Sign up, pick a plan with Ubuntu as the operating system, and create your server. The provider gives you an IP address and a password. Write both down.

Tip: Pick Ubuntu 22.04 LTS as your operating system. Almost every OpenClaw guide and troubleshooting resource assumes Ubuntu. Picking a different OS means every command in every tutorial needs to be translated. Save yourself the headache.

Step 2: Access Your Server (30 to 60 Minutes)

This is where most non-technical users hit their first wall. You need to connect to your server using SSH (Secure Shell), which is a way to type commands on a remote computer.

On Mac or Linux, open Terminal and type:

ssh root@your-ip-address

On Windows, download a free tool called PuTTY, enter your IP address, and click Connect.

Either way, you will see a blinking cursor on a black screen. That is your server. Everything from here happens by typing commands.

Tip: If you have never used a terminal before, spend 15 minutes reading a "Linux terminal basics" tutorial first. You only need 5 commands for the entire OpenClaw setup: cd (change directory), ls (list files), nano (edit text files), sudo (run as admin), and cp (copy files). That is it.

Step 3: Install OpenClaw (1 to 2 Hours)

OpenClaw runs on Node.js, so you need to install that first, then install OpenClaw itself. Here is the sequence:

1. Update your server's software packages (1 command, takes 2 minutes)
2. Install Node.js version 20 or higher (2 commands, takes 5 minutes)
3. Clone the OpenClaw repository from GitHub (1 command, takes 1 minute)
4. Run the OpenClaw installer (1 command, takes 5 to 10 minutes)
5. Walk through the onboarding wizard (interactive, takes 10 to 15 minutes)

The onboarding wizard asks you a series of questions: which AI model to use, what name to give your agent, which messaging platform to connect. Answer each one and OpenClaw generates the configuration files for you.

At this point, OpenClaw is installed but not connected to anything useful yet. Think of it as a car with an engine but no wheels.

Step 4: Connect an AI Model (30 to 60 Minutes)

OpenClaw does not include its own AI. You connect it to an external model through an API key. The 3 most common choices:

After signing up, you get an API key (a long string of characters). Paste that key into OpenClaw's configuration file. The onboarding wizard usually handles this step, but if you need to change models later, you edit the config file directly.

Tip: Start with Claude Haiku ($1/$5 per million tokens). It handles email triage, document routing, and daily briefings well and costs 3 to 5x less than Claude Sonnet. You can always upgrade to a more expensive model later for specific workflows that need deeper reasoning.

Step 5: Connect a Messaging Platform (2 to 4 Hours)

This step tells OpenClaw how to receive messages from you and send messages back. The 3 most common options, ranked by setup difficulty:

Telegram (Easiest, 30 to 60 Minutes)

Open Telegram, search for @BotFather, send /newbot, give your bot a name. BotFather gives you a token. Paste it into OpenClaw's Telegram configuration. Done. Telegram is free, has no message limits, and the bot API is straightforward. This is the best option for your first setup.

Slack (Medium, 1 to 2 Hours)

Create a Slack app at api.slack.com, configure OAuth permissions (chat:write, channels:read, channels:history), install the app to your workspace, and paste the bot token into OpenClaw. Slack works well for teams that already live in Slack because OpenClaw can send briefings, alerts, and summaries directly into channels your team already watches.

WhatsApp (Hardest, 2 to 4 Hours)

WhatsApp requires a Business API account through a provider like Twilio, 360dialog, or the official WhatsApp Cloud API. You need a phone number, business verification, and webhook configuration. It is the most natural interface (feels like texting your assistant) but the setup takes the longest and WhatsApp charges per conversation.

Tip: Start with Telegram even if you plan to use WhatsApp or Slack long-term. Get OpenClaw working on Telegram first, confirm your workflows run correctly, then add WhatsApp or Slack as a second channel. Debugging workflow issues and messaging issues at the same time is twice as frustrating as doing them separately.

Step 6: Harden Security (3 to 5 Hours)

This is the step most DIY guides gloss over and the one that matters most for business use. Running OpenClaw without security hardening means your API keys, business emails, and CRM credentials are accessible to anyone who scans your server's open ports.

Here is what needs to happen, in plain English:

Run OpenClaw Inside Docker

Docker is a container that isolates OpenClaw from the rest of your server. If OpenClaw gets compromised, the attacker cannot access your full server. Without Docker, OpenClaw has access to every file on your machine.

Store API Keys in Environment Variables

Never paste API keys directly into config files. Config files can get accidentally shared, committed to Git, or read by other processes. Environment variables store keys in memory where only OpenClaw can access them.

Configure a Firewall

Your server has dozens of ports open by default. OpenClaw only needs 2 or 3. A firewall blocks everything else. The most common setup: allow SSH (port 22), allow your messaging platform's webhook port, block everything else inbound.

Restrict Outbound Network Access

OpenClaw should only be able to reach the domains it actually needs: your LLM API provider, your messaging platform, and your business tools. Block everything else outbound. This prevents a compromised skill from sending your data somewhere unexpected.

Audit ClawHub Skills Before Installing

36% of community-built skills on ClawHub have known vulnerabilities, based on independent security analysis. Do not install random skills. Read the SKILL.md file. Check what commands it runs. Stick to the verified registry or build custom skills.

Tip: Run openclaw security audit after completing your setup. OpenClaw includes a built-in security checker that flags common misconfigurations. For a deeper scan, run openclaw security audit --deep. Fix every issue it finds before connecting business tools.

Step 7: Configure Your First Workflow (5 to 15 Hours)

This is where OpenClaw goes from "installed software" to "working AI agent." A workflow tells OpenClaw what to do, when to do it, and what tools to use.

For your first workflow, start with email triage. It is the simplest to set up and gives the most immediate value. Here is what you configure:

1. Connect OpenClaw to your email (Gmail or Outlook) through the email skill
2. Set up the heartbeat scheduler to run the triage every 30 minutes
3. Define your categories: "client urgent," "internal FYI," "vendor action needed," "billing," "spam"
4. Configure where the prioritized summary gets delivered (Telegram, Slack, or email digest)
5. Test with a few hours of real email and adjust the category rules

The time range here (5 to 15 hours) depends on how many workflows you configure. Email triage alone takes 3 to 5 hours. Adding a daily briefing takes another 2 to 3 hours. Each additional workflow (CRM updates, document routing, vendor coordination) adds 2 to 5 hours of configuration and testing.

Tip: Write your workflow rules as simple "if/then" statements before touching any config file. "If an email contains the word 'invoice' and is from a new sender, flag it to the CFO." "If a client email has not been responded to in 4 hours, send me a Slack alert." Having these written in plain English first makes the technical configuration much faster because you are translating logic, not inventing it on the fly.

Step 8: Test Everything (3 to 8 Hours)

Before trusting OpenClaw with real business communications, test every workflow end to end:

• Send test emails to yourself and check if OpenClaw categorizes them correctly
• Verify that urgent alerts arrive on the right messaging channel within 5 minutes
• Check that the daily briefing actually delivers at the scheduled time
• Confirm that draft responses look reasonable (you will review them before sending)
• Try to break it: send a very long email, a blank email, an email with attachments, an email in another language
• Run openclaw security audit one more time after all integrations are connected

Testing takes longer than you expect. Budget a full day. Most issues surface in the connection between tools (the email skill works, but the Slack notification does not arrive because a permission is missing). These are fixable, just time-consuming.

The Honest Assessment: Should You DIY or Hire Help?

Here is a simple way to think about it:

There is no shame in starting DIY and switching to professional help at step 6. Many Mixbit clients start that way. They get OpenClaw installed, realize the security and workflow configuration is a bigger project than expected, and bring in Mixbit to finish the deployment properly.

What to Do After Setup

Once OpenClaw is running and your first workflow is tested:

1. Run it for one full week without making changes. Watch how it handles real email, real documents, real scheduling. Note where it gets things right and where it misses.
2. Adjust category rules and routing logic based on what you observed. This is normal. No workflow is perfect on day one.
3. Add a second workflow (daily briefing is the natural next step). Read the 10 OpenClaw use cases guide for ideas on what to automate next.
4. Check your API costs after the first month. If they are higher than expected, review the cost optimization tips in the OpenClaw setup cost guide.
5. Run openclaw security audit monthly. Security is not a one-time thing.

Common Mistakes That Waste Time

From Mixbit's experience deploying OpenClaw for dozens of businesses, here are the 5 mistakes that cause the most wasted hours during DIY setup:

1. Skipping the heartbeat scheduler and then wondering why OpenClaw does not do anything autonomously. The heartbeat is what makes OpenClaw proactive. Without it, OpenClaw just sits there waiting for you to type something.
2. Installing random skills from ClawHub without reading the SKILL.md file first. Some skills run shell commands that modify system files. Read before you install.
3. Using the expensive AI model for everything. Claude Haiku handles 80% of business workflows at 5x lower cost than Sonnet. Switch models per workflow, not globally.
4. Not setting a daily token budget. One runaway workflow can cost $50 in a single day. Set a cap.
5. Testing on fake data instead of real email. OpenClaw needs real patterns to calibrate. Use a secondary email address if you are nervous, but send real types of messages to it.

Where to Go from Here

OpenClaw is installed and running. Now the question is what to do with it.

• If you want to understand what OpenClaw is at a deeper level, start there.
• If you want workflow inspiration, read the 10 OpenClaw use cases for business.
• If you want to understand costs in detail, check the full cost breakdown.
• If you tried DIY and decided professional help is the better path, Mixbit deploys OpenClaw with security hardening, custom workflows, team training, and hypercare. Live in 3 days.