# Keygen changelog > Software licensing and distribution API, self-hostable as Keygen CE. - Vendor: Keygen - Category: Developer Tools - Official site: https://keygen.sh - Tracked by: What's New (https://whatsnew.fyi/product/keygen) - Harvested from: GitHub (keygen-sh/keygen-api) - Entries below: 5 (newest first) What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. ## Releases ### v1.7.0 — The one introducing Clickhouse - Date: 2026-06-23 - Version: v1.7.0 - Original notes: https://github.com/keygen-sh/keygen-api/releases/tag/v1.7.0 - Permalink: https://whatsnew.fyi/product/keygen/releases/v1.7.0 Upgrade to the `keygen/api:latest` or `keygen/api:v1.7` image. This release follows our twice-yearly release cadence for Keygen CE/EE and introduces a new Clickhouse database system backing request and event logs, replacing the Postgres request and event log tables, in addition we've introduced new private API analytics endpoints used by [Portal](https://github.com/keygen-sh/keygen-portal), support for Postgres replicas, connection poolers, cursor pagination, among various bug fixes. > [!WARNING] > **The new Clickhouse database is only applicable to Keygen EE. It is *required* in order to continue using request and event logs.** Legacy request and event logs stored in Postgres will remain available, but will no longer be accessible through the API. ##### Configuration To enable the Clickhouse database in Keygen EE, configure the following environment variables: ``` CLICKHOUSE_DATABASE_URL=clickhouse://... CLICKHOUSE_DATABASE_ENABLED=1 ``` To enable a replica Postgres database, configure the following: ``` REPLICA_DATABASE_URL=postgres://... REPLICA_DATABASE_ENABLED=1 ``` It's recommended to configure a database before enabling it. ##### Migrations This release will include a new database (EE), multiple database migrations, including data migrations, so we recommend taking a database backup beforehand and performing the upgrade during off-peak hours where possible. ```bash docker pull keygen/api:latest ``` After deploying, but before "rolling over the release," run the following commands in the container, where applicable: If you're running Keygen EE and have Clickhouse configured, provision Clickhouse: ```bash rake db:schema:load:clickhouse # provision Clickhouse ``` Then, migrate the databases normally: ```bash rake db:migrate # apply database migrations ``` After deploying and running the migrations, run the following commands in the container to seed any new data: ```bash rake db:seed # adds new permissions and event types ``` You may now "roll over" the release, i.e. route traffic to the new containers and shut down old containers. For more information on database migrations, see [the Rails documentation](https://guides.rubyonrails.org/active_record_migrations.html). --- For more information on upgrading, [see the docs](https://keygen.sh/docs/self-hosting/#upgrading). For all changes, [see the changelog](https://keygen.sh/changelog/). ### v1.6.0 — ECDSA P-256, memory/disk metering, and cross-env auth - Date: 2026-01-12 - Version: v1.6.0 - Original notes: https://github.com/keygen-sh/keygen-api/releases/tag/v1.6.0 - Permalink: https://whatsnew.fyi/product/keygen/releases/v1.6.0 Upgrade to the `keygen/api:latest` or `keygen/api:v1.6` image. This release follows our twice-yearly release cadence for Keygen CE/EE and introduces support for ECDSA P-256 cryptographic signatures, memory and disk metering and consumption for machines, a more straight-forward cross-environment authentication scheme for admins, expanded metadata support, among various bug fixes. This release will include multiple database migrations, including data migrations, so we recommend taking a database backup beforehand and performing the upgrade during off-peak hours. ```bash docker pull keygen/api:latest ``` After deploying, but before "rolling over the release," run the following command in the container to migrate the database: ```bash rake db:migrate # apply database migrations ``` After deploying and running the migrations, run the following commands in the container to seed new data: ```bash rake db:seed # adds new permissions and event types ``` You may now "roll over" the release, i.e. route traffic to the new containers and shut down old containers. For more information on database migrations, see [the Rails documentation](https://guides.rubyonrails.org/active_record_migrations.html). For more information on upgrading, [see the docs](https://keygen.sh/docs/self-hosting/#upgrading). For all changes, [see the changelog](https://keygen.sh/changelog/). ### v1.5.0 — Multiplayer mode, SSO, Docker/OCI engine, and more - Date: 2025-06-20 - Version: v1.5.0 - Original notes: https://github.com/keygen-sh/keygen-api/releases/tag/v1.5.0 - Permalink: https://whatsnew.fyi/product/keygen/releases/v1.5.0 Upgrade to the `keygen/api:latest` or `keygen/api:v1.5` image. This release follows our twice-yearly release cadence for Keygen CE/EE and introduces support for our [OCI engine](https://keygen.sh/docs/api/engines/#engines-oci), allowing you to distribute Docker and OCI container images to licensed users using [our new OCI-compliant container image registry](https://conformance.opencontainers.org/#keygen). It also introduces the option for multiplayer mode in Keygen EE, i.e. multi-tenant installations, as well as SAML/SSO. This release will include multiple database migrations, including data migrations, so we recommend taking a database backup beforehand and performing the upgrade during off-peak hours. ```bash docker pull keygen/api:latest ``` After deploying, but before "rolling over the release," run the following command in the container to migrate the database: ```bash rake db:migrate # apply database migrations ``` After deploying and running the migrations, run the following commands in the container to seed new data: ```bash rake db:seed # adds new permissions and event types ``` You may now "roll over" the release, i.e. route traffic to the new containers and shut down old containers. For more information on database migrations, see [the Rails documentation](https://guides.rubyonrails.org/active_record_migrations.html). For more information on upgrading, [see the docs](https://keygen.sh/docs/self-hosting/#upgrading). For all changes, [see the changelog](https://keygen.sh/changelog/). ### v1.4.0 — Rubygems, npm, imports and exports - Date: 2025-01-20 - Version: v1.4.0 - Original notes: https://github.com/keygen-sh/keygen-api/releases/tag/v1.4.0 - Permalink: https://whatsnew.fyi/product/keygen/releases/v1.4.0 Upgrade to the `keygen/api:latest` or `keygen/api:v1.4` image. This release introduces support for [Rubygems](https://keygen.sh/docs/api/engines/#engines-rubygems) and [npm](https://keygen.sh/docs/api/engines/#engines-npm) distribution engines. In addition, this release brings support for [importing and exporting data](https://keygen.sh/docs/self-hosting/#migrating) between Keygen Cloud and Keygen CE/EE. This release will include multiple database migrations, so we recommend taking a database backup beforehand and performing the upgrade during off-peak hours. ```bash docker pull keygen/api:latest ``` After deploying, but before "rolling over the release", run the following command in the container to migrate the database: ```bash rake db:migrate # apply database migrations ``` After deploying and running the migrations, run the following commands in the container to seed new permissions: ```bash rake db:seed # adds new permissions and event types ``` You may now roll over the release, i.e. route traffic to the new containers and shut down old containers. For more information on database migrations, see [the Rails documentation](https://guides.rubyonrails.org/active_record_migrations.html). For more information on upgrading, [see the docs](https://keygen.sh/docs/self-hosting/#upgrading). ### v1.3.0 — Multi-user licenses and more - Date: 2024-06-18 - Version: v1.3.0 - Original notes: https://github.com/keygen-sh/keygen-api/releases/tag/v1.3.0 - Permalink: https://whatsnew.fyi/product/keygen/releases/v1.3.0 Upgrade to the `keygen/api:latest` or `keygen/api:v1.3` image. This release will include multiple database migrations, so we recommend taking a database backup beforehand and performing the upgrade during off-peak hours. Depending on your data's size, some migrations could take up to a few minutes as data is migrated. But for most self-hosted installs, each migration should be quick. ```bash docker pull keygen/api:latest ``` After deploying, but before "rolling over the release", run the following command in the container to migrate the database: ```bash #### Migrate the database rake db:migrate ``` After deploying and running the migrations, run the following commands in the container to seed new permissions: ```bash #### Add new permissions and event types rake db:seed #### Migrate existing role permissions rake keygen:permissions:admins:add[license.users.attach,license.users.detach,license.owner.update,machine.owner.update] rake keygen:permissions:environments:add[license.users.attach,license.users.detach,license.owner.update,machine.owner.update] rake keygen:permissions:products:add[license.users.attach,license.users.detach,license.owner.update,machine.owner.update] ``` After running the above, and you have a large database, you may also want to vacuum the following tables: ```sql #### Vacuum these tables to improve performance of large tables VACUUM ANALYZE licenses; VACUUM ANALYZE users; ``` You may now roll over the release, i.e. route traffic to the new containers and shut down old containers. For more information on database migrations, see [the Rails documentation](https://guides.rubyonrails.org/active_record_migrations.html). For more information on upgrading, [see the docs](https://keygen.sh/docs/self-hosting/#upgrading).