Private cloud platform

Your own cloud.
On your own hardware.

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

One command per machine.
That's the whole setup.

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>
A real session, shortened. Nothing staged.
01 / SETUP

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 join
02 / RESILIENCE

Heals itself.

When 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 · recover
03 / AVAILABILITY

No single point of failure.

Run the control plane on three machines. Lose one, including the leader, and another takes over in seconds.

3 replicas · automatic failover
04 / STORAGE

Storage built in.

S3-compatible object storage, replicated across your machines and managed like everything else.

S3 API · buckets · access keys
~40 MiB
of RAM per control plane replica. The rest of your hardware belongs to your workloads.
1
command to add a machine – x86 or ARM, from a mini PC to a server.
3
replicas for a control plane that keeps running when a machine doesn't.

Progress

Shipped step by step.
Every milestone ends in a working release.

Seven milestones done, the eighth up next. Updated with every release.

  1. 01 · done

    Machines join

    Secure enrollment with certificates and one-time tokens.

  2. 02 · v0.1

    Containers via API

    Schedule containers onto any machine with one call.

  3. 03 · v0.2

    Self-healing

    Failed machines are detected, their containers move.

  4. 04 · v0.3

    Web console

    See and manage machines and containers in the browser.

  5. 05 · v0.4

    No single point of failure

    Three control plane replicas with automatic failover.

  6. 06 · v0.5.0

    Object storage

    S3-compatible buckets and keys, replicated. First release.

  7. 07 · v0.6.0

    Tenants & access

    Accounts, users, policies and sign-in. Containers isolated per tenant.

  8. 08 · up next

    Full web console

    Users, policies and every service, managed in the browser.

What's next

The building blocks of a cloud. One at a time.

  • Private networks

    Isolated networks that span all your machines.

  • Load balancers

    Host names, HTTPS and health checks in front of your services.

  • Block storage & snapshots

    Volumes for containers and virtual machines, with snapshots.

  • Virtual machines

    Lightweight VMs next to your containers.

  • Infrastructure as code

    Describe your setup once, apply it anywhere.

  • Queues

    Reliable messaging between your services.

  • Key-value database

    A managed key-value store with its own API.

  • Functions

    Run code without thinking about containers.

Contact

Get in touch.

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.