The Cloaky public beta has ended

The v0.2 beta is closed. Cloaky Base, free and running on Venice, becomes the product everyone can run. Cloaky Pro goes into a private build on what the beta taught us.

The public beta of Cloaky ran from v0.2.0 on August 12 to v0.2.10 on September 11, on macOS and Linux. It is now closed. This post says what the beta was, what we took from it, and what comes next.

What the beta was

Eleven releases in a month. Each one shipped the whole workbench: every engine, every provider, local models, direct provider keys, Venice, fleet, bots and squads. Anyone could download it and run it on real work. People on both platforms did, and they wrote back. The feedback was specific, generous, and there was more of it than we expected. Thank you for it.

What we took from it

The part people kept naming was the route. They liked seeing the engine, the provider and the privacy tier where the work happens, and they asked us to protect that.

Read together, the feedback also kept raising a few ideas about what an agent workbench should do for the person running it. They need time and a small group of people who will use them on real work before we say more.

The split

Cloaky becomes two products.

Cloaky Base is free. Every session runs on Venice, on the model and privacy tier you pick. Five engines, all on Venice models: Claude Code, OpenCode, Codex, Kimi Code and Grok Build. Nothing routes anywhere you did not turn on.

This is where we want to contribute first: to Venice, and to private tooling that the person doing the work controls. Base is that as a whole product, in the open, for everyone.

Cloaky Pro is the full workbench. It has every engine, including Cursor and Prime Agent, local models through Ollama and LM Studio, direct providers, and fleet, bots and squads. Pro goes into three months of private build on the ideas above. We will describe them when they exist.

What happens to the beta

The beta downloads and the beta release page go private. An installed beta keeps working, but it will not receive updates.

If you ran the beta and told us what you found, that is the reason the split looks the way it does.

How to get Pro

Pro has no public download during the private build. If you want it, email hello@cloaky.dev and say what you would do with it. A person reads every message, and we are choosing a small group to build with.

That group is the user study: people who help us build Pro, and who get Pro for it.

What’s next for Base

The first release is v0.1.1. The number restarts because Base is a new product line. Downloads will be on this site the day it ships, and the changelog picks up from there.

The source is not on GitHub yet. It opens at v0.1.10, after ten releases.

Base will be open source under MIT, as Cloaky always has been. First we want ten releases of evidence that it does what we say. That means privacy that holds, turns that run on the model you picked, and builds that install on machines that are not ours. Ten releases is enough to find the parts that only break on someone else’s computer.

The second reason matters more to us. Opening a repository is a promise to look after it. Issues get read, pull requests get answered, and somebody is there when a contributor takes the trouble to send one. We have all seen the repositories where that stopped, where a good patch sat for a year until the person who wrote it gave up. We would rather open late than do that to anyone. So we are putting tooling in place first, with Jev, to triage what arrives. It has to tell the patches worth merging from the ones that would cost us, and keep up with that load before we invite it.

Ten releases, then the source. We will say so here when it happens.