Unleash

What Is Unleash?

Feature flags have become table stakes for engineering teams that ship frequently. The ability to decouple deployment from release — pushing code to production but controlling who sees it and when — underpins every modern progressive delivery practice, from canary releases to kill switches. The market leader, LaunchDarkly, built a billion-dollar business on this premise. But LaunchDarkly is American, cloud-only, and priced on monthly active users in a way that punishes growth.

Unleash takes a fundamentally different approach. Built by Bricks Software AS in Oslo, Norway, the platform started life as an open-source project in 2019 and has grown into an enterprise-grade feature management platform with over 500 paying customers. In March 2026, the company closed a $35 million Series B led by One Peak, bringing total funding to $51.5 million.

The core proposition is straightforward: feature flag management that you can self-host, inspect, and control. The open-source edition runs under Apache 2.0, giving engineering teams full access to the codebase and complete ownership of their flag evaluation data. The Enterprise edition layers on governance — change requests, RBAC, audit logging, SSO, and the recently launched Impact Metrics — for teams that need compliance controls without sacrificing deployment velocity.

For European organisations, the value case is structural. Unleash is an EEA company, subject to Norwegian and EU data protection law. The cloud-hosted version runs in EU data centres. The self-hosted version keeps everything inside your perimeter. No flag evaluation data crosses the Atlantic.

Key Features

Activation Strategies

Unleash's strategy system is where it diverges from simpler toggle libraries. Beyond basic on/off flags, you can define strategies based on gradual percentage rollout, specific user IDs, IP ranges, hostnames, or custom application context. Strategies stack, so you can combine a 10% rollout with a geographic constraint — roll out to 10% of users, but only in Germany. This composability is genuinely useful for teams managing releases across multiple regions.

Feature Lifecycle Management

Version 6 introduced a structured lifecycle for flags: Define, Develop, Production, Cleanup, and Archived. This sounds like process overhead until you have 2,000 stale flags cluttering your codebase. The lifecycle view surfaces flags that have been in production for months without a cleanup plan, which is exactly the kind of technical debt that accumulates silently on fast-moving teams.

Impact Metrics and Signals

The newest addition, shipped alongside the Series B announcement, is Impact Metrics. This lets teams define counters, gauges, and histograms — error rates, latency percentiles, adoption curves — and feed them directly into release templates. When metrics are healthy, rollouts progress automatically. When something spikes, Unleash pauses. Combined with Signals (ingesting telemetry from external systems) and Actions (triggering automatic rollout adjustments), this moves Unleash from passive flag management toward autonomous release governance.

Change Requests

For regulated environments, change requests add an approval layer to flag modifications. Every proposed change goes through review, gets timestamped and attributed, and creates an audit trail. This is Enterprise-only, and it is the feature that most clearly separates Unleash from its open-source self.

SDK Ecosystem

Unleash ships 15 official SDKs — Node.js, Java, Python, Go, .NET, Ruby, PHP, React, Vue, Angular, iOS, Android, Flutter, and more — plus over 15 community-maintained SDKs. Server-side SDKs evaluate flags locally after an initial sync, which means flag checks add microseconds of latency rather than a network round-trip. Unleash Edge extends this to the CDN layer for client-side applications that need low-latency evaluation at scale.

Pricing

Unleash runs on two tiers, with the former Pro plan now discontinued.

The Open Source edition is free under Apache 2.0. You get unlimited feature flags, but you host and maintain it yourself. Enterprise features — SSO, RBAC with project scoping, change requests, audit logs, SCIM provisioning — are not included. For a small team running a handful of flags, this is perfectly adequate.

Enterprise starts at $75 per seat per month with a 5-seat minimum ($375/month floor), available as either pay-as-you-go monthly billing or custom annual contracts. You get cloud-hosted or self-hosted deployment, unlimited projects and environments, and the full governance stack. Annual contracts come with dedicated support and SLAs.

The pricing model deserves honest scrutiny. At $75/seat/month, a 20-person engineering team pays $1,500/month — $18,000 annually. That is competitive against LaunchDarkly for teams with large user bases (where LaunchDarkly's MAU pricing escalates fast), but expensive for smaller teams that only need a few governance features on top of the open-source core. The gap between free and $375/month is wide, and the absence of the old Pro tier at $12/seat makes that gap harder to bridge.

EU Compliance & Privacy

Unleash's compliance story is strong and structurally grounded. As a Norwegian company (Bricks Software AS), it operates within the EEA and is directly subject to GDPR and the broader EU data protection framework. This is not a US company with an EU subsidiary — it is a Nordic company by origin and jurisdiction.

The platform has achieved SOC 2 Type II certification, audited by Prescient Assurance. Enterprise features align with ISO 27001 controls. Data in the cloud-hosted version is encrypted in transit and at rest, with per-customer isolation and unique encryption keys.

Crucially, Unleash's SDK architecture means no personally identifiable information needs to flow through the platform. Feature flags evaluate server-side against application context you define — user segments, percentages, custom properties — without requiring PII to leave your application boundary. For GDPR purposes, this is a meaningful design advantage: the feature flag platform never sees your users' personal data.

Self-hosted and air-gapped deployment options take this further. Organisations operating under FedRAMP, Schrems II constraints, or internal security policies that prohibit third-party data flows can run Unleash entirely within their own infrastructure.

Who It's Best For

Platform engineering teams building internal developer platforms who want feature flag management as a self-hosted service. The open-source core integrates cleanly into existing Kubernetes infrastructure, and the Enterprise tier adds the governance that platform teams need to offer feature flags as a managed capability.

Regulated enterprises in finance, healthcare, and government where audit trails, change approval workflows, and data sovereignty are non-negotiable. The combination of SOC 2 certification, self-hosting, and EEA jurisdiction covers most compliance requirements.

Teams replacing LaunchDarkly who have hit pricing ceilings on MAU-based billing or need to keep flag evaluation data within EU borders. Unleash's per-seat model is more predictable, and the self-hosted option eliminates third-party data concerns entirely.

Open-source-first organisations that want to start free, inspect the code, and upgrade to Enterprise only when governance requirements demand it. The Apache 2.0 licence provides genuine flexibility.

It is less suited to teams that need advanced experimentation and statistical analysis (where dedicated A/B testing platforms remain stronger), or small teams that find the jump from free to $375/month too steep.

The Verdict

Unleash occupies a distinctive position in the feature flag market: an open-source foundation with genuine enterprise ambition, built in Europe by a team that treats data sovereignty as a design principle rather than a marketing checkbox. The SDK architecture, which evaluates flags locally and never requires PII, is a technical decision with real compliance implications. The recent Impact Metrics launch signals a shift from passive flag management toward autonomous release governance — ambitious, and worth watching.

The trade-offs are real. The open-source tier is capable but governance-bare. Enterprise pricing is competitive at scale but presents a steep entry point for smaller teams. Experimentation features lag behind dedicated platforms. Polling-based flag propagation adds latency compared to streaming competitors.

For European engineering teams that need feature flag management with genuine data control, Unleash is the strongest open-source option available. The question is not whether it is good enough — it is — but whether your team's needs justify the Enterprise tier, or whether the open-source core does what you actually need.

Frequently Asked Questions

Is Unleash GDPR compliant?

Yes. Unleash is built by Bricks Software AS, headquartered in Oslo, Norway, and operates within the EEA legal framework. The cloud-hosted version runs in EU data centres, and the self-hosted option keeps all data within your infrastructure. The SDK architecture evaluates flags locally without requiring PII to flow through the platform.

Can I migrate from LaunchDarkly to Unleash?

Unleash does not offer an automated migration tool, but the flag model is conceptually similar. You will need to recreate flag definitions, strategies, and segments manually. The SDK switch involves replacing LaunchDarkly SDK calls with Unleash equivalents — the evaluation pattern is similar. Most teams report migration taking days rather than weeks for moderate flag counts.

What happens if the Unleash server goes down?

Server-side SDKs cache the last known flag configuration locally. If the Unleash API becomes unreachable, flags continue evaluating based on the cached state. This means a server outage does not break your application — flags simply stop updating until connectivity is restored.

Is the open-source version production-ready?

Yes, many organisations run the open-source edition in production. It supports unlimited flags, environments, and API tokens. The main limitations are the absence of enterprise governance features: no SSO, no change requests, no RBAC with project scoping, and no audit logs. If your team does not need those controls, the open-source edition is a viable production choice.

How does Unleash handle flag cleanup and technical debt?

Unleash's lifecycle management tracks flags through five stages — Define, Develop, Production, Cleanup, and Archived. The system surfaces flags that have been in production without a cleanup plan, helping teams identify and remove stale flags before they become entrenched technical debt. Enterprise customers also get metrics on flag age and usage patterns.