Nothing downstream is at risk
Relium found no meaningful semantic change and nothing downstream that this release puts at risk.
GitHub check passes
Pre-deployment verification for data teams
Verify data changes before they reach production.
Relium reviews every SQL and dbt change on the pull request, traces what it affects downstream, evaluates the impact on your metrics, and returns a release decision — before the change ships.
- Free plan, no card required
- Installs as a GitHub App
- Works with your existing CI
The problem
Code passing tests is not the same as a data change being safe.
A dbt change can compile, pass every test and deploy cleanly, and still silently change what a number means. Tests check the shape of your data. They do not check whether the definition of revenue moved.
What your pipeline checks today
- The SQL compiles
- Schema tests pass
- Uniqueness and not-null hold
- The models build in order
CI is green. The pull request is approved.
What nothing checks
- A filter moved and a third of customers left the model
- A metric definition quietly changed meaning
- Four downstream marts inherited the change
- The board report now disagrees with finance
Nobody finds out until someone questions the number.
How it works
Relium reviews the change where the change happens — on the pull request.
There is nothing to run and nothing to watch. Relium reads the pull request, works out what it would do to everything downstream, and publishes a decision before the merge.
Relium sits here
Decision returned
Verification layer
Relium
Between the pull request and the merge — the last point where the outcome can still be different.
The output
One decision, in three words your team already understands.
Every review resolves to one of three outcomes, with the reasoning and the evidence recorded beside it.
Somebody should look at this
The change alters behaviour in a way a reviewer should see. The decision is visible on the pull request and does not fail the check.
Advisory — merge is not held
This is expected to break something
Relium expects the change to break something that matters downstream, and says exactly what and why.
On Pro, the check fails and the merge waits
Where Relium sits
Before the release, not after the incident.
Most tooling in the data stack tells you what already happened. Relium works on the change that has not shipped yet, which is the only point where the outcome can still be different.
A test asserts that a column is never null. Relium asks whether the definition behind that column still means what it did yesterday.
The risk of a change is not the model it edits — it is everything that inherits from it. Relium traces that path from your compiled dbt project.
Not a dashboard to check and not an alert to triage. A single ALLOW, WARN or BLOCK, published where the merge decision is already being made.
Fits your stack
Four connections, all of which you already have.
Installed as a GitHub App. The decision is published as a check run and a comment on the pull request.
Relium reads your compiled manifest, so lineage, tests, exposures and contracts come from your own project.
One workflow step submits the base and head manifests. Relium shows you the exact file to copy.
Optional. A collector you run with your own read-only credentials submits aggregate metadata — never rows.
Warehouse evidence is collected by a process that runs in your environment, with credentials you hold. See how Relium handles your data.
Pricing
Understand, verify, enforce.
Start free. Upgrade when you want Relium to hold the merge.
Free
Understand
$0
Explore change impact on one repository.
Get started free- Core SQL and dbt analysis
- Downstream impact tracing
- ALLOW / WARN / BLOCK decision
- 1 repository
- 7 days of review history
Starter
Most popular
Verify
$149/month
Verify every change before production, with evidence.
Start with Starter- Everything in Free
- Full KPI impact analysis
- Warehouse evidence
- Runtime evidence
- Up to 3 repositories
- 90 days of review history
Pro
Enforce
$250/month
Enforce safe data releases across your team.
Start with Pro- Everything in Starter
- Merge blocking on a BLOCK decision
- Custom review policies
- Team-wide governance controls
- Unlimited repositories
- Unlimited review history
Prices in USD, billed monthly. Payments are handled by Polar, our merchant of record — Relium never sees or stores your card details. Compare the plans in full.
Questions
Before you connect a repository.
How long does setup take?
Sign in, install the Relium GitHub App on the repository, point Relium at your dbt project, and add one repository secret so your CI can hand over the compiled manifest. Relium walks you through each step and shows you the exact workflow file to copy.
Does Relium need access to my data?
No. The analysis works from your repository and your compiled dbt manifest. Warehouse evidence is optional, and it is collected by a process that runs in your environment with credentials you hold — it reads aggregate metadata such as row counts, null rates, duplicate keys and freshness. Individual rows and cell values are never read or submitted.
Will it block our merges straight away?
Not unless you ask it to. Relium starts in shadow mode: it publishes the real decision on the pull request, but a WARN or BLOCK stays advisory and never fails the check. Enforcement is a deliberate switch, and merge blocking is a Pro capability.
Which warehouses are supported?
The collector currently supports PostgreSQL and SQLite. The core analysis — lineage, semantic diff, downstream impact and the release decision — does not depend on the warehouse and works on any dbt project regardless of where it runs.
What happens if I stop paying?
Your workspace drops back to the Free plan at the end of the paid period. Nothing is deleted at that moment: repositories beyond the free limit stop being reviewed, warehouse evidence stops being accepted, and history is shown for the free retention window. Billing, invoices and cancellation are managed through Polar's customer portal.
Do you support GitLab or Bitbucket?
Not today. Relium reviews pull requests through a GitHub App and publishes its decision as a GitHub check run and comment. GitHub is the only supported host right now.
Get started
Know what changes before you ship.
Connect a repository and open your next pull request. Relium will review the change and publish its decision on the PR.
- Free plan, no card required