Skip to main content
Store your app’s flags in a public silo and read them when the app starts. To flip a flag, edit the silo. Every app that reads it picks up the change on its next fetch, with no deploy. You will use: a public silo, and optionally Schema Lock.
Anyone with the URL can read a public silo. Put only values that are safe to show in a browser in it, never API keys or secrets.

1. Create the silo

Create a Public silo named app-config with this JSON:
app-config.json
Copy the URL from the Public URL card on the silo’s Overview tab. It looks like this:

2. Read the flags

Always keep a set of defaults in your code. If the request fails or is slow, the app still starts with known values.
config.js
main.js

3. Flip a flag

Pick whichever fits your workflow:

4. Protect the shape with Schema Lock

Every app reading this silo expects maintenance to be a boolean. A typo such as "maintenance": "no" would turn on maintenance mode, because a non-empty string is truthy in JavaScript. Lock a schema on the silo to stop that. With the generated strict schema locked:
If you plan to add new flags often, use Loose mode. Existing flags must keep their types, but new keys are accepted.

Good to know

  • Each fetch is a request. Public silo reads count towards the silo owner’s daily limit. For busy sites, fetch once per session and keep the result in memory or sessionStorage. See Rate Limits.
  • The whole document is returned. Public silos don’t support Query or Search, so keep config silos small.
  • The URL can change. Switching the silo to private or moving it to another region gives it a new URL. Update your apps if you do.