// about flagdrop

Built for engineers
who ship.

FlagDrop is feature flag infrastructure that runs where your code runs — in your cloud, under your control.

~/about/mission

Feature flags should be infrastructure, not a service dependency.

Every flag evaluation in your production environment should resolve from a config file in your own cloud bucket — not from a third-party API that sits between your users and your code. FlagDrop is the control plane that generates and pushes those configs. Your SDKs read locally. Zero runtime dependency on us.

~/about/origin

Born from frustration.

We were platform engineers running feature flags at scale. The bill from LaunchDarkly grew every quarter — not because we used more features, but because we hired more people and shipped to more users.

Per-seat pricing punished growth. Per-MAU pricing punished success. And every flag evaluation depended on an external API we didn't control.

We built FlagDrop to fix this: a control plane that pushes static configs to your own cloud storage. Your SDKs read locally. Evaluations are instant, free, and entirely under your control. Pricing is flat, per-project, and predictable.

4 reasons / 0 asterisks

What makes us different.

D.01

Data Sovereignty

Flag evaluations run in your cloud. Your data never touches our servers.

D.02

Fixed Pricing

Per-project pricing. No per-seat, per-MAU, or per-event surprises.

D.03

AI-Native

MCP server built in. Your AI coding agent manages flags without leaving the editor.

D.04

Open Architecture

Config push to standard cloud storage. No proprietary SDKs phoning home.

// join us

Want to build
the future of flags?

We're a small team of infrastructure engineers building the feature flag platform we always wanted. We're hiring across engineering, developer experience, and go-to-market.