About

Production should be boring.

Every engineer who has taken production down knows the shape of the story: the change parsed, the tests passed, staging was fine, and then it met real data, real traffic, or a credential that should never have been committed. Bolvrk exists to make that story far less likely to repeat, whoever or whatever writes the change.

Mission

A deterministic checker for code

Software is increasingly written by AI, and the changes that hurt most are the ones that look fine in review: a lock on the busiest table, a dropped column with live dependents, a credential in a seed file. Bolvrk checks code deterministically: a rule engine that reads the real parse tree of every change, whoever wrote it, and checks it against what the target actually does. Same input, same verdict, every time, and a rule with fixtures behind each one. Today that means databases, Postgres deepest, SQLite in beta, more engines on the way, and committed credentials in any file. Verified claims with fixture evidence behind every rule, and the same bar for every surface that follows.

Principles

The rules we hold ourselves to

AI is never in the trust path

We verify AI work: so no AI, ours or anyone's, is ever part of the verdict. Bolvrk runs no model at all: it verifies AI-written changes deterministically, and the deterministic engine alone decides. If we would not trust a model's judgment with your production database, we do not ask you to either.

Silence over false alarms

A checker that cries wolf gets ignored, and an ignored checker is worse than none. When we cannot prove a claim, we stay silent. Every rule ships with dangerous fixtures that must fire and safe look-alikes that must not.

One surface at a time, done properly

Postgres first and deepest: real libpg_query parse trees, lock claims validated empirically against live Postgres 13–17, and our own backend runs on Postgres. Every next engine and every next surface meets the same bar: a real parser, empirically validated claims, and a fixture corpus, before a single rule ships.

Correctness is never paywalled

The CLI is open source, with the outage rules and credential hygiene built in under the same license, and the same free rules run in the cloud at no cost. Teams pay for the rest of the corpus and live-schema context, never for the core outage rules.

Company

The boring facts

Bolvrk is built in Denmark by Simon ApS (CVR DK38213458), founded in 2026. The CLI and its free rules are open source; the rule corpus beyond the free set is proprietary, and every rule is documented with its fixtures, what fires, what stays silent, and the fix, on its own page in the rule reference. Questions, feedback, or a finding you disagree with, we want to hear it: contact us.