01
Apply
Start through contact with your Postgres footprint, migration workflow, and the kind of review pain your team is dealing with.
Design partner program
Turn risky migrations into
governed releases.
The free CLI is available today. We are shaping a governance layer around it with a small group of design partners: risky migration PRs, required approval, audit history, and compliance export. No fixed pricing, no self-serve product yet.
What we are exploring
Approval workflow and audit evidence, not a hosted paywall.
The free analyzer stays local. We are shaping a governance layer that turns risky Postgres changes into a review process with clearer defaults, approvals, exemptions, and accountability.
- Free analyzer stays local The CLI, LSP, docs, and reporting outputs remain available without an account, login, or hosted dependency.
- Design partner program The current engagement is with a small group of teams that need consistency, approvals, and review evidence around risky schema changes, and want to help shape what governance looks like.
- Hands-on rollout help Design partners get direct support on rollout, policy shape, and review process design while the governance workflow is shaped with their real production migrations.
Step 1
Start with the shipped OSS analyzer.Roll the CLI and editor checks into the repository your team already uses for migrations.
Step 2
Define how risky changes should be reviewed.We help shape what happens when HIGH and CRITICAL migrations are flagged in your workflow.
Step 3
Shape governance around one production scope.The engagement stays narrow and accountable so the team can prove out approvals, policy, and review evidence in one real workflow before anything broader exists.
Founder support Manual onboarding No DB creds
Built with the cohort
What the design partner program is built around
The open-source analyzer stays local. The exploratory governance workflow adds collaboration and enforcement around the migrations that need human sign-off, shaped together with design partners.
Approvals
We are exploring sign-off flows for HIGH and CRITICAL migrations before they merge, with an auditable approver trail.
Policies
We are shaping central controls for lock-timeout rules, risk thresholds, and exemptions so teams can enforce shared guardrails.
Audit log
We are validating what teams need recorded about analyses, approvals, and bypasses for review and compliance evidence.
No DB creds
The public analyzer already supports stats snapshots for size-aware risk scoring, so future governance workflows do not need direct production database credentials.
Best fit
Who should join now
The design partner program is for teams with real migration risk, not casual curiosity.
Production Postgres teams
You use Postgres in production and schema changes can create real customer impact if review goes wrong.
ORM-heavy workflows
You ship migrations through Prisma, TypeORM, Knex, Sequelize, Drizzle, or mixed raw SQL workflows.
No dedicated DBA gate
Application teams own schema changes and need better review consistency before merge.
Need accountable process
You care about approvals, policy, and auditability, not just one more lint check.
Governance signal
Why teams talk to us now
The reason to talk is not better detection. The reason to talk is better control over risky changes across the team.
Shared standards
If migration review quality changes with whoever reviews the PR, you already have an organizational problem, not just a tooling problem.
Visible approvals
Teams reach out when they need a clean answer to who approved a risky migration, why it was approved, and what safeguards were expected.
Compliance pressure
If the company needs review evidence for audits, internal controls, or customer trust, migration changes cannot stay an informal side process.
Fewer expensive mistakes
One migration that blocks reads or writes can cost far more than a focused design-partner engagement around safer review and escalation.
How company access works today
There is no account creation or self-serve cloud console yet.
The current access path is a scoped design partner engagement with direct onboarding. We keep the rollout narrow so the team can prove out the workflow before anything broader exists.
02
Qualify
We use a short call to confirm there is a real production workflow, real ownership, and urgency around migration governance.
03
Scope the workflow
If there is a fit, we keep the rollout narrow around one production database or one production application workflow and agree success criteria.
04
Onboard directly
We provision access with your team manually, guide the rollout, and enable cohort features as the governance product is hardened.
Tell us about your migration review process.
We are looking for a handful of teams with painful migration workflows and clear urgency. If there is a fit, we scope one workflow, agree on the engagement, and onboard the company manually instead of sending you to a fake signup flow.