Remote config for apps: change values without a release
Veresk is remote configuration for applications, services and games. Edit a config in the browser, publish it to a CDN, and your app reads it. People and AI agents work in the same place.
SDKs, REST API and MCP
From an edit to a running app in three steps
- 1
Edit
Open a project and change a JSON, Lua or text file in the browser. The editor checks the syntax before you can save.
- 2
Publish
Publishing builds a release of the version and uploads it to the CDN, with a manifest for every client.
- 3
Read
Your app loads the files with an SDK or a plain HTTP request. No new build, no store review.
Versions inherit, so every change stays small
A version serves its parent's files until you give it its own copy. Create staging from default, change one file, compare, then promote. Consumers such as ios, android and server get only the files assigned to them.
Built for AI agents
Agents are first-class users. They work with your content the way you do, through open standards, inside limits you control.
- MCP server
- Connect Claude Code, Codex, Cursor, VS Code or Claude Desktop. An agent reads and edits files, manages versions and tags, compares and publishes.
- REST API
- The same operations over HTTP for scripts and CI. One logic behind both, so agents and scripts behave identically.
- Limits you control
- A token carries its owner's permissions. Agents cannot delete projects, change roles or touch encryption keys.
- Docs agents can read
- These docs are plain HTML with llms.txt, llms-full.txt and a Markdown version of every page.
Built for production
- Encryption per file
- Mark a file as encrypted and it is published as ciphertext. Your client decrypts it with the project key.
- Editor with syntax checks
- JSON and Lua are validated before saving. Leave team notes in JSON with $note keys; they are removed on publish.
- Roles per project
- Admins and managers with different permissions. The owner always keeps control.
- Locked versions
- Freeze what you have released. A locked version is read-only.
- A release per version
- Publishing builds one manifest per consumer, so every client receives exactly its files.
- Git integration
- Keep the state of a project in a Git repository alongside publishing.
Frequently asked questions
What is Veresk?
A remote configuration platform. You keep config files in one place, edit them in a browser and publish them to a CDN. Your applications read the published files at runtime.
What can I configure with it?
Anything an application reads at runtime: settings, prices, feature flags, copy and remote content, and in games balance and event schedules. It suits mobile and web apps, backend services and games.
How is this different from shipping a new build?
A config is data your app fetches while it runs. Changing a value means editing a file and publishing, not building, submitting and waiting for a release.
Which platforms are supported?
Any platform that can make an HTTP request can read the published files: a client loads a manifest and the files it lists from the CDN. Ready-made SDKs make that easier, and the list is on the SDKs page of the documentation.
Are my config files protected?
Files marked as encrypted are published as ciphertext and decrypted by the client with the project key. A key shipped inside an app or game build can be extracted, so do not rely on encryption to hide secrets from app or game clients.
Can an AI agent work with Veresk?
Yes. Veresk has an MCP server and a REST API with the same permissions. Agents can read and edit files, manage versions and tags, compare and publish. They cannot create or delete projects, change roles or touch encryption keys.
Can several people work in one project?
Yes. Project admins grant access to other users and assign the admin or manager role.
Try it on your project
Create a project, add a config and publish it in minutes. Questions are welcome on Telegram.