Skip to content

Everything a rollout needs

Product

  • Gates

    A gate is on or off for each person. The kill switch turns it off at once, rollouts go by percent with stable SHA-256 bucketing, every version is kept, and Restore brings an old one back.

  • Configs

    Serve a number, text or JSON instead of on or off. Each config has a type, and JSON values are checked against a shape you set.

  • Parameters

    Code reads a name like checkout.buttonColor. The console maps that name to a constant, a gate, a config or an experiment in each environment.

  • Experiments

    Split people into groups and read the lift, its confidence interval, the p-value and a sample ratio check. The page says how many people are still needed, then offers Ship, Don't ship or Keep running.

  • Segments

    Group people into a list or a rule, like plan in pro. Give a gate to a segment, not to a list of names.

  • Environments

    Each environment has its own rules and keys. Mark an environment protected to require a reason for every change.

  • Events

    Exposure is recorded automatically. Count the events your apps send and use them as goals in experiments.

And the rest

  • Channels

    One gate serves web, Mac and iOS. Make it visible to some channels, or give one its own rule.

  • Check a person

    Type an id and see the exact rule that decided the answer.

  • Rules stay on the server

    The app gets only the values it asked for. Rules, other people and segment lists never leave the server.

  • Members and teams

    Readers look, writers change content, owners manage keys and access.

  • Audit log

    Every change is recorded with its reason and the before and after values.

  • SDKs

    TypeScript and Swift. Read a gate, config or parameter with a default. The SDKs never throw and answer from their cache when offline.

Request access

Open a ticket and your workspace owner adds you.

Request access