If hotcfg shuts down
Last updated 10 November 2026
We intend to run hotcfg for a long time, but you're trusting it with config your apps read at startup, so here is what happens if it ever has to close.
What we commit to
- At least 90 days' notice. Every organization administrator gets an email, and the dashboard and this site show the date. We won't close sooner, except where the law or a court order forces us to.
- Reads keep working until the end. Your apps keep getting their config from the same URLs, from Cloudflare's edge, for the whole notice period.
- Writes and the dashboard keep working too, so you can move at your own pace.
- A full export, any time. Every bin, its schema and settings, and every kept version, as one JSON file: Settings → Export, or
GET /v1/organizations/{id}/exportwith a secret key. This is available today, not only when closing. See Exporting your config. - No new charges. Billing stops on the day we announce. Time you've already paid for past the closing date is refunded.
- Your data is deleted afterwards. When the service closes, the database is deleted, and backups are gone within 7 days.
Why your apps won't break
hotcfg is read over plain HTTPS, with no SDK to remove. The recommended fetching code keeps the last config it received and falls back to defaults shipped in the app, so even an app that is never updated keeps working on its last good copy after the URL stops answering.
To move, point your apps at another JSON URL in a release during the notice period. The export holds everything you need to recreate your config elsewhere; it's plain JSON, and the payloads are exactly what you published.
The open-source CLI
The hotcfg CLI is Apache-2.0 licensed and stays available on GitHub.