> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.getunleash.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.getunleash.io/_mcp/server.

> Review Unleash v8.0.0 release notes, covering the move to AGPLv3, automated release management becoming generally available, the remote MCP server becoming generally available, streaming between Unleash and Edge in beta, improved project onboarding, a redesigned user access overview, and the new sunset flag type.

# Unleash v8.0.0

If you self-host Unleash, review the [v7 to v8 migration guide](/deploy/upgrading-unleash#upgrading-from-v7-to-v8) before you upgrade. No API endpoints were removed, but several deprecated schema properties have been.

## Announcement: Unleash open source moves to AGPLv3

Starting with Unleash v8, the source code in the [primary Unleash GitHub repository](https://github.com/Unleash/unleash) and the [`unleash-server` npm package](https://www.npmjs.com/package/unleash-server) move from the Apache 2.0 license to the GNU Affero General Public License v3 (AGPLv3).

Most users are unaffected:

* Official open-source Docker images remain under Apache 2.0. Running a pre-built Unleash container without modifying the source is unaffected.
* Unleash SDKs keep their current permissive licenses, so your application code is unaffected.
* Unleash Enterprise and Unleash Cloud are unaffected. Your deployment, terms, and obligations are unchanged.

The change applies if you modify the Unleash source and make it available to users over a network, for example as a public or commercial SaaS. In that case, AGPLv3 requires you to make your modified source available under the same license, or to contact us for a commercial license. For the full reasoning and a use-case breakdown, see [Evolving our open source commitment](https://www.getunleash.io/blog/unleash-moving-to-agplv3).

## Automated release management now generally available

[Release templates](/concepts/release-templates), [impact metrics](/concepts/impact-metrics), [safeguards](/concepts/impact-metrics#configure-safeguards), and [milestone progression](/concepts/impact-metrics#automate-release-progression) are now generally available.

Impact metrics are application-level time series, such as counters, gauges, and histograms for error rates, latency, and adoption. They can be recorded by Unleash SDKs or queried from an existing Prometheus or VictoriaMetrics instance. Safeguards let you set thresholds on those metrics that automatically pause a rollout or disable an environment when a metric crosses the limit. Milestone progression advances a release template to its next milestone when the metrics stay healthy for a configured interval, removing the need to step rollouts forward manually.

## Remote MCP server now generally available

The [remote Unleash MCP server](/integrate/mcp#remote-mcp-server) is now generally available. It lets you connect MCP clients to a server hosted by your Unleash instance, without installing anything locally. Use it when developers cannot run MCP servers on their machines, or when you want to manage MCP access centrally.

## Streaming between Unleash and Edge in beta

[Unleash Edge](/unleash-edge) can now receive flag updates from Unleash as a real-time stream instead of polling. Flag changes propagate to your Edge nodes, and to your applications, in milliseconds. Streaming is available on both managed and self-hosted [Enterprise Edge](/unleash-edge#real-time-updates-with-streaming).

## Improved project onboarding

We've further improved the project onboarding experience. The project page now shows a three-step **Project setup** checklist that tracks creating a feature flag, connecting one or more SDKs, and sending flag evaluation metrics back to Unleash. On the flag page, a contextual banner points you to the next step based on your current setup state. SDK setup now also works for any SDK you add to a project, not only the first one.

## Redesigned access overview

The [access overview page](/concepts/rbac#view-a-users-roles-and-permissions) is redesigned to give admins and individual users a clearer view of a user's instance and project access in one place.

## New `sunset` flag type

We introduced a new `sunset` [flag type](/concepts/feature-flags#feature-flag-types) to help you coordinate the planned removal of an existing feature. Use it to wrap a feature you plan to retire, so you can gradually disable it for selected user segments while monitoring the impact, and pause or re-enable the rollout if downstream issues surface.