# self-hosting

Claude tag only officially supports Slack. Want an AI assistant that comes when you call on LINE? Build it yourself. Use OpenClaw to spin up a LINE bot on a VPS — messages come in from LINE's official cloud, the gateway catches them, and the agent replies. This post covers the replicable skeleton, three security must-haves, and why freedom always comes with responsibility.

A team wants OpenClaw on their intranet, coworkers tagging it in Teams. Outbound is sorted via a forward proxy. But inbound? Teams messages come from Microsoft's cloud — pure intranet is physically impossible. The post office problem: what moves inside the building (GitLab issues), what needs a door (DMZ + Teams), and why the extra architecture hassle is the right answer.

In early 2026, OpenClaw got hit three times: 20,000+ gateways exposed to the internet, 20% of marketplace skills were trojans, and link previews became exfiltration vectors. Attackers had a smooth ride until they hit a closed door — and 'proper configuration' suddenly mattered. Self-hosting freedom comes with self-hosting responsibility.

Everyone's installing OpenClaw raw and wondering why it burned $200 organizing Downloads. This guide adds guardrails: Raspberry Pi isolation, Tailscale VPN, Matrix E2E encryption, prompt injection hardening. The goal isn't perfect security—it's knowing where the bullets can get in.