Ship behind a flag, measure with stats, kill instantly — no redeploy.

Four primitives that share one SDK and one API key: gates for ramps, configs for typed values, killswitches for break-glass, experiments for A/B tests with automated p-values.

Getting started→Which primitive?

Production readyOn this page · 3 min readUpdated · May 10, 2026Works with · Server SDK · Browser SDK

Four primitives, one mental model

⌗

Gates — boolean flags→

Targeted rollouts: enable for country=US, ramp 5% → 100%. The default tool when you want to ship code without showing it to everyone.

~1ms evaluation·no per-request fetch

⚙

Configs — typed values→

String, number, boolean, JSON values you change without a redeploy. Use when the question is "what value?" not "on or off?".

JSON schema-validated·typed access

⏻

Killswitches — break-glass→

A flag with a single job: disable a system in an incident. Separate from gates so on-call doesn't have to think about rollout percentages at 3am.

1-click disable·auditable

◈

Experiments — A/B tests→

Universes, holdouts, multivariate variants. Automated p-values and 95% confidence intervals delivered to the dashboard each day.

p-values + 95% CIs·daily updates

Not sure which to use?

See the decision tree — one diagram that maps "I want to do X" to the right primitive.

How it works

Every primitive is read by your SDK with sub-millisecond latency — no round-trip on the hot path. Writes you make in the dashboard or CLI propagate worldwide in under a second.

Step 1Install & configure

npm install @shipeasy/sdk and one shipeasy() call.

Read →Step 2Ship your first gate

Five-minute walkthrough. Create, gate code, ramp.

Read →Step 3Run an experiment

Pick a metric, define a variant, watch the p-value.

Read →