Octomind Cloud Is Live: Real Machines for Your Agent, Every Model Through One Key | Octomind

Today Octomind Cloud goes live in beta. Before I tell you what it is, let me tell you the three problems that made us build it — because odds are you have at least two of them right now.<br>Your agent lives and dies with your laptop. You kick off a long refactor, the agent is forty minutes into it, and then you need to close the lid, catch a train, or your Wi-Fi hiccups. The session is gone, the context is gone, and the tokens you paid for produced work you'll never see. Agents are long-running processes; laptops are not long-running machines.<br>Your API keys live in five dashboards. OpenRouter for the cheap models, Anthropic for the good ones, OpenAI because some tool demands it, Voyage for embeddings, and a .env file that's one git add -A away from being public. Every provider has its own billing page, its own rate limits, its own "add $5 minimum" — and no single view of what your agent actually spends.<br>Your AI bill is a mood, not a number. Seat-priced tools give you rate-limit roulette — an opaque allowance that resets on someone else's schedule. Usage-priced tools give you the opposite fear: nothing stops a runaway agent from burning $80 overnight. Neither shows you a per-token price or lets you watch the meter.<br>Octomind Cloud is our answer to all three. It's two things that share one subscription, one wallet, and one key: the hub (models) and machines (compute). This post is the map of everything that's live today — each section deserves its own deep dive, and those are coming. But this one piece should tell you exactly what you're getting, economics included, because pricing you can't reason about is a bug, not a business model.<br>The hub: log in once, every model works<br>The hub is an OpenAI-compatible gateway in front of a curated model roster — one key, every model works, in the panel, in the CLI, in any tool that speaks the OpenAI API:<br>bash<br>curl https://hub.octomind.run/v1/chat/completions \<br>-H "Authorization: Bearer $OCTOMIND_KEY" \<br>-d '{"model": "deepseek-v4-flash", "messages": [{"role": "user", "content": "hi"}]}'<br>If you're using the CLI you don't have to handle that key at all. As of 0.38.0, octomind login shows you a short code, opens the panel where you're already signed in, and writes the key to disk itself:<br>text<br>$ octomind login<br>╭ login · octomind account<br>│ code TX8T-UC7U<br>│ url https://octomind.run/app/login/cli<br>│ Confirm the code in your browser to finish signing in.<br>│ waiting…<br>It's the standard device flow — the same one gh auth login uses — so no password is ever typed into a terminal, each machine gets its own revocable key, and the /usage command tells you what you've spent against your caps without opening the panel.<br>No provider accounts. No key sprawl. And the part I care most about: published prices, and metering that matches the table exactly.

The roster is deliberately curated, not a 400-model dropdown — twenty-one models that earn their place. The open shelf (DeepSeek V4 Flash and Pro, Qwen3.7 Plus and Max, Kimi 2.6 and 2.7 Code, MiniMax M3, GLM-5.2, Gemma 4) is included in every paid plan and draws from your plan caps. The premium shelf bills per token from prepaid credits, and it's the real thing: Claude Fable 5, Opus 4.8 and Sonnet 5; the whole GPT-5.6 family (Sol, Terra, Luna) with GPT-5.5, 5.5 Pro and the fast little 5.4 mini and nano; Gemini 3.5 Flash and 3.1 Pro. You see every price before you pick. And there's a free model with a daily allowance that keeps working even when everything else is exhausted, because an agent that goes completely dark the moment you hit a cap is worse than a slow one.<br>Fair use is per account , not per key: Free runs one model call at a time, Pro two in parallel, Max five, Team fifteen pooled. Mint a thousand keys and the budget doesn't move — and past it, requests queue briefly instead of failing. It's the anti-abuse rule that doubles as a noisy-neighbor guarantee: nobody's runaway script makes your completion wait.<br>Under the hood this is octohub — open source, Rust, one static binary. The hosted hub is the same code with the keys problem solved. Want to run it yourself with your own provider keys? That's not a loophole — it's the point of publishing it.<br>Machines: a dev box that exists whether or not your laptop does<br>A machine is a persistent Linux container in our cloud with the whole agent toolchain baked in — your files, your repos, your indexes, persisted on its own disk. It's got: octomind (the agent), octocode (code indexing + semantic search), octobrain (memory), a web terminal, git, Docker (more on that in a minute), and — on the default image — Node, bun, a headless browser, ffmpeg and image tools. You create one in the panel, it's ready in under a minute, and it's yours.

The billing model is the part I want to defend in detail, because it's where most clouds get either opaque or hostile. A machine is always in one of three states, and the state...