Skip to content
← All work

P-003 · 2025

OpenClaw — 15-agent autonomous system

A self-hosted AI agency on a $10/month VPS — 15 sub-agents across three agencies (Dev/Shuri, Creative/Maya, LinkedIn/Natasha) reporting to Jarvis the COO. One Telegram message kicks off a full product cycle: build → QA → deploy → post.

Role
Founder · solo engineer
Year
2025
Outcome
15 agents · 3 agencies · 0 headcount
Hostinger KVM2 VPSDockerGLM-5GroqGemini 2.5 FlashClaude CodeTelegram BotFirebaseVercel

The problem

Building AI-powered products solo means orchestrating dozens of moving parts across research, design, code, deploy, QA, content, and marketing — every day. The existing SaaS multi-agent platforms lock you in, leak your data, or stack subscriptions. I wanted a self-hosted agency I owned end-to-end: cheap to run, fork-able, fully customisable. One Telegram message in, a shipped product out.

Architecture

Interactive system view

See the product from purpose to implementation.

Follow the work, then switch views when you want the practical answer: who it is for and what it is built with.

Flow pausedStep 01 / 08

Step 01 of 08

Three-layer hierarchy on a $10/month…

Three-layer hierarchy on a $10/month Hostinger KVM2 VPS (Docker). Layer 1: Jarvis the COO. Layer 2: agency CEOs — Shuri (Dev), Maya (Creative), Natasha (LinkedIn). Layer 3: 15 specialised sub-agents.

Full system map

The grouped dependency view stays visible so the infrastructure is readable at a glance.

System map

How the pieces connect

Three-layer agency hierarchy on a $10/month Hostinger VPS. A single Telegram message reaches Jarvis (Layer 1 COO running a ReAct loop with persistent context in SOUL.md / USER.md / MEMORY.md). Jarvis routes through Groq's free tier to one of three agency CEOs — Shuri (Dev), Maya (Creative), Natasha (LinkedIn) — each owning a narrow pipeline of specialists. Heavy models (GLM-5, Gemini 2.5 Flash) are invoked only when needed; image and video agents always confirm with the user before firing. Shared Firebase state, not prompt-passing, is what keeps the whole agency coherent — and what makes a $10/month VPS replace a 5–7 person team.

Outcome

  • 15 agents across 3 agencies — fully autonomous after task input.
  • Running 24/7 on a $10/month Hostinger KVM2 VPS, zero downtime since launch.
  • Replaces what would otherwise be a 5–7 person team for a side project.
  • No SaaS subscriptions stacking up, no vendor lock-in, no data leaving the box. Fully customisable agency structure — fork it, rewire it, add your own CEOs.

Lessons learned

  • Specialisation beats generalisation. Narrow-scope agents with clear boundaries fail less than one big "do everything" model.
  • Shared state > prompt-passing. The moment agents share a store, hallucinations drop sharply.
  • One COO > round-robin routing. A single agent deciding who-does-what prevents infinite loops between peer agents.
  • Brand-check is mandatory — Maya (Creative) has a brand-checker built in so every output passes a visual style filter before shipping.
  • Persistent context files (SOUL / USER / MEMORY) beat re-prompting every turn. The agent stays itself across days, not just turns.

On LinkedIn

Launch post· 856 launch-day impressionsWorkflow demo· 841 launch-day impressions