The Short Answer
If you're technical and only need basic OpenClaw with 1-2 integrations, DIY is fine. Use our free tools and you'll be running in an hour.
If you want 3+ integrations, security hardening, custom skills, or you just don't want to spend a Saturday debugging OAuth tokens — the $100 done-for-you setup saves you 4-8 hours and gets you a production-grade instance in 24 hours.
What DIY Setup Actually Looks Like
Here are the actual steps involved in a full OpenClaw setup with integrations. This is what we do for every client:
- 1.Install Node.js 22+ and verify version
- 2.Install OpenClaw globally (npm install -g openclaw@latest)
- 3.Run openclaw onboard — configure API key or OAuth subscription
- 4.Install Gateway daemon (launchd/systemd service)
- 5.Pair WhatsApp via QR code (openclaw channels login)
- 6.Set up Gmail OAuth credentials in Google Cloud Console
- 7.Configure Gmail/Calendar integration with correct OAuth scopes
- 8.Create a Telegram bot via BotFather and set token
- 9.Configure Telegram webhook URL (public endpoint needed)
- 10.Set up Slack app with bot token and app token
- 11.Configure Discord bot and set DM policies
- 12.Set up GitHub personal access token with correct scopes
- 13.Configure DM security policies (pairing vs open)
- 14.Set up Tailscale Serve/Funnel or reverse proxy for remote access
- 15.Add authentication (password or Tailscale identity)
- 16.Configure TLS for any exposed webhook endpoints
- 17.Test each channel end-to-end (send/receive round trip)
- 18.Run openclaw doctor to verify configuration
Steps 1-4 take about 15 minutes. Steps 5-18 take 4-8 hours depending on how many integrations you want and how comfortable you are with OAuth flows, webhooks, and security configuration.
Where DIY Gets Hard
OAuth Configuration
Gmail, Google Calendar, and Slack all require OAuth2 setup in their respective developer consoles. Scopes, redirect URIs, and consent screens are fiddly and poorly documented.
Webhook Configuration
WhatsApp and Telegram require publicly accessible webhook endpoints. If you're running locally, you need tunneling (ngrok) or a reverse proxy. Getting this wrong means messages silently fail.
Security Hardening
An AI agent with access to your email, calendar, and chat apps is a high-value target. Exposed ports, missing auth, and default credentials are common mistakes that leave your data vulnerable.
Integration Testing
Each integration works differently. Tokens expire, rate limits kick in, webhooks timeout. Testing all permutations takes time and patience.
Side-by-Side Comparison
DIY Setup
- ✓ Free
- ✓ Full control over every setting
- ✓ Learn how it works under the hood
- ~ 4-8 hours for full setup
- ✗ No security review
- ✗ No support if things break
Done-For-You ($100)
- ✓ Live in 24 hours
- ✓ Up to 5 integrations configured
- ✓ Security hardening included
- ✓ 30-minute walkthrough
- ✓ 7 days of follow-up support
- ✓ Production-grade from day one
When to DIY
- →You're a developer comfortable with Node.js, Docker, and OAuth
- →You only need basic OpenClaw with 1-2 simple integrations (Telegram, Notion)
- →You want to learn how OpenClaw works internally
- →Budget is the primary constraint
Start with our free Docker templates and setup script. They handle 60-70% of the work.
When to Go Done-For-You
- →You want 3+ integrations (WhatsApp, Gmail, Calendar, Slack, etc.)
- →You're a founder and your time is worth more than $100 for 4-8 hours
- →You need security hardening for an agent that touches sensitive data
- →You want custom skills built for your specific workflow
- →You tried DIY and hit issues with OAuth, webhooks, or configuration