CheckOps home

Tools directory

O

CheckOps

OpenFeature

OpenFeature is an Apache-2.0 CNCF open specification and set of SDKs that provide a vendor-agnostic API for feature flagging, with providers for many flag platforms.

Visit website

Latest public signals

Not refreshed yet. Refresh reads the public site and, when the entry has a GitHub repository, the latest release.

Visit Website

Introduction

OpenFeature is an open specification that provides a vendor-agnostic, community-driven API for feature flagging. It is a CNCF project, and its SDKs let application code call one standard API while a provider connects to the actual flag system.

Providers exist for commercial and open-source platforms such as LaunchDarkly, Flagsmith, Unleash, Flipt, GrowthBook, ConfigCat and others, plus flagd, the project’s own lightweight flag daemon. Hooks add behaviour around evaluations, such as logging, telemetry or validation, and evaluation context carries user and request data. SDKs cover languages including Java, JavaScript, Go, .NET, Python, PHP, Ruby, Swift and Kotlin.

In the quality loop OpenFeature reduces lock-in and makes flag behaviour testable, for example with in-memory providers in unit tests.

The source code is at open-feature/spec on GitHub under the Apache-2.0 licence, with about 1,300 stars; the most recent commit was on 5 November 2026.

Features

  1. Standard API: One flag API across vendors.
  2. Providers: Adapters for many flag platforms.
  3. flagd: Open-source flag daemon.
  4. Hooks: Telemetry, logging and validation.
  5. Evaluation context: Standard user and request data.
  6. Multi-language SDKs: Server, web and mobile.

Pros

  1. Avoids lock-in: Switch vendors without rewriting checks.
  2. Free to use: Open source under the Apache-2.0 licence, so the core tool costs nothing to use.
  3. Actively maintained: The repository had commits as recent as 5 November 2026.

Cons

  1. Abstraction limits: Vendor-specific features may not be exposed.
  2. Provider quality varies: Maturity differs by provider.
  3. Spec, not a service: You still need a flag backend.
import { OpenFeature } from "@openfeature/server-sdk";
import { FlagdProvider } from "@openfeature/flagd-provider";
await OpenFeature.setProviderAndWait(new FlagdProvider());
const client = OpenFeature.getClient();
const on = await client.getBooleanValue("new-checkout", false, { targetingKey: "user-42" });

Resources:

Pricing

OpenFeature is free and open source under the Apache-2.0 licence.

  1. Platform teams standardising flag usage.
  2. Organisations that may change flag vendors.

Conclusion

OpenFeature is the neutral layer feature flagging needed.

Adopt it early to keep application code portable.

On CheckOps, OpenFeature is filed under the Release & CI gates stage. Related tools listed here include LaunchDarkly, Unleash, Flagsmith, GrowthBook, Flipt and Statsig. Which one fits best depends mostly on your stack, your team’s size and skills, and whether you prefer to run tools yourself or pay for a managed service. This page reflects the official website, documentation and repository as they stood on 11 November 2026.

Alternatives

Other tools on CheckOps that cover similar ground. Open a page, or compare one with OpenFeature side by side.