Set up in minutes, not weekends.
One command starts a cluster, one command adds a machine. Certificates, trust and configuration are handled for you.
granger init · granger joinPrivate cloud platform
Granger turns a handful of machines – mini PCs, servers, ARM boards – into a self-healing cloud with containers, object storage and a web console. No Kubernetes degree required.
126 nodes · leader elected · healthy
Everything else – certificates, trust, configuration, recovery – is handled for you.
node-1:~# granger init service granger-controlplane: enabled, started CA certificate published as /etc/granger/ca.crt control plane ready; join a node by running this as root on it (valid until …, up to 10 nodes): granger join 10.0.0.10:7443 --token … --ca-cert-hash sha256:… node-1:~# granger join 10.0.0.10:7443 --token … --ca-cert-hash sha256:… --no-compute preflight: all 8 checks passed compute: off (--no-compute): no containers are placed on this node node node-1 joined as node-01M7RH0Y398Q5Z2DT4J9TZBFVX and is connected; … node-2:~# granger join 10.0.0.10:7443 --token … --ca-cert-hash sha256:… preflight: all 8 checks passed compute: on (CPU and memory for containers; --no-compute turns it off) node node-2 joined as node-01M7RH0YR0CG0M2F9QJRW5K396 and is connected; … node-3:~# granger join 10.0.0.10:7443 --token … --ca-cert-hash sha256:… preflight: all 8 checks passed node node-3 joined as node-01M7RH0ZCB2Y9VE8HE4BNZF4KP and is connected; … node-1:~# granger node list NAME STATUS ROLES FEATURES ARCH CPU MEMORY LABELS LAST SEEN node-1 Ready storage disk=hdd amd64 4 11.6Gi <none> 2s node-2 Ready compute,storage disk=hdd amd64 4 11.6Gi <none> 2s node-3 Ready compute,storage disk=hdd amd64 4 11.6Gi <none> 1s node-1:~# granger container create web --image nginx:alpine --port 80 --cpu 250m --memory 64Mi container web created node-1:~# granger container list NAME STATUS NODE ENDPOINTS AGE web Running node-2 80=10.0.0.11:30000 4s node-1:~# curl -s http://10.0.0.11:30000/ | grep title <title>Welcome to nginx!</title> # node-2 loses power … 81 s later node-1:~# granger container list NAME STATUS NODE ENDPOINTS AGE web Running node-3 80=10.0.0.12:30000 1m node-1:~# curl -s http://10.0.0.12:30000/ | grep title <title>Welcome to nginx!</title>
One command starts a cluster, one command adds a machine. Certificates, trust and configuration are handled for you.
granger init · granger joinWhen a machine fails, Granger notices within seconds and, after a short grace period, moves its workloads to healthy machines – no pager, no manual steps.
detect · reschedule · recoverRun the control plane on three machines. Lose one, including the leader, and another takes over in seconds.
3 replicas · automatic failoverS3-compatible object storage, replicated across your machines and managed like everything else.
S3 API · buckets · access keysSeven milestones done, the eighth up next. Updated with every release.
Secure enrollment with certificates and one-time tokens.
Schedule containers onto any machine with one call.
Failed machines are detected, their containers move.
See and manage machines and containers in the browser.
Three control plane replicas with automatic failover.
S3-compatible buckets and keys, replicated. First release.
Accounts, users, policies and sign-in. Containers isolated per tenant.
Users, policies and every service, managed in the browser.
Contact
Questions, ideas or a spare machine to try it on? Send a message and I'll get back to you.
Write to hello@granger-cloud.com.
I'll reply to the address you gave me.