Sheeternetes runs your containers on the only runtime humanity already trusts with its most critical data: the Google Sheet. No clusters. No etcd. No YAML. Just Infinite Power, one row at a time.
Kubernetes solved container orchestration by adding a distributed operating system, a consensus database, and sixty-three resource types. Sheeternetes solves it by opening a spreadsheet. One of these you can explain to your CFO.
The control plane is a Google Sheet. Nothing to provision, patch, or page you at 3am. Google keeps the lights on; you keep the tab open.
Workloads are rows. If you must serialize, we emit JSON — which is merely YAML that has already compiled. Indentation-related outages: eliminated.
State lives in cells. The source of truth is a thing your whole company can already read, filter, and accidentally sort by column B.
A real control loop: heartbeat-driven scheduling, self-healing on node loss,
restart-on-crash, and rolling updates with maxUnavailable=1.
A shared Docker network with service aliases gives you service discovery and basic load balancing — Services, without the CRDs.
Point ./sheetlux at a directory of manifests and it syncs desired state
into the Sheet. Declarative delivery, spreadsheet-native.
Your dashboard is the Deployments tab. Conditional formatting is your alerting stack. Mean time to insight: one glance.
The most cost-optimized orchestrator in the industry, because the industry forgot to check whether a spreadsheet counts. It does now.
| Sheeternetes 💩 | Kubernetes | HashiCorp Nomad | Docker Swarm | Cloud Foundry | |
|---|---|---|---|---|---|
| Control plane | A Google Sheet | etcd + API server + controllers + scheduler | Raft + server nodes | Raft-backed managers | BOSH + Diego |
| Lines of YAML for hello-world | 0 (we use JSON) | ~40 | ~15 (HCL) | ~12 | a manifest and a prayer |
| Distributed consensus DB required | No — it's a Sheet | Yes (etcd) | Yes (Raft) | Yes (Raft) | Yes |
| Editable by your CFO | Yes | No | No | No | Absolutely not |
| Learning curve | One afternoon | One career | One week | One weekend | One reorg |
| Observability | Open the tab | Prometheus + Grafana + a team | Metrics API | Limited | Loggregator |
| Spreadsheet-native | ✅ Only us | ❌ | ❌ | ❌ | ❌ |
| Control-plane cost | $0 | $$$ | $$ | $ | $$$ |
| Time travel (undo) | Ctrl+Z (revision history) | No | No | No | No |
| Safe for production at scale | Please don't | Yes | Yes | Yes | Yes |
| Governed by | Sheet-Native Computing Foundation | CNCF | HashiCorp | Docker | CF Foundation |
Apps Script is the API server, scheduler, and reconcile loop. The Google Sheet
(tabs: Deployments, Nodes, Pods, Events) is etcd. kubelet.sh on your Docker
hosts is the kubelet; skctl is your kubectl. Nodes heartbeat the API server,
the scheduler bin-packs by CPU and memory, and the loop keeps desired state and
reality in agreement. It is exactly Kubernetes, if Kubernetes were a spreadsheet and also
a joke.