Skip to content
The Bridge Logo The Bridge docs

Feature Flags

Bridge Feature Flags is a standalone product. Feature flags work with an app ID and a single flag call — Bridge auth, billing, and user management are optional add-ons, not prerequisites. Start here for the standalone feature-flag path.

const showBanner = useFlag('show_banner', false); // that's the whole integration

Every flag evaluation is a local, in-memory lookup — no network call, safe to use in render paths and hot server loops. When you change a flag in the admin UI, every connected app reflects it within about a second, live, with no refresh or polling.

What you need

Section titled “What you need”
  • A Bridge app ID, create one at app.thebridge.dev
  • One of the Bridge SDKs (Svelte and NestJS shown throughout; more frameworks below)

What you don’t need

Section titled “What you don’t need”
  • Bridge auth — flags work for anonymous visitors out of the box. If you later adopt Bridge auth, attributes like user.role and tenant.id start flowing into your flag rules automatically.
  • Bridge billing — you can target on your own plan attribute today. If you later adopt Bridge payments, bridge:billing.* attributes (plan, quotas, entitlements) merge in automatically.

Both upgrades are incremental and non-breaking — see Upgrade to the full platform.

The reading path

Section titled “The reading path”
  1. Quickstart — install, init with an app ID, first flag, live updates.
  2. Targeting & attributes — the evaluation context, custom attributes, and the rule builder.
  3. Observability — eval telemetry, call-site reporting, and verifying your integration.
  4. Common patterns — marketing sites, A/B tests, percentage rollouts, kill switches.
  5. Upgrade to the full platform — what changes when you add Bridge auth or billing.

See also

Section titled “See also”