BetterConfig docs

BetterConfig is hosted remote config. You keep your configuration as JSON, organized per environment, and edit it in a real in-app editor. When you publish, your config propagates to an edge-cached read API running on a global network, so your app reads fresh values with low latency from anywhere. No redeploys to change a value.

• JSON config values, stored and versioned per environment.
• A real in-app JSON editor with full change history and rollback.
• Publish to a global edge read API with aggressive caching.
• Read-only API tokens, scoped to a project or a single environment.
• Team members with owner, editor, and viewer roles.

Also planned:Feature flags with targeting and percentage rolloutsComing soon·Native typed SDKs for iOS, Android, web, Node, and GoComing soon

Today you read config over plain HTTPS with curl or fetch. See Reading your config.

1. 1Create a project from your dashboard.
2. 2Add the environments you need, such as dev, staging, and prod.
3. 3Add config keys with JSON values in the editor, then publish to push them to the edge read API.
4. 4Open History to review every change, and roll back to a previous version if needed.
5. 5Invite teammates by email and assign each one a role.

Already have config somewhere else? Bring it over in one upload. Open your project's Keys page, click Import, and drop in a file. Two formats are supported, and the right one is detected automatically:

• JSON key/value. A single JSON object where every property becomes a config key. Types are inferred from the values, including nested objects and arrays.
• Firebase Remote Config. A Remote Config template export, downloaded from the Firebase console, CLI, or REST API. Each parameter's default value is imported with its declared type.

{
  "checkout.enabled": true,
  "api.timeoutMs": 5000,
  "banner.title": "Spring sale",
  "theme": { "accent": "#095D43", "radius": 8 }
}

# Firebase CLI
firebase remoteconfig:get -o template.json --project your-project

# Or the Remote Config REST API
curl "https://firebaseremoteconfig.googleapis.com/v1/projects/your-project/remoteConfig" \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" \
  --compressed -o template.json

Nothing is written until you confirm. The dialog previews every key with its inferred type, flags the ones that already exist, and lets you pick the environment to import into. New keys receive the imported value in that environment and start from the type's default everywhere else. For keys that already exist, choose to skip them or to overwrite their value in the target environment. Overwriting appends a new version, so history stays intact and you can roll back. Re-importing an unchanged file writes nothing, and a single import handles up to 500 keys from a file of up to 10 MB. Got a bigger template? Split it into several files of up to 500 keys each and import them one at a time.

Export is the reverse. Click Exporton the Keys page to download the selected environment's live keys as a flat, alphabetically sorted JSON file. The file matches the JSON import format exactly, so you can move config between environments or projects, keep a local backup, or check a snapshot into your repo.

Create an API token in your project under Settings → API tokens. Tokens are read-only. A project-scoped token can read any environment in the project; an env-scoped token is locked to a single environment. Treat tokens as secrets and pass them in the Authorization header.

curl "https://api-public.betterconfig.dev/v1/config?project=<slug>&env=prod" \
  -H "Authorization: Bearer $BC_TOKEN"

{
  "projectSlug": "acme-web",
  "environmentKey": "prod",
  "version": 12,
  "fetchedAt": 1730000000000,
  "values": {
    "checkout.enabled": true,
    "api.timeoutMs": 5000,
    "theme": { "accent": "#095D43" }
  }
}

const res = await fetch(
  "https://api-public.betterconfig.dev/v1/config?project=acme-web&env=prod",
  { headers: { Authorization: `Bearer ${process.env.BC_TOKEN}` } },
);

if (!res.ok) throw new Error(`config read failed: ${res.status}`);

const config = await res.json();
const timeout = config.values["api.timeoutMs"]; // 5000

BetterConfig offers Free, Pro, and Ultra plans. Each plan sets limits on reads per month, stored config size, and the number of projects, environments, and members. Usage is metered and enforced, so reads past your monthly quota are rejected with a 429 until the quota resets or you upgrade. See the pricing page for the current numbers on each plan.

For worked examples of BetterConfig in real apps, see the blog. Ready to build? Create an account and publish your first config in minutes.

Stuck or have a question? Email us at support@betterconfig.dev.