Getting started

Introduction

What Veresk is, who it is for and how its pieces fit together.

Veresk is a remote configuration platform. You keep config files (settings, prices, feature flags, copy, styles, and in games balance and event schedules) in one place, change them in a web editor, and publish them to a CDN. Your applications read the published files at runtime, so a change goes live without shipping a new build.

How it works

  1. Edit. Open a project and edit its files in the browser. The editor checks JSON and Lua syntax before you can save.
  2. Version. Work in versions such as default, staging or season-5. A version inherits files from its parent until you change them.
  3. Publish. Publishing builds a release of the version and uploads it to the CDN: one manifest per consumer, with the files that consumer should receive.
  4. Read. An app uses an SDK (Node.js or Unity) or plain HTTP to load the manifest and the files, and checks for updates.

What it is good for

  • Tuning a live application or game: settings, prices, balance, event schedules.
  • Feature flags and per-environment settings for services.
  • Delivering different config sets to different clients (for example ios, android, server).
  • Letting non-developers change values without touching the code base.

What is in these docs

Quickstart

From an empty project to a config read in your app.

Concepts

Projects, versions, files, consumers, bundles, publishing, access.

SDKs

Node.js and Unity.

REST API and MCP

Automate everything you can do in the editor.

Quickstart

Create a project, publish a config and read it from your app.