Introducing Joule Cloud

A green neocloud you can sign up for in a minute and pay for in joules. Today we're opening it up.

Today we're opening Joule Cloud to everyone with an email address and $5.

The shape: a green neocloud you sign up for in a minute, ship workloads to in another minute, and pay for the energy they consume — measured in joules, at the silicon, on every request. No reserved hours. No egress lock-in. No invoice surprises.

The internals: a 101-node mesh across Hetzner, Vultr, Latitude, and a handful of edge providers. Inference is OpenAI-compatible (run chat.completions.create(model="auto") and the router picks the cheapest capable silicon). Object Store is S3-compatible. Database is Postgres-wire compatible with pgvector built in. Functions, Compute, and a video-meeting service round out the surface.

The pitch is honest about scope: we don't have all 200 AWS services, we don't have customer logos on the homepage yet, and we're SOC 2 in flight, not in hand. What we do have is the wedge: billed in joules, signed receipts, free in-mesh egress. For a class of workloads — anything where the energy bill is a meaningful share of the total bill, and anything that needs audit-ready ESG evidence — that wedge is enough.

What you can do today

• Move your OpenAI workload in two lines. Change the base_url and api_key. The SDK keeps working. See the guide.
• Move your S3 buckets without changing any application code. Point the AWS SDK at our endpoint, run rclone copy s3:/bucket jc:/bucket, done.
• Run a Postgres-wire workload against JouleDB. Same drivers, same pg_dump/restore.
• Ship a container with a 12-line invisible.hcl. The carbon-aware scheduler picks where; you pay for the joules.

How we got here

We've been building the substrate (called Invisible) for two years, source-available on git.openie.sh. Last six months: brought up the mesh in production, wired billing to per-request RAPL/NVML reads, shipped the inference layer, generated the first 10 million signed receipts. Last six weeks: built out the surface APIs, the portal, the docs you can read at docs.greenjoules.cloud.

What's next

The roadmap by quarter is in the changelog. The highlights: SOC 2 Type 2 in Q4, multi-region by default for Compute, FedRAMP via the Oracle partnership in 2027, the energy-budgeted programming language (Joule) reaching v1 in 2027.

How to start

1. Go to portal.greenjoules.cloud, sign in with a passkey, put $5 on file.
2. Mint a token. Scope it.
3. Make a request. Look at the X-Energy-Joules header in the response.

If you stumble: [email protected] reaches a small team that reads everything. If you have a workload that doesn't fit the substrate, tell us; the early customers shape the roadmap.

Welcome.

— David