Self-host

Operate Bitcoin Bastion on infrastructure you control

Self-hosting is a sovereignty decision: no custody, no key management by Bastion, and visible degraded states when dependencies fail.

No-custody warning: never store seed phrases, private keys, or signing authority in Bitcoin Bastion.

Starter

Single host baseline for evaluation and non-critical operations.

Operator

Multi-service VPS with explicit monitoring, backup, and incident procedures.

Production

Hardened deployment posture with verified readiness gates and recovery drills.

Sovereign

Operator-owned stack with Bitcoin-node-aligned controls and minimized external trust.

Self-Hosted Readiness Wizard

No secrets are requested. This wizard is client-side only and stores nothing sensitive.

Do you have a VPS?Do you have a domain?Do you have PostgreSQL?Do you have Redis?Do you need Telegram integration?Do you plan Bitcoin node integration?Do you need Kubernetes?

Recommended profile

Starter

Required services

Local dev environment
Container runtime
Non-production test data

Security checklist focus

Never place private keys or seed phrases in Bastion.
Enable TLS, backups, and restore drills before production cutover.
Keep degraded mode indicators visible to operators.

Next docs

/self-host/quickstart /self-host/security-checklist

Self-host docs

Quickstart Docker Kubernetes VPS Security checklist Production readiness