Free analyzer, design partner program
pgfence is not a paywalled CLI. The analyzer is open source and free forever. Governance is exploratory: we are shaping approvals, audit history, and policy with a small group of design partners with real production migration pain.
Open source is free. Governance is exploratory and only available to design partners today.
Pricing
CLI, LSP, GitHub Action, ORM extractors, lock-mode rules, safe rewrite recipes, and editor integrations are all free, forever. There is no paid analyzer tier, no usage cap, no premium-rule paywall.
Need org-wide migration governance, custom policy support, or compliance-grade audit evidence? We are talking to a small group of design partners. Tell us about your migration review process and we will see if there is a fit.
Governance trigger
The free analyzer helps an engineer understand one migration. Design-partner conversations start when an organization needs a repeatable way to review risky migrations across many engineers and repositories.
Stop depending on one Postgres expert or the luck of who reviews the PR. Teams reach out when migration safety knowledge needs to become repeatable.
Engineering managers and platform leads need a clearer process around HIGH and CRITICAL changes, not one more generic lint check.
If risky schema changes need documented approvals, exemptions, and review evidence, the value shifts from detection to governance.
One blocked production table can create a very expensive day. Teams explore governance when they need to reduce that blast radius and make review more trustworthy.
Design partner program
Keep this narrow and honest. The design partner program exists to solve a real workflow problem with real teams, not to fake every future Cloud feature into being self-serve before it works.
We focus the engagement on one protected production database or one production application so the rollout stays tight and measurable.
We help your team wire in the analyzer, define review defaults, and map what should happen when risky migrations are flagged.
You get direct access while we shape approvals, exemptions, audit history, and other governance controls around your real workflow.
You get direct founder support, fast iteration, and a shorter path to the controls your team actually needs.
Design partner role
The design partner program is hands-on and specific. It is not a promise that every governance feature below is already generally available or self-serve.
Direct input into how central rules for risk thresholds, policy requirements, and migration review defaults should work across repositories.
Early access to approval and review flows as we build them for real HIGH and CRITICAL migration cases.
A chance to shape what should be recorded when risky migrations are flagged, approved, or exempted.
Fast feedback loops, direct product input, and a shorter path to the workflows your team actually needs.
Design partner outcome
A good design partner engagement should leave your team with a better migration review process even before any broader governance product is public.
Reviewers can see lock impact, blast radius, and safe rewrites earlier, so dangerous patterns stop slipping through vague SQL review.
The team has a clearer default for what needs approval, what needs an exemption, and what should not merge as-is.
Migration safety stops living in one staff engineer's head and becomes a more teachable, documented workflow.
By the end of the engagement, both sides should know whether governance around migration risk deserves deeper product work.
Trust promise
The analyzer is the product today. Governance stays exploratory until real teams prove the workflow is worth building.
Static migration analysis with the real Postgres parser, safe rewrites, and coverage reporting.
CLI, JSON, GitHub comments, GitLab output, and the VS Code extension all stay open source.
Teams can adopt the OSS first and add governance later without changing the developer workflow.
The public analyzer already supports stats snapshots, so teams can adopt size-aware analysis without handing pgfence production database credentials.
How design partner access works today
There is no self-serve company signup today. If the fit is real, we scope the engagement tightly, align on success, and onboard your team manually while the governance layer is shaped with you.
01
Start through contact with your Postgres footprint, migration workflow, and who owns review today.
02
We confirm the fit, narrow the engagement to one production workflow, and agree what success should look like.
03
We provision access with your team manually, guide the rollout, and enable cohort features without sending you to a product signup that does not exist yet.
Need the trust and security details before you talk to us? Start with the security page.