Loading...
Move supported LaunchDarkly evaluations to the OpenFeature API while LaunchDarkly continues to serve values and manage flags. Select a workspace repository fleet, route exact exceptions, and leave every merge decision with your team.
Migration Autopilot is currently a limited, allowlisted pilot. This is code API adoption, not a provider migration. It does not copy flag configuration, replace the LaunchDarkly control plane, delete provider-side flags, or merge pull requests automatically.
Today
Application → LaunchDarkly SDK → LaunchDarkly
Evaluation calls are coupled directly to the vendor SDK throughout application code.
After adoption
Application → OpenFeature → LaunchDarkly provider → LaunchDarkly
Application code uses the standard evaluation API while LaunchDarkly remains the runtime backend and flag-management plane.
FlagShark turns a workspace fleet into an exact exception-routing queue and a reviewable rollout. Successful repositories continue; ambiguity, drift, failed checks, and unsupported cells stay visible as exceptions.
Select from connected GitHub installations or use a saved filter. FlagShark resolves an immutable cohort and explains every selected, excluded, inaccessible, or unmapped repository.
Large fleets are split across bounded assessment requests and independently tracked repository work. The complete fleet never rides in one request, and one repository failure does not erase completed siblings.
Matching blockers are grouped by evidence fingerprint and exact affected membership. Review the repository and work-item blast radius, then keep the work manual or exclude it; either route stops automated publication for that affected set. Protocol v1 does not accept typed blocker answers or credentials.
The safe default is a 5-repository pilot followed by waves of 20. Only repositories whose exact support cell advertises the requested stage can advance.
Publication boundary
Draft pull requests, human merge
Eligible changes are validated and opened as drafts. FlagShark does not merge them automatically or bypass branch protection.
Failure boundary
Pause the wave, preserve the evidence
A failing CI check pauses the next publication wave. Repository exceptions stay isolated; authentication, tenant, or provider-wide failures pause the fleet.
Pin repository commits, inventory direct SDK calls, and compare code evidence with the selected LaunchDarkly project. Unknown work stays unknown rather than becoming a zero.
Supported calls, contexts, dependencies, and provider setup become an immutable change plan. Ambiguous wrappers, dynamic keys, and unsupported runtime shapes remain explicit blockers.
The current exact Node JavaScript and TypeScript cell can publish a draft PR only after credential-free validation passes against the same immutable plan. Your team still owns review, CI, and merge.
After a human merge, FlagShark proves the merge commit is on the default branch and rescans the actual result. Static verification records residual, manual, or newly introduced source calls without claiming runtime proof.
Assessment, preview, draft PR, and verification are separate promises. The table is generated from the same versioned registry that gates the product, so a broad detection claim cannot silently enable source transformation.
Inventory and evidence only. No source edit is generated.
A deterministic change set can be reviewed. No PR is published.
Validated edits can be published as a draft for human review and CI.
The merged default branch is rescanned and its static result recorded.
Resolve the workspace cohort, see every exact support boundary, and approve the pilot only when the evidence is ready. Access is currently limited to allowlisted pilot workspaces.
Request pilot access →