Documentation
in real steps.
Short guides, real commands, manifests that run. From the first install to the fifth incident — in the order you'll need them.
Install, bring up the cluster, day-to-day commands.
Installation
Install HeroCtl on any Linux server with Docker in a single command. Covers prerequisites, bootstrap, and verification.
Bring up a 3-node cluster
Form a cluster with 3 servers in under 10 minutes. Tolerates 1-node failure with no downtime.
Complete CLI reference
All heroctl commands with synopsis, flags, and example. Use as a desk reference.
Multi-region (planned for Q4 2026)
What to expect from multi-region in HeroCtl, how to run across regions today, and the roadmap through 2027.
Ship code to production without giving up downtime.
Deploy your first app
Bring up a Node.js application with a Postgres database in 50 lines of YAML. Includes health check, rolling deploy, and rollback.
Rolling, canary, blue-green, and rainbow
Four deploy strategies. When to use each, with complete examples and honest trade-offs.
Domain, certificates, and firewall without external tooling.
Ingress and automatic TLS
How to expose applications on port 443 with certificates issued and renewed automatically, without operating an external router.
Firewall configuration
Which ports HeroCtl uses, which need to stay open, and which should never be exposed to the internet.
Secrets, RBAC, and who gets to touch what.
Metrics, logs, and cluster state backups.
Metrics and logs
Collect metrics, logs, and traces without standing up an external observability stack. When it's worth it, and when to integrate with an outside tool.
Backup and restore of cluster state
How to save, schedule, and restore HeroCtl control plane snapshots. Disaster recovery strategy.
HTTP endpoints for automation and integration.
When things go wrong: from alert to diagnosis.
Start at the start.
If this is your first contact, follow the order above. In half an hour you have a 3-node cluster with an app behind HTTPS.