A cloud you can leave
OpenStack resources are declared in Heat, configured by Ansible and operated through a TypeScript CLI. There is no proprietary control plane to keep alive.
- Heat
- Ansible
- TypeScript
Open infrastructure, end to end
TOAD turns an OpenStack project into a secure Docker Swarm platform—from one useful node to a resilient production cloud—without Terraform or a proprietary control plane.
$ pnpm run apply -- my-cloud
✓ Heat resources reconciled
✓ Swarm managers healthy 3 / 3
✓ Traefik HTTPS ready
✓ Monitoring targets up 18 / 18
✓ Acceptance checks passed
What it gives you
TOAD keeps the infrastructure understandable while adding the contracts a maintained service needs.
OpenStack resources are declared in Heat, configured by Ansible and operated through a TypeScript CLI. There is no proprietary control plane to keep alive.
Traefik discovers Swarm services from labels, obtains HTTPS certificates and sends traffic through a shared overlay—without publishing application ports.
Machine-readable diagnosis, external probes, metrics, logs, alerts and declared acceptance checks make failures explainable to people and agents.
Immutable images, resource limits, rollback policy, encrypted backups and mTLS-protected administration are enforced before a service is deployed.
One contract, two scales
A profile changes the topology, not the operating model. The manifests, security policy and application workflow stay familiar as the cloud grows.
Small but complete
The same routing, certificates, monitoring and application contract on the smallest practical footprint.
A closed operational loop
Every normal change returns to declared state and ends with evidence. Agents can follow the same narrow runbooks as a human operator.
doctorCheck tools, credentials and safe local state without exposing secret contents.
applyCreate or update cloud resources, hosts, Swarm, ingress, DNS and monitoring.
app deployValidate policy, deploy with rollback and run the application’s HTTPS checks.
verifyMeasure quorum, replicas, DNS, TLS, routes and monitoring in one JSON report.
Before an application reaches the cluster
Choose deliberately
TOAD is not trying to imitate every platform. It chooses a compact operating surface and excellent Traefik integration for teams that want to own the result.
| Consideration | TOAD / Swarm | Kubernetes | Managed PaaS |
|---|---|---|---|
| Starting footprint | 1 manager | Control plane + workers | Provider-defined |
| Operational surface | Small | Large | Small |
| Infrastructure ownership | Your OpenStack project | Your cluster | Provider account |
| Application routing | Traefik labels | Ingress resources | Platform-specific |
| Exit path | Heat + Compose + backups | Cluster manifests + backups | Varies by provider |
Kubernetes remains a possible separate provider—not a hidden mode that makes Swarm harder to understand.
GNU AGPL-3.0-or-later
Use it, study it, adapt it for clients, and keep the complete system reproducible.