Everyone reviews code. Nobody reviews the migration. Until now.

Liquibase and Flyway run migrations. Atlas plans schema state. Squawk lints SQL. CodeRabbit reviews the code around them. Bedrock reviews the migration itself — the schema change, its blast radius in your codebase, and the safe path to deploy it. It runs alongside your stack and replaces nothing.
Capability
Bedrockus
Atlas
Squawk
CodeRabbit
SchemaHero
Manual review
Detection
Lints raw SQL migrations
Understands typed schema diffs
Reads the ORM's typed schema (Prisma, Drizzle, and more), not just the .sql file.
Detects schema-touching PRs automatically
Classifies risk by change type
Code awareness
Walks your TypeScript for blast radius
Surfaces affected services / domains
Posts inline PR comments on affected files
Safer rollout
Generates expand-and-contract plan
Generates idempotent backfill SQL
Generates rollback playbook
Suggests tests for new states
Workflow
Native GitHub PR Check
Slack / Linear / PagerDuty
Self-hosted runner (your VPC)
Custom risk policy as code
Scope
Reviews migrations specifically, deeply
Reviews general code (React, APIs, tests)
Bedrock only runs on schema PRs — pair it with CodeRabbit for everything else.
full partial none

Bedrock column reflects current early access: GitHub check, PR summary comment, shareable report, org dashboard, and blast radius. Slack hooks, policy files (bedrock.yml), inline file comments, and VPC hosting are planned for Team and Enterprise tiers.

See it on a real migration

Run the playground, or install the GitHub App on a repo.

Compare — Bedrock