Developer-first Configuration Files Storage

Configuration is code's quieter half: the JSON of feature flags, the YAML of environment settings, the TOML your CLI reads, the remote kill-switch that should flip without a redeploy. When that config has to reach app instances spread across regions, you want it fetched fast and you want a clear history of what changed. files.link stores config files as plain, fetchable objects on a global CDN, with versioning you control through naming — no SDK to embed, no proprietary config service to learn.

The pattern most teams use is immutable, versioned filenames: write config-v3.json (or config-2026-06-25.json) as a new object rather than overwriting config.json in place. Each version gets its own permanent URL, so a rollback is just pointing back at the previous URL, and you have an auditable trail of exactly which bytes were live when. Publishing a new version is the usual three calls — POST /v1/files/{folderId} → { success, urls:[{url,id,...}] }, PUT the file's bytes to the presigned url, POST /v1/files/confirm-upload with { ids:[...] }, authenticated by your raw API key — so a deploy step or admin UI can push config without touching servers.

Reading is just an HTTP GET against the CDN URL from any language or runtime, which means a Go service, a browser SPA, and a shell script all consume the same config the same way, no client library required. Feature-flag files in particular benefit: flip a flag by publishing a new flags file and your fleet picks it up on its next fetch, with edge caching keeping reads cheap.

Keep secrets-bearing config private — store it as a private file and read it through short-lived signed URLs minted server-side rather than exposing it publicly; everything is encrypted at rest.

This sits naturally beside terraform-state-storage for infra state, yaml-paste and json-pastebin for quick shares, xml-file-storage for legacy config, log-file-storage and ci-cd-artifact-storage for the pipeline around it, and mobile-app-assets for shipping remote config to apps. cloud-file-storage-api and encrypted-file-storage cover the API and privacy details. Billing is prepaid credits.