Design partner program

Use the free analyzer now,
buy governance when migration risk becomes a team problem.

pgfence is not a paywalled CLI. The analyzer stays free. The paid offer is a hands-on design partner program for teams using Postgres in production that want a safer, more accountable process around risky schema changes.

Paid design partner pilot: $6k to $15k ARR.

Apply as a design partner See cloud Trust

Design Partner

Paid today

$6k to $15k ARR

The paid offer is a founder-led design-partner pilot for one production Postgres workflow. You are buying rollout help, review defaults, and a clearer migration governance process while the product hardens.

  • Manual rollout help for the OSS analyzer in CI and editor workflows
  • Direct support on policy shape, approval defaults, and escalation paths
  • Priority access to governance features as they land for the cohort
  • Discounted future pricing in exchange for active design feedback
Apply now How access works

Free

Available now

$0

For individual contributors and teams adopting the analyzer locally.

  • CLI, JSON, GitHub PR comments, SARIF, and GitLab output
  • VS Code LSP integration
  • Docs, blog, trace mode, and safe rewrite recipes
Get started

Business

Target package

Target public plan

Not currently available. This is the likely public packaging once the design partner cohort hardens the product and pricing model.

  • Priced per protected production database or app
  • Planned packaging includes RBAC, approval routing, and expiring exemptions
  • Planned packaging includes audit export and rollout reporting
Talk to us

Enterprise

Later path

Custom

Not currently a live packaged tier. This is the likely path for regulated teams, private deployments, and procurement-heavy rollouts later.

  • Roadmap items include SCIM, SSO, and custom retention controls
  • Roadmap options include self-hosted or air-gapped deployments
  • Security reviews and onboarding support
Talk to us

Buying trigger

Why teams pay

The free analyzer helps an engineer understand one migration. The paid offer helps an organization control migration risk across many engineers and repositories.

Consistency

Stop depending on one Postgres expert or the luck of who reviews the PR. Teams pay when migration safety knowledge needs to become repeatable.

Accountability

Engineering managers and platform leads pay for a clearer process around HIGH and CRITICAL changes, not for one more generic lint check.

Auditability

If risky schema changes need documented approvals, exemptions, and review evidence, the value shifts from detection to governance.

Incident reduction

One blocked production table can create a very expensive day. Teams pay to reduce that blast radius and make review more trustworthy.

Paid today

What the paid pilot includes

Keep this narrow and honest. The pilot is paid because it solves a real workflow problem now, not because every future cloud feature is already self-serve.

One production scope

We focus the pilot on one protected production database or one production application so the rollout stays tight and measurable.

Rollout and policy help

We help your team wire in the analyzer, define review defaults, and map what should happen when risky migrations are flagged.

Design-partner access

You get direct access while we shape approvals, exemptions, audit history, and other governance controls around your real workflow.

Direct support

You are not buying a blank beta. You are buying direct founder support, fast iteration, and a shorter path to the controls your team actually needs.

Cohort access

What a design partner gets

The design partner offer is hands-on and specific. It is not a promise that every governance feature below is already generally available or self-serve.

Shared migration policy

Direct input into how central rules for risk thresholds, policy requirements, and migration review defaults should work across repositories.

Approval workflow

Early access to approval and review flows as we build them for real HIGH and CRITICAL migration cases.

Audit history

A chance to shape what should be recorded when risky migrations are flagged, approved, or exempted.

Founder support

Fast feedback loops, direct product input, and a shorter path to the workflows your team actually needs.

Pilot outcome

What success looks like

A good pilot should leave your team with a better migration review process even before the broader governance product is public.

Better PR review

Reviewers can see lock impact, blast radius, and safe rewrites earlier, so dangerous patterns stop slipping through vague SQL review.

Cleaner escalation path

The team has a clearer default for what needs approval, what needs an exemption, and what should not merge as-is.

Less tribal knowledge

Migration safety stops living in one staff engineer's head and becomes a more teachable, documented workflow.

Stronger buying signal

By the end of the pilot, both sides should know whether governance around migration risk is valuable enough to expand into a longer paid relationship.

Trust promise

What stays free forever

The analyzer is the adoption engine. Governance is the monetization layer.

Local analysis

Static migration analysis with the real Postgres parser, safe rewrites, and coverage reporting.

Developer tooling

CLI, JSON, GitHub comments, GitLab output, and the VS Code extension all stay open source.

No lock-in

Teams can adopt the OSS first and add governance later without changing the developer workflow.

Trust boundary

The public analyzer already supports stats snapshots, so teams can adopt size-aware analysis without handing pgfence production database credentials.

Manual onboarding Access path today

How company access works today

Apply, qualify, and we onboard your company directly for one production workflow.

There is no self-serve company signup today. If the fit is real, we scope the pilot tightly, align on success, and onboard your team manually while the governance layer hardens.

01

Apply

Start through contact with your Postgres footprint, migration workflow, and who owns review today.

02

Qualify and scope

We confirm the fit, narrow the pilot to one production workflow, and agree what success should look like.

03

Onboard directly

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.

Talk to us Cloud beta

Need the trust and security details before you talk to us? Start with the security page.