Open infrastructure, end to end

Own your cloud.
Keep your exit.

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.

toad / apply

$ pnpm run apply -- my-cloud

✓ Heat resources reconciled

✓ Swarm managers healthy 3 / 3

✓ Traefik HTTPS ready

✓ Monitoring targets up 18 / 18

✓ Acceptance checks passed

PLATFORM READYreproducible · observable · yours
OPENSTACKHEATANSIBLEDOCKER SWARMTRAEFIK

What it gives you

Cloud primitives,
shaped into a platform.

TOAD keeps the infrastructure understandable while adding the contracts a maintained service needs.

01

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
02

Routing that feels native

Traefik discovers Swarm services from labels, obtains HTTPS certificates and sends traffic through a shared overlay—without publishing application ports.

  • Traefik
  • Automatic HTTPS
  • Swarm labels
03

Operations with evidence

Machine-readable diagnosis, external probes, metrics, logs, alerts and declared acceptance checks make failures explainable to people and agents.

  • Prometheus
  • Grafana
  • Loki
04

Guardrails by default

Immutable images, resource limits, rollback policy, encrypted backups and mTLS-protected administration are enforced before a service is deployed.

  • mTLS
  • age
  • Policy checks

One contract, two scales

Start with what you need.
Keep the path forward.

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

One useful node

The same routing, certificates, monitoring and application contract on the smallest practical footprint.

  • 1 manager
  • Direct ingress
  • Best for evaluation and small services
Internet
Public IP
Manager 1
Traefik
Apps
Observe

A closed operational loop

Declare. Reconcile.
Prove. Repeat.

Every normal change returns to declared state and ends with evidence. Agents can follow the same narrow runbooks as a human operator.

  1. 01doctor

    Prove the workstation

    Check tools, credentials and safe local state without exposing secret contents.

  2. 02apply

    Reconcile the platform

    Create or update cloud resources, hosts, Swarm, ingress, DNS and monitoring.

  3. 03app deploy

    Ship declared services

    Validate policy, deploy with rollback and run the application’s HTTPS checks.

  4. 04verify

    Keep the receipt

    Measure quorum, replicas, DNS, TLS, routes and monitoring in one JSON report.

Before an application reaches the cluster

Immutable imageNo public portsMemory boundedRollback declaredHTTPS checkedBackups explicit

Choose deliberately

Swarm is a feature
when simplicity matters.

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.

ConsiderationTOAD / SwarmKubernetesManaged PaaS
Starting footprint1 managerControl plane + workersProvider-defined
Operational surfaceSmallLargeSmall
Infrastructure ownershipYour OpenStack projectYour clusterProvider account
Application routingTraefik labelsIngress resourcesPlatform-specific
Exit pathHeat + Compose + backupsCluster manifests + backupsVaries by provider

Kubernetes remains a possible separate provider—not a hidden mode that makes Swarm harder to understand.

GNU AGPL-3.0-or-later

Your infrastructure should
remain yours.

Use it, study it, adapt it for clients, and keep the complete system reproducible.