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 source infrastructure for people and agents
Put your first website on an independent cloud, understand how it works, then grow from one useful node to a resilient Docker Swarm platform.
$ pnpm run doctor -- --json
{ "ok": true, "passed": 18, "failed": 0 }Illustrative handoff · commands stay visible · actions follow your authorization
Two ways in · one operating model
Manual mode turns the deployment into a course. Agent mode compresses the same work into a reviewed plan and verified execution. Nothing important becomes a black box.
Read the architecture and identify what Heat, Ansible, Swarm, and Traefik each own.
The agent reads the operating contract and explains the same ownership boundaries before acting.
Create the cloud user, place clouds.yaml, and run every local prerequisite check yourself.
Provide the protected credential file; the agent diagnoses readiness without asking you to paste secrets.
Inspect the Heat environment, chosen image, network, service shape, and expected cost line by line.
Receive a compact plan with the exact stack, resources, changes, cost, and stop points.
Type the declarative command and follow Heat, host configuration, Swarm, ingress, and monitoring.
Approve the displayed plan once; the agent reconciles the same declared files and narrates progress.
Read the verifier output and account for each node, replica, certificate, endpoint, and boundary.
Get the same machine-readable evidence summarized with failures, limits, and the smallest next action.
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
Built for agents · clear for people
People and coding agents inspect the same contexts, replicas, task errors, endpoint checks, and operation history. Sensitive actions still stop for an explicit human decision.
A useful agent brief
“Diagnose my-service. Show me the failed check and the smallest declarative fix. Do not deploy until I approve.”See the agent operating contract →
{
"app": "my-service",
"ok": false,
"replicas": "1/2",
"https": 503,
"next": "inspect failed task"
}Show the receipts—and the limits
TOAD distinguishes a recorded result from an architectural promise. Recovery procedures state exactly what was restored and what remains to be tested.
Cloud resources, Swarm, ingress, monitoring, and routes can be reconciled from the repository and protected operator inputs.
Platform volumes have bounded age-encrypted backup and exact-volume restore procedures.
Three managers protect quorum, not application data. Stateful services need an explicit storage and recovery profile.
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.