Weights stay open, the license stays plain.
Two flagship checkpoints per year ship under Apache 2.0 with reproducible training logs — no audit clause, no field-of-use rider, no email gate.
Apache 2.0 · reproducible logsWhat stays continental
Four commitments the model
will not negotiate.
A short read of how Mirage keeps weights, evaluation and data residency under continental governance — without slowing the open-source release cadence our developer cohort depends on.
Inference resides in-region by default.
Three continental clusters in Paris, Frankfurt and Stockholm route requests without leaving jurisdiction; cross-border calls require an explicit per-tenant toggle.
3 clusters · explicit egressEvaluation is public, dated, signed.
Every release ships with a 240-task evaluation card, the eval set hash, and the date the suite was frozen — so regressions can be argued, not asserted.
240 tasks · sha256 frozenCadence beats announcements — always.
A new minor release every six weeks, a major every six months; deprecation windows run twelve months, never less, so production teams plan past the news cycle.
6-week minor · 12-month deprecation