Everything you ship, behind one SDK.
Feature flags, typed runtime configs, kill switches, metrics & threshold alerts, and bug + error capture — one SDK, one API key. Drive it by hand, by CLI, or by an AI agent.
Start here
Install, wire one configure() call, ship a flag — from zero to live in five minutes.
Fast local reads, explicit edge writes, sub-second propagation. The mental model behind every product.
Read →ReferenceBrowse the SDKsOne package for server + browser, plus native ports for Go, Python, Ruby, Java, Kotlin, PHP and Swift.
Read →Explore by product
Flags & Configs→
Feature flags for ramps, typed configs for values you change without a deploy, and killswitches for break-glass.
Metrics & Alerts→
Turn events into metrics with a small DSL, watch them move as you ramp, and raise threshold alerts that file their own tickets.
Bugs & Requests→
User-reported bugs, feature requests, and handled errors — captured in-app and routed into your tooling.
SDKs→
One package, server + browser builds, plus native ports for Go, Python, Ruby, Java, Kotlin, PHP and Swift.
Assistant→
Ask questions about your project, and let the assistant draft flags, configs, and measurement plans as editable cards.
Get started→
Install the SDK, authenticate, learn the core concepts, and hand setup to a coding agent.
Or start from a goal
Most teams arrive with an outcome in mind. Each path is an ordered set of pages that takes you from install to shipped.
Ship a feature behind a flag
Put new code behind a switch, target who sees it, and ramp from 0% to 100% with no redeploy.
Know whether the ramp is safe
Turn your own events into a metric, watch it while the flag ramps, and get paged when it moves the wrong way.
Catch bugs & errors in production
Capture user-reported bugs and handled exceptions, route them to your tools, alert on regressions.
Let an AI agent run it all
Hand setup, flags, configs, and metrics to a coding assistant via the CLI and MCP server.
Not sure which primitive?
Inside Flags & Configs there are three primitives. This picker maps "I want to do X" to the right one.
Full breakdown → decision guide.
Why Shipeasy
- One SDK for feature flags, configs, kill switches, metrics, and feedback. Server and client.
- One CLI (
shipeasy) for everything you can do in the dashboard. - One MCP server so your AI agent can do the boring setup for you.
- Sub-millisecond evaluation: flags resolve in your code without a network round-trip.
- Export your data: your events and metric series are yours, not locked into our dashboard.
Stop reading. Start shipping.
The fastest way to feel Shipeasy is to install it on a real repo. Start free, the CLI does the boring parts, and your AI agent can do the rest.