Skip to main content
Fireweave v1 does not ship an OpenFeature provider. ADR-0010 (accepted 2026-08-20) retired FireweaveProvider and FireweaveWebProvider from every language SDK. There is no makeFireweaveLocalProvider, and no OpenFeature extra or peer dependency in the core packages.
If you arrived here looking for a drop-in OpenFeature provider, that path is gone from the core SDK. Use the native controlPoints surface, and follow Migrate 2.1 to 2.3.

Why the provider was unbundled

ADR-0010’s rationale, not a restatement of it:
  • The provider was a thin delegation layer, not a second evaluation path. getBooleanValue and resolveBooleanEvaluation both called the same runtime.
  • The OpenFeature peer dependency was mandatory by accident. A consumer who only called controlPoints.* was still told to install an OpenFeature SDK they never imported.
  • The surface is seven languages. Requiring a mature OpenFeature SDK in each language made Rust and Swift depend on another project’s coverage.
OpenFeature compatibility is unbundled, not forbidden. Nothing in ADR-0010 prevents a future optional bridge package that depends on both this SDK and an OpenFeature SDK. What is retired is the bridge shipping inside the core, where every consumer pays for it.

What you call instead

v1 exposes exactly two capabilities: control-point reads and target registration.
The nine methods (getBooleanValue, getStringValue, getNumberValue, getObjectValue, the four *Details variants, and evaluate) live on controlPoints / control_points / ControlPoints in every language. See Control points. flagKey is still the parameter name on the wire, on Decision envelopes, and in conformance fixtures. Removing the OpenFeature dependency did not rename flagKey. The product noun in prose is control point.

What was removed

A search for those symbols in a v1 install should find nothing. conformance/surface/control-points.surface.json asserts mustNotExpose for FireweaveProvider and FireweaveWebProvider.

Next

Migrate 2.1 to 2.3

Before and after call sites for the provider removal and the package rename

Control points

The nine-method native surface
Last modified on September 11, 2026