Why we serve open-weight models only
Every model in the catalogue is one you could run yourself. What that means for lock-in, for auditability, for licensing, and why a closed model could not work in a distributed pool anyway.
Every model we serve is one you could download and run on your own hardware. That is a constraint we chose, and it shapes the product more than any other decision.
You are never locked in
If we raised prices tomorrow, or went away, your application keeps working: same weights, same API shape, a different endpoint. That is a weak position for a vendor and a strong one for a customer, which is roughly the point. It also means our pricing has to stay honest — the exit is always one base URL away.
It is the only thing that could work here
A distributed pool means model weights sit on machines we do not own. No proprietary model licence permits that, and no amount of engineering makes it permissible. Open weights are not a philosophical flourish on top of the architecture; they are what makes the architecture legal.
Auditability, all the way down
- Every build is pinned to an exact upstream revision with a published SHA-256, so "which weights answered me" has one verifiable answer.
- The agent that runs them is open source, and its releases are checksummed.
- The engine is a pinned upstream release, verified before it runs.
You can reproduce the whole stack. We would rather compete on price, latency and honesty than on being the only ones who know what is inside.
Licences, taken seriously
Apache-2.0 and MIT models are straightforward. Others — Gemma's terms, for instance — carry usage conditions we read before adding a model, and the licence is shown on every catalogue entry rather than buried. If a model's terms do not permit what we do, it does not go in, however good the benchmarks look.
What we give up
The frontier closed models are, on some tasks, still ahead. We are not going to pretend otherwise. What the open catalogue gives you instead is a price several times lower, weights you can inspect, and an EU-sovereign path that does not exist for a model you are not allowed to move. For a great many workloads that trade is obviously right; for some it is not, and you should use the right tool.
Related
Model catalogue · Download mahout · How the whole system works · Blog