FTF at a glance
Feature toggles managed across your whole delivery — releases across applications, promotion to production, the same screens on a developer's laptop — on its own or in front of LaunchDarkly or ConfigCat.
For the CIO, in one minute
- No extra work for developers, BAs and testers. Toggles live in a file in the developer's own repo, edited with FTF's screens and promoted to FTF — or pulled from it — like git push and pull, with clashes caught before anything is overwritten. About 20 hours of toggle work per release, where the others take 33–37 (how we count).
- Keep what you have — and keep your options. FTF works on its own, or in front of the LaunchDarkly or ConfigCat account you already pay for, both included. Your applications only ever talk to FTF, so you can move between them — or to FTF alone — without changing a single system. Another provider can be added on request.
- Releases, not just flags. One switch takes a release live across every application — policy, billing, claims, digital — while each feature keeps its own kill switch.
- Integrates anywhere, on the open standard. FTF speaks OpenFeature's remote-evaluation protocol (OFREP), so any language uses OpenFeature's own SDKs — or one plain HTTP call. No FTF client to install, nothing vendor-specific to upgrade in every service.
- Governance built in. Your identity provider decides who switches what, in which environment. Every switch is recorded, and every toggle is tracked until it's removed everywhere.
- Designed for insurance. Brands, jurisdictions, claim amounts and policy shares as toggle attributes; long test cycles and core systems that can't roll back data, as design inputs.
More about FTF
BYO provider
Your vendor, or none
FTF on its own, or in front of the LaunchDarkly or ConfigCat account you already have.
BYO provider →FTF-101
How it works
Toggles, releases, business scenarios, promotion, local development and a toggle's life.
FTF-101 →Open standards
Any language
OpenFeature's own SDKs through its remote-evaluation protocol — no FTF library to adopt.
Open standards →Security & access
Your identity provider decides
No users kept in FTF; permissions scoped to environments and applications.
Security & access →How FTF compares
What FTF adds to LaunchDarkly and ConfigCat, side by side, and the effort per release.