FEATURES

Unified Control for the Modern Stack.

Every feature a platform team needs to manage flags across environments, clouds, and teams — without the bloat.

SECURITY BOUNDARY

Backend + Frontend Scoping

Every environment produces two config files: one for backend services with full targeting rules, one for frontend clients with sensitive data stripped. The security boundary is built into the architecture.

BackendFrontend

backend.yaml

scope: backend
version: 12
flags:
  new-checkout:
    enabled: true
    rollout: 25
    rules: # full targeting rules
      - attribute: plan
        operator: in
        values: [pro, enterprise]

frontend.json

{
  "scope": "frontend",
  "version": 12,
  "flags": {
    "new-checkout": {
      "enabled": true
      // no targeting rules exposed
    }
  }
}

person

Create a feature flag called "dark-mode" for frontend, disabled by default

smart_toy

I'll create that flag now using MCP.

create_flag({ key: "dark-mode", type: "boolean", scope: "frontend", default: false })

check_circle

Flag created and deployed

dark-mode pushed to 3 environments in 1.2s

AI-NATIVE WORKFLOW

MCP Workflow Integration

FlagDrop ships an MCP server. Your AI coding agent can create flags, set targeting rules, toggle environments, and push configs — all without leaving your editor.

ClaudeCursorWindsurfVS Code

MULTI-CLOUD

Multi-Cloud Per-Environment Sync

Production on GCP. Staging on AWS. Dev on Azure. Each environment has its own bucket, region, and credentials. FlagDrop pushes to all of them.

hub

FlagDrop

Control Plane

Active

Push

cloud

GCP Prod

gs://flags-prod

Synced

cloud

AWS Staging

s3://flags-staging

Synced

DASHBOARD

Everything at a glance

Flag states, environment sync status, rollout percentages, and targeting rules — all in one view.

flag

web-app

12 flags

check_circleAll synced

Flag Name

ProdStgDevRollout

new-checkoutboth

100%

dark-modefrontend

25%

ai-recommendationsbackend

payment-v2backend

50%