Schema Gateway compares a baseline schema against the candidate version, surfaces
provider-specific regressions, and tells you when a change is likely breaking before it
hits CI or production. This is the quickest way to prove the product saves real time.
Baseline vs candidateone report across provider targets
The hosted regression endpoint is available at POST /v1/diff, and the free
demo is available at POST /v1/demo/diff.
Interactive regression demo
Check the schema change before anyone merges it.
This public demo is intentionally limited, but the regression engine is real:
baseline plus candidate schemas in, provider-specific drift and a likely-breaking
verdict out, no API key required.
12 KB request6 KB per schemaNo signup
Live output
The sample run loads automatically so the page immediately shows what the regression report looks like.
Loading a sample regression run...
Show raw regression bundle
Paid access unlocks the signed shared endpoints for /v1/diff,
/v1/compile, /v1/lint, and /v1/normalize.
Why this lands in CI
Regression reports make schema changes reviewable, not just testable.
A portability lint is useful, but a baseline-vs-candidate report is easier for teams
to operationalize because it answers the merge question directly: did this change make
any target riskier?
GitHub Action
Use the same regression engine in CI and fail the workflow when a likely breaking schema change appears.