Clawdie AI

Everything we use to run Clawdie — documented openly. FreeBSD, nginx, Tailscale, Stripe — if it runs on our server, it can run on yours.

Architecture

Clawdie runs on a two-server split architecture connected via Tailscale VPN.

domedog — Brain

Agent runtime, Telegram integration, Supabase memory, Playwright browser orchestration, tmux glass-pane console.

Control plane · FreeBSD 15

clawd — Eyes

Real Chrome browser on Xfce4 desktop, Chrome DevTools Protocol at port 9223, VNC monitoring at port 5901.

Browser server · CDP
Memory split

Clawdie is moving toward a split-brain model: Brain A is prebuilt local knowledge imported into the database jail during bootstrap. Brain B is dynamic user and agent memory that evolves later.

Why separate?

Headless environments fail against Cloudflare Turnstile challenges. Running Chrome on a dedicated desktop server maintains human-like browser behavior while the operator monitors via VNC.

Quick reference

Component Technology Purpose
OSFreeBSD 15Server platform
RuntimeNode.js 24+Agent orchestration
LanguageTypeScriptType-safe codebase
IsolationFreeBSD JailsAgent sandboxing
Web servernginxReverse proxy, static sites
SSLLet's EncryptHTTPS certificates
VPNTailscaleEncrypted mesh network
FirewallPFPacket filtering
ChatTelegramOperator interface
MemoryPostgres / pgvectorPersistent storage
BrowserPlaywright + CDPWeb automation
PaymentsStripeBilling integration
EmailProtonMail SMTPOutbound email from custom domain
LicenseBSD-3-ClauseSame license as FreeBSD

Setup guides

Step-by-step guides for deploying and operating a self-hosted AI assistant on FreeBSD.

Project

Release history, license reasoning, and project meta.