Launching October 13, 2026
dif.sh

dif.sh

Feature flags and A/B tests as Markdown files in your repo.

FreeCLIDevOpsCode0 impressionslaunches Oct 131 comment

Comments

>log in to comment
  • Chris Fowles[maker]· 1d ago

    We built dif.sh so feature flags and A/B tests can live right in the repo as simple Markdown files, versioned with git and reviewed in PRs. It’s a single‑command install, no signup, and the CLI generates the context for your code and CI builds. Let us know what you think 😊

dif keeps each feature flag and A/B test as one Markdown file in your git repo, reviewed in pull requests like any other code. dif validate checks every file in CI: weights sum to 100, the surface exists, and two experiments on one surface cannot collide. dif build compiles the active files into a typed TypeScript client. The zero-dependency SDK picks a variant by hashing the user ID, so there is no flag server and no request to evaluate a flag. MIT licensed, no signup. Dif Cloud is optional.
  • Store feature flags as Markdown files in the repo
  • Versioned in git and reviewable via pull requests
  • Coding agents read dif/context.json on session start
  • One‑command install, no signup required
  • Supports A/B tests with results written back to files

dif.sh stores feature flags and A/B tests as Markdown files in your git repo, generating a typed TypeScript client.

for
Developers who want version-controlled, code-reviewable feature flags without a separate flag service.
pricing
freemium
license
MIT
dif-sh/dif 27 0Rustupdated a day ago
works withTypeScript

Key features

6 features of dif.sh
  • Markdown-based flags — Define each flag or experiment in a single .md file stored in the repo.
  • CI validation — CLI validates files in CI for weight sums, surface existence, and collision checks.
  • Typed client generation — dif build compiles active files into a zero-dependency TypeScript SDK.
  • No server calls — SDK picks variants by hashing user ID, eliminating runtime flag server requests.
  • Conflict detection — Build fails if two live tests would collide on the same user.
  • Optional cloud metrics — Dif Cloud provides live pulse, team metrics and PR write-back for a per-event fee.

Use cases

  • Version-controlled rollout of a new UI copy with 50/50 split.
  • Running holdout or staged rollout experiments directly from PRs.
  • Ensuring no two experiments affect the same user via exclusion groups.
  • Archiving concluded tests and preserving learnings in surface logs.

dif.sh vs alternatives

dif.shGitHub ActionsCircleCIVercelRender
Best forGit-backed feature flags and experimentsCI/CD pipelinesCI/CD pipelinesFrontend hostingContainer runtime
PricingFreemiumSubscriptionSubscriptionSubscriptionSubscription
DevHunt upvotes10000
LaunchedOct 2026————

dif.sh FAQ

Do I need Dif Cloud to run experiments?+

No. The CLI and SDK are free and open source; Cloud is optional for live metrics and team view.

What counts as an event?+

Each SDK exposure and each dif.track() call count as one event; deduped retries are not billed.

What happens if I exceed my event quota?+

Events above the included 1M are billed $0.02 per 1,000 and a spend cap stops further ingestion.

Are seats charged separately?+

No. Both Pro and Enterprise plans include unlimited seats.

Can I reduce my bill?+

Yes, by setting a per-project sample rate to lower event volume.

Summarized by DevHunt from dif.sh · Oct 9, 2026. Details may change; check the official site.