Pricing built around the engineers who actually touch the schema.
Public repos · open source · solo devs
- Full engine on every public schema PR
- GitHub check run + PR comment
- Schema diff + blast radius + risk score (0–100)
- Generated rollout SQL + rollback playbook
- Shareable report link
- Review dashboard (sign in with GitHub)
- Private repos
- Custom risk policy (bedrock.yml)
- Slack / Linear / PagerDuty hooks
- SSO
Private repos · small teams · up to 15 engineers
Everything in Free, plus:
- Unlimited private repo reviews
- Org review dashboard
- Report history (30 days)
- Weekly review email digest
Billing coming soon
Billed annually at $49/schema PR author/month (saves 17%)
Policy + compliance · growing teams · 5–50 engineers
Everything in Pro, plus:
- Custom risk policy as code (bedrock.yml)
- Org dashboard + full audit log
- Slack / Linear / PagerDuty hooks
- SSO (Google + GitHub)
- Report history: unlimited
- Priority support
Team billing coming soon
Platform teams · VPC deployment · custom classifier
Everything in Team, plus:
- Self-hosted runner (your VPC)
- SAML SSO + SCIM provisioning
- Custom risk classifier (trained on your stack)
- Per-service rollout budgets
- Dedicated founder support
- Custom MSA + DPA
FAQ
How do you define a "schema PR author"?
Any engineer who opens or commits to a PR that touches your schema or migrations in a given billing month. If you have 20 engineers but only 3 touch the schema, you pay for 3 seats.
What if our team doesn't use Prisma?
Bedrock reviews changes across Prisma, Drizzle, TypeORM, Sequelize, Knex, Django, Rails, SQLAlchemy, and raw SQL today. Risk is modeled per engine for Postgres, MySQL, MariaDB, SQL Server, CockroachDB, and SQLite. If your stack isn't listed, join the waitlist and tell us.
Is the playground the same engine as the GitHub App?
Yes. Exact same parser, blast radius logic, risk scoring, and rollout generation. The only difference is the playground uses schemas you paste in — the GitHub App reads your actual PR diff.
Do you store our schema or code?
Schema diffs and review metadata are stored encrypted at rest. Application code is fetched ephemerally per review — we scan it, generate the blast radius, and discard it. We never persist your source code.
Can we start with just one repo?
Yes — install on one repo, watch a few reviews, expand when you're ready. Most teams start with their most active backend service.
Is the Free tier really free?
During early access, yes — no billing, no enforced limits. Pro and Team pricing applies when paid tiers launch. You will be notified before anything changes.