Choose a prebuilt oCMS archive for your platform. Each archive includes the CMS binary, embedded admin assets, core themes and built-in modules, the README, and the license. Go and Node.js are not required to run a prebuilt binary.
Review the release details and upgrade requirements below, then use the platform-specific quick start to run oCMS locally. Keep your database, uploads, custom themes, and configuration when updating an existing site.
Latest stable release
Read the latest release notes before installing or upgrading.
Browse the local release history for previous changes and upgrade context.
Choose your download
These links always download the latest stable release from GitHub. Choose the archive for your platform; all archives are .tar.gz files.
Download SHA-256 checksums. Verify the archive before extracting or running it. GitHub build-provenance attestations are also available for these archives.
Reviewed release information: v0.30.0
The details below were checked for v0.30.0 on 2 November 2026. Download links above follow the latest stable release; use its release notes for current changes and requirements.
- Published: 24 October 2026, 00:54 CEST (23 October, 22:54 UTC).
- Release channel: Stable.
- License: GNU GPL v3.0 or later.
- Release information checked: 2 November 2026.
Read the v0.30.0 release notes.
What is new in v0.30.0?
- Authenticator-app two-factor authentication and single-use recovery codes for administrator, editor, and public accounts.
- Password confirmation for sensitive account changes and DB Manager activation.
- Deployment and production-data sync scripts report failed health checks when an instance fails to start.
- Updated dependencies and Go 1.27.3 for source builds.
Important upgrade requirement
Production requires two-factor authentication by default. Configure OCMS_MFA_KEY with at least 32 bytes, distinct from OCMS_SESSION_SECRET. Keep the MFA key stable and back it up with the database. Existing users enroll an authenticator at their next sign-in. Read the breaking changes before upgrading; server startup applies pending database migrations.
Follow the complete upgrade walkthrough to rehearse the release, back up the site, install the verified binary and recover the old installation if necessary.
Verify build provenance
Optionally verify an archive's build provenance with the GitHub CLI before extracting it. For the Linux AMD64 download:
gh attestation verify ocms-linux-amd64.tar.gz --repo olegiv/ocms-go
Source code and earlier releases
Prefer to explore first? Try the live oCMS demo in your browser.
Explore the admin interface. Content editing is disabled in the shared demo; sample data resets daily.
Open demo admin (opens in a new tab)