Get started
Documentation
hotcfg serves versioned JSON config to your apps, with schemas, environments and rollback. Start here.
hotcfg keeps your app's remote config as versioned JSON. Each change is checked against a schema, tried in staging, promoted to production, and can be rolled back in one step. Apps read it from a plain URL, cached at the edge.
Everything is plain HTTP and JSON. The API base URL is https://api.hotcfg.run/v1.
Start here
- Quickstart: from sign-up to your app reading a value, in five minutes.
- Concepts: bins, environments, versions and keys.
- Fetching config in your app: tested code for Swift, Kotlin, Java, JavaScript and more, which never blocks your app.
Common tasks
- Validate every change with a JSON Schema
- Test in staging, then promote to production
- Push config from CI with GitHub Actions
- Know what happens when hotcfg is down
- Build kill switches and feature toggles
Recipes
- Version and platform targeting with jq
- iOS kill switch without an SDK
- Maintenance mode for a React Native app
- Remote config for Godot
Reference
- Reading a bin and writing over HTTP
- API keys and scopes
- The CLI: install, log in, and every command
- Every endpoint, with the OpenAPI file
- Errors and limits
- Changelog
Last updated 10 November 2026