Releases
Open Model Gateway's releases, what to expect before 1.0, and how releases are published.
| Release | Date | In short |
|---|---|---|
| v0.3.0 | Not yet released | The Files API on an encrypted file store, storage quotas, batches for any model, "jobs at once" limits, the SCIM last-admin guard, realtime holds sized from the conversation, and batch scheduling for self-hosted models. Migrations 0018 to 0022. |
| v0.2.0 | 2026-10-09 | Alerts and notifications, key safety, model compare, SCIM, signing-key refresh, Prometheus metrics, backups, a browser test suite, realtime audio, async jobs, and budget checks that don't slow down with history. Migrations 0011 to 0017. |
| v0.1.0 | 2026-10-08 | The single-enterprise gateway: platform roles, Teams, Projects and personal workspaces, catalogs, price lines, stacked budgets, many workloads and providers, logs, Admin settings and the dashboard. Migrations 0001 to 0010. |
The full history is in the repository's commits and roadmap.
Before 1.0
- It is development software. Each release is tested locally and in CI with mock providers and real PostgreSQL, plus a few small, capped checks against real providers. Production readiness, live identity-provider certification and load testing in your environment are your pilot's job.
- Upgrades only go forward. Migrations can't be undone by changing images; going back past a migration means restoring a backup. Read every release's notes between your version and the target. See Upgrades.
- The management API may change in any release. The inference API follows the vendor APIs it copies.
How releases are published
- Each release is a Git tag,
vX.Y.Z, on the main branch. - From v0.3.0, each release publishes a signed container image to
ghcr.io/ncecere/open-model-gateway, taggedvX.Y.Z,vX.Y(the newest patch of that minor version) andlatest-release(the newest release). Images are signed with cosign keyless signing; check the signature and deploy by digest. See Container and Compose. - Each release's notes are also in the repository, in
docs/releases/(for exampledocs/releases/v0.3.0.md), and the binary reports its release as theversionofgateway_build_info. - You can still build the image from the tag with the repository's
Dockerfile. The manual publishing workflow pushes tested images ofmain, tagged with their full commit SHA, for staging.
What's next
From the roadmap, planned and not yet built: an OpenRouter video adapter, using uploaded files in chat requests, image edits and image input, token-by-token Responses and Messages streaming, native batches for more providers, more of the realtime interface, active health checks, key-expiry notifications and webhooks, and provider-invoice reconciliation. A plan, not a promise.