The cloud: your system of record Cloud & run log

On-prem: the whole service as one executable

available
Enterprise

Enterprise runs Bolvrk on its own servers: a single bolvrk-server binary with the API, the dashboard, the full rule corpus and the schema inside, one TOML config file, one Postgres you provide. Nothing leaves your network except the GitHub sign-in round trip.

Some teams cannot send a migration to anyone, and some cannot depend on anyone else being up. For them the service is a file. bolvrk-server is built with Bun into one executable that serves the API under /api and the signed-in dashboard on the same origin, applies its own schema on every boot, and runs every team on the full corpus with nothing metered: the agreement is the licence.

It needs a Postgres 14 or later that you own (Bolvrk creates its tables there and touches nothing else) and a GitHub OAuth app on github.com or your GitHub Enterprise Server for sign-in. That sign-in round trip is the only outbound connection: no telemetry, no licence check, no calls to bolvrk.com.

Install in four commands

bolvrk-server init writes a fully commented config. bolvrk-server keygen prints the keypair that seals stored connection strings. bolvrk-server check validates the file and the database connection and names every problem at once; an unknown key is an error, so a typo can never silently disable a setting. bolvrk-server serve runs it, under systemd or whatever you run services with.

Upgrading is replacing the binary and restarting: the schema is additive and applied at boot. Notification targets on your private network are allowed, live-schema context reaches your shadow databases read-only, and the MCP server runs at your own origin for your own agents.

What stays with us

The public site, pricing and billing are not part of the binary; links to the rule reference open bolvrk.com in the browser. The rule corpus ships as bytecode inside the executable and is covered by the Enterprise agreement, which is how every serious on-prem vendor protects what runs on a customer machine. Linux x64 and arm64 builds; macOS for evaluation.

Try it on your next migration

The CLI is open source and needs no account: npx bolvrk check migration.sql

Also in The cloud: your system of record