Unleash is the open-source incumbent, and for a large class of teams it is the right answer: you can self-host it in your own VPC or fully air-gapped, keep flag data on your infrastructure, and get custom roles, SSO/SAML, SCIM and approval workflows, none of which wagle has. Do not pick wagle if you need self-hosting or data residency, broad or mobile SDK coverage, enterprise SSO/SCIM, or a funded company with a support SLA: pick Unleash, full stop. Consider wagle if you are a Go/TypeScript shop that wants nothing to operate, a browser SDK that evaluates locally instead of calling a proxy tier, one per-sync pricing meter instead of $75 per seat, and a small independent vendor with no VC clock, accepting, in exchange, a young closed-source product run by one person. One honest asymmetry to weigh: Unleash's free path is real but narrowing (the server relicensed to AGPL, and OSS Edge is dead end-of-2026); wagle's isn't open at all.
Competitor claims re-verified 2026-07-19 · sources at the bottom
None, by design. wagle is hosted-only: there is no self-host build and no way to keep flag data on your own infrastructure. If self-hosting or data residency is a hard requirement, wagle is the wrong tool and Unleash is the right one.
Genuinely self-hostable: a single container plus Postgres, runnable in your own VPC or fully air-gapped, so flag data never leaves your infrastructure. This is Unleash's real, structural advantage.
Closed source: "not yet" rather than "never", but there is no public repository today and nothing to read or fork. On openness, Unleash simply wins.
Actually open source (permissive SDKs), so you can read and modify it. The asterisk, stated honestly: the server relicensed Apache-2.0 → AGPL-3.0 at v8 (June 2026), and OSS Unleash Edge reaches end-of-life 2026-12-31; the free path is real but narrowing.
Three fixed per-project roles (admin / editor / viewer) on every account. No SSO/SAML/SCIM and no custom roles: if your org lives in Okta or needs SCIM provisioning, that gap is real today.
Custom and project roles, user groups, SSO/SAML, SCIM and approval workflows, deeper than wagle, though all of it is Enterprise-gated and absent from the open-source edition.
Two languages: Go and TypeScript/React. No Python, Java, .NET, Ruby, and no mobile. If your stack needs those, stop reading and use Unleash.
25+ official SDKs across backend, frontend and mobile.
The browser SDK receives rules and evaluates locally, byte-identical with the Go SDK and the server, pinned by shared CI vectors. No proxy tier to run, and switching user context needs no round-trip.
Backend SDKs evaluate locally too, a genuine tie there. But frontend/client-side SDKs do not: they fetch pre-evaluated flags from the Unleash Frontend API, Edge or Proxy, so a browser or mobile client depends on that tier being reachable, an extra hop and point of failure, and in OSS the client updates by polling (real-time streaming is Enterprise-only).
Multitenancy and environments are day-one and unmetered: every flag is (project, environment)-keyed, with the environment folded into the bucketing hash so each one rolls out independently.
The open-source edition is capped at 1 project and 2 environments; unlimited environments require the Enterprise tier.
One meter: SDK syncs (the config pull, the only call that reaches the service). Seats and viewers are not the unit, and local evaluations are free and unlimited because they never touch wagle.
$75 per seat / month on Cloud, with a 5-seat minimum on self-hosted Enterprise and no viewer-only seat, so read-only stakeholders cost a full seat (a G2 reviewer notes costs scale quickly). The free path is self-hosting the capped OSS edition: $0 in licence, but you operate it.
Solo-owned, no investors, break-even ambition, so no VC clock and no incentive to move value behind paywalls or sell out. Said in the same breath: bus factor of one. The mitigation is architectural: SDKs keep serving their last local snapshot if wagle is unreachable, stale rather than broken.
A funded company (a $35M Series B in 2026, $51.5M total) with real support and staff, but with the growth expectations that come with it. The AGPL relicense and the OSS Edge end-of-life are that open-core model tightening its free surface over time.
Every write, on every account: actor-attributed, versioned, with readable per-version diffs.
Audit logs exist (up to two-year retention), but approval workflows and change requests are Enterprise-only and absent from the open-source edition.
Third-party sources only: reviews, buyer data, and their own published docs and pricing; never their marketing copy, never our opinion of them.
The why & how page states every deliberate limitation plainly, the fastest way to rule wagle in or out.