Concepts

Conceptual documentation for the Rumi Platform private cloud model and its environment bindings.

Environment Bindings

• AWS Binding - Feature catalogue for deploying the Rumi private cloud on AWS (topologies, access posture, bastion model, access and security, HTTPS, observability, tagging, lifecycle).

• Hetzner Binding - Feature catalogue for deploying the Rumi private cloud on Hetzner Cloud (prebaked-snapshot model, public-only topology, bastion DNS, per-role firewalls, pluggable HTTPS, lifecycle).

• Civo Binding - Feature catalogue for deploying the Rumi private cloud on Civo (install-at-boot model, bastion DNS, pluggable HTTPS, cost-saving start/stop, lifecycle).

One command vocabulary across providers

All three providers — AWS, Hetzner, and Civo — now share a single command vocabulary. Every role and service has its own per-component lifecycle verbs (start-admin, stop-solace, terminate-monitor, …); start-platform / stop-platform / terminate-platform act on the whole platform; an env-wide start / stop acts on every instance in a network; and deprovision tears an environment down. This means the workflow you learn on one provider transfers to the others.

Two honest gaps remain, by design:

• The whitelist family is AWS-only. Hetzner and Civo firewalls are open-by-default within the network (label/CIDR rules), so there is no whitelist / unwhitelist / whitelist-ssh / unwhitelist-ssh to selectively open a proxied port to a CIDR.

• A few AWS-only verbs remain, by provider capability. create-zone / list-zones (Route 53 hosted zones) and attach-volume / resize-volume (EBS) are AWS-specific and have no Hetzner/Civo analogue. (All three providers do share create-network / list-networks / delete-network / deprovision.)

Note: This section is under development; more binding and concept pages are being added.