AI
OpenFeature: Vendor-Neutral Feature Flagging as a CNCF Standard
OpenFeature is an incubating CNCF project that defines an open specification for feature flagging. The model mirrors OpenTelemetry: one standardized SDK API in your code, swappable provider plugins underneath. The SDK call never changes regardless of which flag management system sits behind it. Providers exist for file-based configs, homegrown solutions, and commercial vendors. This separation means switching vendors requires no application code changes, only a different provider wired at startup.
SDK Releases and Growing Adoption
React and Angular SDKs reached 1.0 this year. Kotlin and Swift work is in progress. A C++ SDK started recently and is not fully spec-complete but already usable. Adoption data shows a large gap in JS SDK downloads compared to the prior year, with growth visible across all SDKs where download data is collected. New contributors include Datadog, Google, and Spotify. Several companies now build OpenFeature-first SDKs rather than custom integrations. OpenFeature also appeared on the ThoughtWorks Technology Radar this year.
OFREP: Two APIs Instead of One Provider Per Vendor
OFREP (Open Feature Remote Evaluation Protocol) reduces the per-vendor provider build problem to two HTTP APIs: one for single flag evaluation on the server side, one bulk evaluation API for clients. Any vendor or homegrown system that implements those two endpoints gets community-maintained providers for free across Go, Java, Python, and all JS environments. flagd, DevCycle, GO Feature Flag, and Flipt already ship OFREP. Version 1.0 is close. The next planned addition is server-sent events so clients get notified when flag configurations change.
MCP Server for AI-Assisted Flag Development
André Silva presented an OpenFeature MCP server, now listed on the MCP registry and in active development. It gives AI agents two capabilities: pulling best-practice documentation (SDK installation, evaluation context population) and querying live flags via the OFREP protocol. A developer can ask Claude to scaffold a Go SDK integration from scratch and receive generated code built from current docs. Another scenario: pasting a 10,000-flag config and asking Claude to explain how a specific flag resolves for a given context. Write operations are not yet supported; the team is gathering vendor consensus first.
GitHub Action and CLI for Flag-Driven Pull Requests
Alexandra Oberaigner presented the OpenFeature GitHub Action, built on top of the OpenFeature CLI. Three CLI commands power it: pull fetches flag configs from a remote management system, compare diffs two manifests, and generate outputs typed flag variables. In a PR workflow this means additions, removals, and modifications to flag configs appear automatically in the review. It also detects drift between a local repository copy and the live remote system. Typed variable generation removes the risk of a misspelled flag key string reaching production.
Isolated API Instances and the LFX Course
Lukas Reining described a design problem surfaced by a micro-frontend user: when one micro-frontend shut down, it closed the singleton and broke flag evaluation for the others still running. The proposed solution is isolated OpenFeature API instances, available from a separate import path so teams opt in deliberately. The singleton remains the default. Separately, an OpenFeature introductory course on the LFX Education platform has reached 500 enrollments. It is free, runs about 10 hours, and includes hands-on labs, quizzes, and a discussion forum.
Q&A
How should teams handle performance when evaluating more than 1,000 active flags? Flag sets let teams scope down to only the flags a specific service or team needs, avoiding loading the full catalog on every evaluation. ▶ 26:09
Will the MCP server support write operations like creating or updating flags? Only read operations are available now; write support requires community and vendor consensus, and a separate CLAG SIG effort is exploring vendor-neutral flag creation APIs. ▶ 27:49
Notable Quotes
oh Jesus, this flag scheme has 10k flags. So how does it resolve? Please help me claude. André Silva · ▶ 12:25
like the first microrend to go shut down open feature and it was gone. So the connection was closed. It it was it was ended. It didn’t work. Lukas Reining · ▶ 18:04
switching vendors means like switch just putting a different URL in your configuration and you switch from one vendors to another. Thomas Poignant · ▶ 09:18
we actually have 500 enrollments until now. So 500 people did that and yeah got their first hands on feature flagging Lukas Reining · ▶ 23:44
Key Takeaways
- React and Angular SDKs hit 1.0; C++ SDK is new and already usable.
- OFREP lets any backend become an OpenFeature provider by implementing two HTTP endpoints.
- The GitHub Action diffs flag configs in PRs and generates typed variables automatically.
- An MCP server connects AI agents to live flag state via OFREP, read-only for now.
- Isolated API instances solve the micro-frontend and parallel-test singleton problems without removing the default singleton.
About the Speaker(s)
André Silva is a developer from Portugal based in Ireland, specializing in .NET applications and open standards. He is a maintainer of OpenFeature at LexisNexis Risk Solutions, contributing to the project library and telemetry conventions.
Lukas Reining is a software developer and IT consultant at codecentric AG. His focus is software architecture and cloud native applications. He serves on the OpenFeature Technical Committee.
Thomas Poignant works at Gens de Confiance and sits on the OpenFeature Governance Committee. He is the creator and maintainer of GO Feature Flag, a self-hosted open source feature flag management system.
Alexandra Oberaigner joined Dynatrace as a security researcher and transitioned to the Feature Flagging team, where she leads OpenFeature adoption company-wide. She is an active OpenFeature contributor and agile practices advocate.