Compare

hotcfg vs Firebase Remote Config

hotcfg is remote config that can't be pushed broken, with a real staging step and no SDK in your app. How it compares with Firebase Remote Config.

If you're here because…

  • Changes don't show up when you expect. By default the Firebase SDK fetches new values at most every 12 hours, and lowering that means thinking about throttling.
  • Staging means a second Firebase project to create and keep in sync.
  • A typo reached production, because nothing checked the values before they went live.
  • You'd rather not add Firebase to your app just to read some config.

…hotcfg is built around exactly those.

Why hotcfg

You can't publish broken config

Attach a JSON Schema to a bin, and every publish, promote and rollback is checked against it. A wrong type or a missing key is refused before any user sees it, 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

Staging before production, built in

Every bin has development, staging and production. Push to staging, try it with a staging build, then promote that exact version to production after reading the diff. Roll back to any earlier version in one command.

A URL instead of an SDK

This is the whole integration:

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

The recommended version adds a 2-second timeout, the ETag, and a fallback to the last good copy, in one short file you own (about 20 lines in JavaScript, 40 in Swift or Kotlin), for every common language. Nothing is added to your app's binary or startup, and it works where the Firebase SDKs don't reach: game engines, desktop apps, scripts and devices. Public bins are served 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

The dashboard is your bins, a JSON editor, history with diffs, API keys and your team. There are no conditions, audiences or templates to learn first. Config is one JSON document in the shape your app decodes, not a list of flattened parameters. The quickstart goes from sign-in to an app reading its config in three short steps, in the dashboard or the CLI.

Why pay when Firebase is free?

Firebase Remote Config is free because it's part of a platform: you adopt its SDK and its project model. hotcfg is free for 3 public bins, and Pro is a flat $19 a month per organization, with unlimited seats and reads. What that buys is a push that can't break production, a staging step and a rollback that takes seconds. If one bad config push would cost you more than $19 in support time or lost sales, the guardrails pay for themselves.

At a glance

hotcfgFirebase Remote Config
ValidationA JSON Schema checked on every publish, promote and rollbackNo schema across parameters
EnvironmentsDevelopment, staging and production in every bin, with promote and a diffOne project per environment
How apps read configA plain HTTPS URL, from any HTTP clientThe Firebase SDK (iOS, Android, Web, Flutter, Unity, C++), or server SDKs
Shape of the configOne JSON document per bin, any structureKey/value parameters, each a string, number, boolean or JSON value
HistoryNumbered versions, rollback to any kept one (10 on Free, 100 on Pro)Up to 300 stored template versions, rollback to any
From CIOpen-source CLI: push, diff, promote, roll backFirebase CLI and REST API for templates
TargetingPlatform, build number and percentage overrides with a jq filter; no per-user targetingApp version, language, Analytics audiences, imported segments, custom signals, random percentage
ExperimentsNoneA/B Testing and rollouts, with Analytics and Crashlytics
Updates reach appsOn their next fetch; the edge copy is purged on publishOn the next fetch (by default at most every 12 hours), or in real time with a listener
PriceFree for 3 bins; Pro $19 a month per organizationNo cost

What hotcfg doesn't do

  • Audiences and A/B tests. hotcfg never knows who your users are. Overrides by platform, build number or rollout percentage work with a jq filter.
  • Real-time push. Apps see a change on their next fetch, typically at launch or when they come back to the foreground. For kill switches and settings, that's usually soon enough.

Moving from Firebase

Export your template from the Firebase console (it's JSON), turn the parameters into one document, and write a schema for it. Then point the app at the bin's URL with the fetching code for your language.

Facts about Firebase are from its documentation 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.