Operate light.
Ship long.
The most sustainable infrastructure decision is the one that never gets made. A single ARM VM running at 40% utilization produces a fraction of the embodied energy of a Kubernetes fleet running at 15%. We chose architecture over offset. This is our accounting.
01 · The single-VM thesis
We run the entire Zen & Shore platform on one Oracle Cloud Infrastructure ARM A1 instance: 4 OCPUs, 24 GB RAM, always-free tier. This is not a cost hack. It is an architectural stance. A single machine, observed carefully, consumes less energy than five lightly-loaded machines observed badly. The idle draw of a dormant Kubernetes node is not zero.
02 · Litestream and the backup tier
Every SQLite database — control plane, session, cache, ledger — streams WAL segments to Cloudflare R2 every five seconds via Litestream. R2 storage is geographically distributed and uses green-certified datacenters. More importantly, WAL replication uses kilobytes per transaction, not megabytes. We do not run a secondary hot standby that burns 50% of primary compute waiting for a failover that may never happen.
03 · No over-provisioned Kubernetes
The industry default for “production-ready” is now a managed Kubernetes cluster: minimum three nodes, a load balancer, a container registry, log aggregation, a secrets manager, and a monitoring stack. The baseline carbon cost of this setup, before a single request is served, is on the order of 400–600 kg CO₂e per year at a mid-tier cloud region. We opted out. Our monitoring stack is a Telegram bot and a cron job that checks uptime. Our log aggregation is stderr to journald. Our secrets manager is a file with correct permissions.
04 · Carbon-aware deploy timing
Deployments that require VM restarts are scheduled against the OCI Bengaluru region's hourly carbon intensity signal (sourced via the Carbon Aware SDK). We target windows below 200 gCO₂eq/kWh when possible. For a service our size, this is a marginal gain — but it is a marginal gain that costs nothing once the tooling is written, so we wrote it.
05 · Embodied carbon in hardware
We do not own servers. Oracle owns the hardware; we rent OCPU allocation. The embodied carbon of manufacturing the underlying ARM Ampere A1 silicon is amortized across thousands of tenants on the same physical host. Our share is small. It is not zero, and we include an estimate of it in our annual carbon report under “compute (embodied)”.
NOTE: Packaging and shipping dominate. Platform compute is 13% of per-order footprint. We are working with logistics partners on last-mile EV delivery in the Bengaluru metro.
- No blockchain. We do not tokenize supply chains, mint carbon certificates, or use distributed ledgers. The energy cost of a blockchain transaction is not a rounding error.NO BLOCKCHAIN
- No autoplay video. The homepage is a static HTML file. No hero video. No lazy-loading background loops. A 4 MB autoplay video costs roughly 6 g CO₂e per page view. We chose typography.NO AUTOPLAY VIDEO
- No crypto offsets. We do not purchase carbon credits to balance a bloated infrastructure footprint. We reduce actual consumption first. Offsets are for the residual, not the avoidable.WE BURN LESS, PERIOD
PUBLISHED: 2026-03-15
NEXT: 2027-Q1