Private beta · Waitlist
Private beta

Prevent risky Postgres DDL from shipping

Approve/block governance for schema changes — before locks and bad ALTERs hit production

Join the waitlist

Platform and SRE leaders — get early access updates.

We’ll only use this to contact you about the private beta.

Problem + AI context

Credible pattern; outcome-first, then governance.

The pattern in production

Postgres DDL isn’t just a migration. A bad ALTER or index build can take locks that queue behind live traffic and stall control surfaces while apps keep running. Seen in public postmortems (e.g., Railway‑style Oct/Dec 2025) — details vary, the locking story repeats.

  • Locks cascade on busy systems
  • Connection pools get exhausted
  • Control plane stalls under backpressure

Why now / AI

  • Coding agents and copilots generate migrations/diffs faster than humans review them.
  • Schema churn rises; shared intuition about hot tables, lock risk, lock_timeout, and sizes does not.
  • More DDL proposals from more people (and agents).
Outcome: more change, same physics of locks.
AI is accelerating schema change. Postgres still punishes a bad lock. Nock is approve/block governance so risky DDL doesn’t ship unchecked.

What Nock does

Nock enforces an approve/block gate before risky schema changes ship. It evaluates proposed DDL and requires explicit approval — helping teams build safe, consistent habits around schema evolution.

How it thinks

  • Size‑aware checks — considers table/object sizes when flagging risk.
  • lock_timeout discipline — prevents untamed locks from stalling production.
  • Plain‑language guidance — pragmatic for platform/SRE leads.

Team pricing

Team plan ~$79–99/mo. Final packaging and tiers to be announced for GA.

Private beta / waitlist only — not a public launch.