Home / Home / Guides / Guide to Self-Hosting sipi.bot

Guide to Self-Hosting sipi.bot

The core is MIT-licensed and self-hosts anywhere. Here's what self-hosting actually includes — and the honest trade-offs.

What you get

The complete deterministic decision engine — all six rule types, HTTP API, MCP tool, CLI.

Your rules, your infrastructure, no vendor in the loop.

What you don't

The hosted dashboard, managed approval queue, and stored audit log are hosted-only.

You own uptime, storage, and your approval UI.

The checklist

Persist the store on a volume. Wire /health to your orchestrator. Create the first rule with the admin token. Set per-agent keys.

Minimum viable deploy

docker build -t sipi-bot .
docker run -d -p 8080:8080 -v sipi-data:/data \
  -e SPENDFIREWALL_DB=/data/spendfirewall.db sipi-bot
curl localhost:8080/health   # 200

See /tutorials/self-host-in-docker for the full walkthrough.

FAQ

Is self-hosting really free?

Yes — MIT license, no gating.

Should I self-host or go hosted?

Self-host for control and cost; hosted for the dashboard, approval queue, and zero ops.

Related

Stop the next $12,400 night.

One API call (or MCP tool) in front of every agent transaction — APPROVED, BLOCKED, or FLAGGED, deterministic, ~5 ms, fully logged.

See plans — from $99/mo Try a live check