One product, three primitives. Pick the right one for the change you're shipping.

Shipeasy · Flags & Configs

Ship behind a flag, change values live, kill instantly — no redeploy.

Three primitives that share one SDK and one API key: feature flags for targeted ramps, configs for typed values you change without a deploy, killswitches for break-glass.

Getting started→Which primitive?

Production readyOn this page · 3 min readWorks with · Server SDK · Browser SDK

Three primitives, one mental model

⌗

Feature flags — 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 feature flags so on-call doesn't have to think about rollout percentages at 3am.

1-click disable·auditable

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 configure() call.

Read →Step 2Ship your first feature flag

Five-minute walkthrough. Create, put a feature flag around your code, ramp.

Read →Step 3Measure what it did

Turn your own events into a metric and watch it while the ramp climbs.

Read →

Was this page helpful?

Updated August 9, 2026✎ Edit this page