── FEATURE SWITCHES ──
Feature switches without the faff. Merge your code when it's ready, then decide who actually sees it; one environment, one user, or a few percent at a time.
Every switch has its own value in stage, prod, and whatever else you run. So yes, you can test on stage without crossing your fingers about prod.
Switch things on for particular users, companies, or plans; anything your app sends. Rules run top to bottom, and the first match wins. Pretty simple.
Start at 5%, nudge it to 25%, then everyone. Rollouts are sticky too, so the same person gets the same answer every time (no flip-flopping between old and new).
Servers check switches in-process, with no network call per check. Browsers only ever get their own answers; your rules (and any user ids in them) never reach the page.
The rule editor learns which attributes your apps send, and suggests them as you type. Got something personal in there? Turn the suggestions off for it.
If we have a bad day, your app shouldn't. The SDKs never throw on network problems, and keep serving the last switches they loaded.
HOW IT WORKS
Stage, prod, the lot. Every switch lives in each one, with its own value.
Give it a key, then decide who gets it in each environment; everyone, a handful of users, or a percentage.
Create an API key, install the SDK, and you're away. Servers pick up changes within 30 seconds; no redeploy needed.
NODE.JS
import { createServerClient,} from "@dev-team-tool/feature-switches-node";const switches = await createServerClient({ apiKey: process.env.FEATURE_SWITCHES_KEY,});if (switches.isEnabled("newCheckout", { userId: user.id, companyId: user.companyId,})) { // ship it}SDKS
Your first switch takes a couple of minutes to set up. Flipping it takes one click.
Part of Dev Team Tools — one workspace for your whole team.