SDKs
Adopt Foredeck without betting the company on us.
Frontend, backend, and mobile SDKs that speak OpenFeature, so you can swap providers without rewriting your integration. Local evaluation on the hot path, automatic exposure emission, and first-class metrics, RUM, and tracing helpers in the same client.
FreeIncluded from the Free tier.
@foredeck/sdk-jsOpenFeatureOne integration. No lock-in.
What you get
Why Foredeck for sdks & openfeature.
OpenFeature-native
Standard provider interface means switching costs stay low — the same wedge as an open wire protocol.
Local evaluation
Flags evaluate in-process against a synced ruleset — no network call on the request path.
Automatic exposures
Every evaluation enqueues an exposure event, batched and flushed asynchronously — the mechanism behind flag = experiment.
One client, four signals
Flags, metrics, front-end RUM, and W3C tracing all ship from the same SDK.
How it works
Three steps, one pipeline.
Add the SDK and configure your publishable key.
Read flags locally; exposures flush in the background.
Turn on metrics, RUM, and tracing from the same client.
Better together
Works with the rest of the platform.
Feature Flags
FreeShip every change behind a flag — free and unlimited.
Explore Feature Flags →Product Analytics
FreeThe front-end story: page views, clicks, Web Vitals — joined to variations.
Explore Product Analytics →Tracing
FreeFollow one call across every service — spans stamped with the variation.
Explore Tracing →Agent Tools (MCP)
FreeManage Foredeck from Claude Code, Cursor, or your own agents.
Explore Agent Tools (MCP) →One object, one pipeline. The same rollout you ship is automatically measured, guarded, and — when it breaks — traceable, because every signal is joined to the flag and variation the unit was in.
Get in