Compare

hotcfg vs LaunchDarkly

hotcfg is remote config and kill switches with guardrails, at a flat price that doesn't grow with your users. How it compares with LaunchDarkly.

If you're here because…

  • The bill grows with your users. LaunchDarkly's paid plans are priced by usage, including client-side monthly active users.
  • It's more platform than you need for kill switches and a settings file.
  • Your config isn't only flags: limits, prices, copy, lists, a whole settings document.
  • You need to read it without an SDK: from a game engine, a script, a device or a language with no official SDK.

…hotcfg is built for exactly that, and nothing more.

Why hotcfg

A flat price

Pro is $19 a month per organization, with unlimited seats and unlimited reads, and Free covers 3 bins. Nothing scales with your users. For comparison, LaunchDarkly's Foundation plan lists $10 per 1,000 client-side monthly active users a month ($8.33 billed yearly), plus service connections. By our reading of their pricing page, an app with 20,000 monthly users reading flags client-side would be around $190 a month before anything else.

You can't publish broken config

A JSON Schema on each bin is checked on every publish, promote and rollback. A wrong type or a missing key is refused with the line and the rule it broke:

terminal
$ hotcfg push flags.json --bin mobile-flags --env staging
error: flags.json does not match the schema of bin mobile-flags (1 error)

  flags.json:3  /limits/max_upload_mb
    rule:    /properties/limits/properties/max_upload_mb/type
    message: expected integer, but got string

Config, not just flags, from a URL

Flags and settings live together, in the shape your app decodes:

mobile-flags.json
{
  "kill": { "payments": false },
  "limits": { "max_upload_mb": 25 },
  "banner": "Scheduled maintenance Sunday 02:00 UTC"
}

And reading it is one request, with no SDK:

config.js
const config = await (await fetch("https://api.hotcfg.run/v1/acme/mobile-flags")).json();

The recommended version adds a timeout and a fallback to the last good copy, in one short file you own (about 20 lines in JavaScript, 40 in Swift or Kotlin). Reads come from Cloudflare's edge, and keep being served for up to a week if hotcfg's servers are down.

Small enough to learn in one sitting

Create a bin, push JSON, read a URL. The dashboard is your bins, an editor, history with diffs, keys and your team; there are no contexts, segments, rules or SDK configuration to understand first. Development, staging and production come with every bin, with promote and one-command rollback.

At a glance

hotcfgLaunchDarkly
What you manageJSON documents (bins), any structureFeature flags (boolean and multivariate) with targeting rules
ValidationA JSON Schema checked on every publish, promote and rollbackFlag variations are typed
How apps read itA plain HTTPS URL, from any HTTP clientLaunchDarkly SDKs, server- and client-side
EnvironmentsDevelopment, staging and production per bin, with promote and a diff3 environments on the free plan, unlimited on paid plans
PriceFree for 3 bins; Pro $19 a month per organization, unlimited seats and readsFree Developer plan; paid plans priced by usage (service connections, client-side monthly active users)
TargetingPlatform, build number and percentage overrides with a jq filterUsers, accounts, devices and any context; segments; percentage rollouts
ExperimentsNoneA/B/n tests, multi-armed bandits, statistical analysis
ApprovalsNoApproval requests on paid plans, required workflows on Enterprise
Audit logOn Pro, 90 daysYes

What hotcfg doesn't do

  • Per-user targeting. hotcfg never knows who your users are. Overrides by platform, build number or rollout percentage work with a jq filter.
  • Experiments. There are no variations to measure against each other.
  • Streaming. Apps see a change on their next fetch, typically at launch or when they come back to the foreground.

If your config is a handful of kill switches and settings, you don't need those, and you don't pay for them.

Facts about LaunchDarkly are from its documentation and pricing page as of November 2026. Something out of date? Tell us.

Try it with your own config.

Free for 3 public configs (bins), each with development, staging and production. No card needed. Three short steps from sign-in to an app reading its config, in the dashboard or the CLI.