Migrations should be boring.
Every engineer who has taken production down knows the shape of the story: the migration parsed, the tests passed, staging was fine — and then the same SQL met a table with forty million rows and a lock queue. Bolvrk exists to make that story impossible to repeat.
Verify AI work before it reaches production
Software is increasingly written by AI, and nowhere is the blast radius bigger than the database. Bolvrk exists so enterprises can trust AI-driven workflows not to destroy their business from within: a deterministic rule engine that reads the actual parse tree of every migration — whoever or whatever wrote it — and checks it against what Postgres really does: lock classes, table rewrites, validation scans, your real schema's shape and traffic. Not heuristics, not vibes: verified claims with fixture evidence behind every rule, and a run log your team can rely on. Postgres migrations are our first surface; the mission is trust in AI-made change.
The rules we hold ourselves to
AI is never in the trust path
We verify AI work — so no AI, ours included, is ever part of the verdict. Our AI review is advisory commentary, clearly labeled, unable to pass or fail anything. 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 engine 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 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 (MIT), with the outage rules and credential hygiene built in, 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 safety itself.
The boring facts
Bolvrk is built in Denmark by Simon ApS (CVR DK38213458), founded in 2026, at Gersonsvej 40, 1., 2900 Hellerup. The CLI is open source (MIT); 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.
Judge us by the corpus
Every rule states its danger, its evidence, and a minimal example. Read them all.
Read the rule reference