v4.2Scheduled rollouts and automatic rollbackRead the release

Ship every change. Lower any of them.

Feature flags, guarded rollouts and kill switches that reach every edge node in 38 ms. Built for teams that deploy every day and sleep every night.

production · web3 flags · live
  • new-checkout-flow

    One-page checkout with saved cards

  • edge-cache-v2

    Stale-while-revalidate at the edge

  • search-reranker

    Semantic reranking for site search

  1. evalnew-checkout-flow → false0.22 ms
  2. evaledge-cache-v2 → true0.41 ms
  3. evalsearch-reranker → false0.20 ms
38 ms
Kill switch, p99
From the click to the last edge node
2.1T
Evaluations a month
Across every customer and SDK
312
Edge nodes
In 41 regions, on three clouds
0
Redeploys to roll back
Rollback is a toggle, not a pipeline
  • Evaluated where your users are

    Rulesets stream to 312 edge nodes. Your code never waits on a network call to ask whether a flag is on.

  • Yours, not ours

    User attributes never leave your servers. Driftwire sees flag keys and counts — nothing that identifies a person.

  • Experiments without a data team

    Any flag can be an experiment. Results arrive with the confidence interval already worked out.

  • Open by default

    An OpenFeature provider for every SDK, so the flag calls in your code are not a lock-in.

Platform

Release is a dial, not a switch.

Every change ships dark, rolls out by percentage and stops itself when a guardrail trips. The deploy and the release are finally two different things.

  • Kill switches

    Turn anything off, everywhere, before the alert finishes paging.

  • Guarded rollouts

    1% to 100% on a schedule, paused automatically when error rates move.

  • Targeting

    Segments, rules and per-user overrides, evaluated locally in every SDK.

  • Audit everything

    Who changed which flag, when, and what it was before. Exportable.

Teams that stopped dreading Fridays.

Two of the teams who moved their releases behind Driftwire, and what changed.

  • 4 sto roll back, from 40 min

    “Rollback used to be a 40-minute pipeline. Now it is a toggle, and on-call is boring again — which is the highest praise I have.”
    Dana OkaforVP Engineering, LumenfoldRead the case study
  • 2,000flags migrated in a weekend

    “We moved 2,000 homegrown flags in a weekend and deleted 312 of them the next month. Nobody noticed, which was the point.”
    Theo LindqvistStaff Engineer, ParcelwickRead the case study

Developers

Wrap the change once. Steer it from here.

Install the SDK, wrap the change, and every decision after that is a click — not a deploy. Typed clients for the languages you already ship.

  • Local evaluation

    Rules live in memory in every SDK. A flag check is a function call, not a request.

  • Streaming updates

    Changes arrive over a long-lived connection, so a kill switch lands in milliseconds.

  • Safe defaults

    If Driftwire is unreachable, your code serves the defaults you set. Nothing breaks.

import { createClient } from '@driftwire-demo/sdk'

const driftwire = createClient({ sdkKey: process.env.DRIFTWIRE_SDK_KEY! })

export async function checkoutFor(user: User) {
    const useV2 = await driftwire.isEnabled('new-checkout-flow', {
        key: user.id,
        plan: user.plan,
    })
    return useV2 ? renderCheckoutV2(user) : renderCheckout(user)
}

Integrations

Plugs into the stack you already run.

Flag changes post to your team chat, link to the pull request that shipped them, and show up in your traces. SDKs for every runtime you deploy.

  • Source control
  • Team chat
  • CI pipelines
  • Error tracking
  • Tracing
  • Incident paging

What the people on call say

“Guardrails turned rollouts from a meeting into a schedule. Releases advance overnight and stop themselves if something looks off.”
Inès Moreau
Inès Moreau
Head of Platform, Orbwright
“We ship forty times a day with a team of nine. Driftwire is the reason that number does not scare our board.”
Kwame Mensah
Kwame Mensah
CTO, Kitebird
“The audit log settled an argument in our incident review in about eight seconds. That alone paid for it.”
Hana Kobayashi
Hana Kobayashi
Engineering Manager, Lanternquay

From the engineering blog

Engineering

Percentage rollouts are a hashing problem

A 25% rollout is not "one request in four". It is a stable answer to "is this user in?", identical on every server, that never flips a user back out. That is a hashing problem.

Avery LinAvery Lin

Make your next deploy the boring kind.

Free for five seats and 10,000 monthly users. Your first flag is about ten minutes away, with nothing to pay and nobody to talk to.