TOADSource ↗

Trust boundaries

Small surface, explicit authority.

TOAD treats the operator workstation, Swarm managers, and the Docker socket as privileged. Public applications and administrative interfaces follow different access paths.

Administrative access

Traefik, Grafana, Prometheus, and Alertmanager require short-lived mTLS client certificates. There is no shared dashboard password or JWT issuer to operate.

Application policy

Immutable delivery

Images require SHA-256 digests. Static website releases use content-addressed Swarm configs.

Private images

Registry credentials stay context-scoped, cross the manager only for deployment, and are removed immediately afterward.

Restricted containers

Privileged mode, host namespaces, added capabilities, Docker socket mounts, and direct published ports are rejected.

Known recovery

Stateful volumes declare their backup policy. Platform and application archives are encrypted with age.

Release provenance

Dependency lockfiles are audited in CI, generated website artifacts must reproduce exactly from source, and the published website image includes an SBOM and a keyless signature. Client deployments still use the registry-free, content-addressed static package.

Responsible disclosure

Do not place credentials, tenant identifiers, customer data, or working exploits in a public issue. Use GitHub private vulnerability reporting and rotate anything that may have been disclosed.