Flag keys, types, and defaults ship in the same pull request as the code they gate.
Hypertune alternative
Hypertune shut down. Flags can still live in git.
Move flag keys into shipd.config.ts. Evaluate locally from a signed snapshot.
Hypertune generated a typed client from UI-authored logic. The hosted service is gone.
The Hypertune hosted service stopped accepting new signups and shut down on 10 August 2026.
Git source of truth
0 extra hops
PR environment plan
$0 to start
Where the products differ
Hypertune was the closest substitute: type-safe flags, Git history, local SDK evaluation. Targeting still lived in their UI. shipd puts flag keys in your repository. Targeting rules in code is still on the roadmap.
| Topic | shipd | Hypertune |
|---|---|---|
| Status | Hosted product with a free tier. | Hosted service shut down 10 August 2026. No new signups. |
| Flag keys | Defined in shipd.config.ts and reviewed in git. | Schema and flags were managed in Hypertune, then a typed client was generated. |
| Targeting | Dashboard today. Targeting rules in code is on the roadmap. | Rules were authored in Hypertune (Hyperlang in the UI), not in your app repo. |
| Evaluation | SDK loads a signed snapshot and resolves in-process. Postgres is not on the request path. | SDKs evaluated locally from Hypertune Edge or a build-time snapshot. |
| Git | Definitions live in your repo and review in your pull requests. | Hypertune kept its own Git-style history of flag logic. |
| Pricing | Free tier, then seat-based Pro from $15 per member / month. | No longer sold. |
Choose shipd when
- You used Hypertune for type-safe flags and local evaluation, and need a new home.
- Flag keys should live in the application repo, not a generated SDK from a dead control plane.
- You want CI to show an environment plan before a definition ships.
- You can live with targeting in a dashboard until targeting-in-code ships.
This is not a drop-in
- There is no Hypertune SDK compatibility layer.
- Hyperlang rules will not import. You redefine flags in shipd.config.ts.
- shipd is not an app-configuration platform for marketing content and AI prompts.
Be precise
What shipd does not claim
Targeting still lives in the dashboard
Flag keys are config as code today. Targeting rules in the repository are coming. Until then, rollouts and audiences are edited in shipd, not in git. Evaluation is still local: see local evaluation.
Not an experimentation suite
shipd evaluates variants. It is not a stats engine, and it is not trying to replace LaunchDarkly experiments, Statsig pulse, or PostHog analytics.
Closest substitute, not a clone
Hypertune generated a type-safe client from UI logic. shipd treats the TypeScript definition as the source of truth. Local evaluation is the shared idea. The authoring model is not.
Questions
- Is shipd a Hypertune alternative?
- Yes for type-safe flag keys and local evaluation. It is not a generated Hypertune client, and targeting is still dashboard-authored today.
- When did Hypertune shut down?
- Hypertune stopped new signups and shut down its hosted service on 10 August 2026.
- Can I migrate Hypertune flags automatically?
- No importer ships today. Recreate flag keys in shipd.config.ts and move targeting into the shipd dashboard.
- Does shipd evaluate flags locally?
- Yes. The SDK downloads a snapshot and checks flags in memory. Your app does not call shipd on every request.
Define once. Evaluate everywhere.