Local-first developer tools

Catch the change.
Before it ships.

Your schema changed. Did your contract?
Validate JSON. Compare revisions. See what needs a second look — without uploading your data.

No signup. No API key. Runs in your browser.

Schema review / PurchaseInteractive example
purchase.schema.jsonv1 → v2
1{
2 "properties": {
3 "total": {
− "type": "number",
+ "type": "integer",
+ "minimum": 1
7 }
8 }
9}
Ready to compare.
Computed locally. No network upload.Open full workspace ↗
Small surface. Clear boundaries.Browser-local processingJSON Schema validationRevision comparison
One focused workflow

Less guessing.
More understanding.

A valid document isn’t always a compatible change. Keep payload validation and schema review together, with the context to make the call.

01

Bring a schema. Keep it yours.

Paste JSON or open a local file. Processing stays in this tab’s browser worker. No workspace setup, no document upload.

How data is handled
02

Test the payload against the contract.

Check types, required fields, enums and constraints. Findings show the JSON path and the rule that didn’t match.

Validate a payload
03

Give every change a second look.

Compare revisions for narrower types, new requirements and tightened bounds. Download the report before you decide what ships.

Compare revisions
PAYLOAD CHECKSample payload
Purchase / example payloadNeeds attention
{
  "id": "order_demo",
  "status": "paid",
  "total": "42.50",
  "currency": "USD"
}
!
/total · expected a number

A string value doesn’t satisfy the numeric contract.
Adjust the payload or review the schema.

Sample data, not a production log.JSON / schema
Built with restraint

A tool, not a black box.

  • 01Deterministic validation, powered by Ajv.
  • 02Changed advanced rules are flagged for manual review.
  • 03No remote reference fetching, accounts or AI calls.
  • 04Available today as a free developer preview.

Make the next change
a deliberate one.

Start with the example. Then bring your own contract.

Open the playground