Make your schemas the law.
ValidityCore validates every request, response, and event against versioned rulesets — at runtime, across every service. Breaking changes stop being something you find out about in a reconciliation job three weeks later.
Standards-native — bring JSON Schema, OpenAPI 3.1, or Protobuf. Nothing proprietary sits in your request path.
Your spec passed CI. Your payload still broke three teams.
In a monolith, the compiler enforces the contract between two functions. In a distributed system, that contract becomes a schema file in a repo — and nothing enforces it once the code is running. You write the OpenAPI spec, wire up a validator in a couple of services, and move on.
Then a producer adds a required field. A consumer three teams away deserializes into a struct that silently drops it. CI was green the whole time. The incident shows up two weeks later in a reconciliation job — and now it's data cleanup instead of a rejected request.
ValidityCore moves the check from build time to the request itself.
- Monproducer adds required: tax_idCI ✓
- Monconsumer deploys, drops fieldCI ✓
- +14dreconciliation finds 42k malformed recordsINCIDENT
Everything a contract needs to actually be enforced.
Not a linter you run in CI. A gateway that sits in front of your services and answers, for every payload, one question: does this conform?
Versioned rulesets
Contracts are versioned artifacts, not code. Promote ruleset@v5j2r9 from canary to enforced, or roll a contract back — without shipping a single service.
One validation IR
Bring JSON Schema, OpenAPI 3.1, or Protobuf. Everything compiles to one internal representation, so a Go service and a Python worker answer to the exact same contract.
Field-level verdicts
Every rejection is a structured diff — path, rule ID, ruleset version, expected vs. received. Your clients get an actionable reason, not a bare 400.
Inline enforcement
Sub-millisecond p50 validation inline on live traffic — or out-of-band in observe-only while you migrate. You choose, per route.
Validation ledger
Every decision, pass or fail, is written to an append-only ledger you can query, export, and hand to an auditor. "Was this event compliant when we accepted it?" becomes one query.
Progressive rollout
Stage a ruleset in observe, escalate to warn, then enforce — per route, per version, no redeploy.
Three moves from schema file to enforced contract.
Register a ruleset
Push your JSON Schema / OpenAPI / Protobuf as ruleset@<version>. ValidityCore compiles it to the validation IR and reports what it will enforce.
Route in observe-only
Point a route at the gateway in observe mode. It validates every payload in the background and surfaces violations — without blocking anything.
Promote to enforced
When violations hit zero, promote the ruleset to enforce. Non-conforming payloads are now rejected at the edge with a structured report.
# ruleset.yaml apiVersion: validitycore.net/v1 kind: Ruleset metadata: name: orders-api version: v5j2r9 spec: source: openapi # openapi | jsonschema | protobuf target: POST /orders mode: observe # observe | warn | enforce onViolation: reject
Contracts have a lifecycle. So do rulesets.
| Ruleset | Version | Target | Mode | 24h violations |
|---|---|---|---|---|
| orders-api | v5j2r9 | POST /orders | enforce | 0 |
| events-ingest | v3a1c8 | topic: events | warn | 212 |
| billing-webhook | v9k4m2 | POST /webhooks/billing | observe | 1,048 |
Illustrative. Every mode change is one command and takes effect without a deploy.
"We turned a whole class of 'someone changed the schema' incidents into rejected requests with a stack trace. That's the whole pitch."
"Observe-only was the unlock. We ran it six weeks, watched the violations drain, then flipped to enforce with zero drama."
"The ledger answered an auditor question in one query that used to take a week of log spelunking."
ValidityCore is in its design-partner phase.
General availability is gated. We onboard a small number of teams every other week so each gets hands-on help migrating their contracts — there's no self-serve signup yet.
Observe
Design PartnerFor teams mapping their contracts.
- ·Observe-only validation
- ·2 rulesets
- ·30-day ledger retention
- ·Community support
Enforce
Design PartnerFor platform teams putting contracts in the hot path.
- ·Everything in Observe
- ·Inline enforcement
- ·Unlimited rulesets
- ·1-year ledger · progressive rollout
- ·SSO
Fleet
Design PartnerFor fleets where malformed data is an incident category.
- ·Everything in Enforce
- ·Multi-region · data residency
- ·Signed ledger export
- ·Dedicated onboarding SE
- ·Custom retention
Cohort intake
We onboard a small number of teams every other week so each gets hands-on help migrating their contracts. Tell us about your fleet and we'll route your application to the next review board.
Application received.
Your submission is queued for the next review board. If your fleet is a fit for the current cohort, a solutions engineer will reach out from [email protected]. We batch reviews and don't operate a waitlist you can jump — cohorts are sized to the onboarding help we can give.