Code, tree, grid, graph
Four synchronized ways to read the same document. Lazy tree expansion, virtualized rows and a structure map that stays responsive.
local-first · no account · no uploads
Inspect structure, profile fields, find data-quality problems, query with real engines, compare versions, build transformations and debug API payloads. Everything runs on your device, in workers, without sending your documents anywhere.
Records
1,204
Max depth
6
Nullable
3 fields
Duplicate IDs
0
Missing email
12 (1%)
Quality score
86/100
Illustrative report layout. Real values come from the document you open — the studio never fabricates statistics.
Views share one parsed document and one selection. A path found while profiling opens in the tree; a record filtered in the grid can be exported or transformed without re-importing anything.
Four synchronized ways to read the same document. Lazy tree expansion, virtualized rows and a structure map that stays responsive.
Field cardinality, null frequency, missing fields, outliers and duplicate records — with custom rules, severity and a remediation note for every finding.
Infer JSON Schema from one or many documents, compare versions, detect breaking changes and validate with AJV Draft 7 / 2019-09 / 2020-12.
Structural comparison with identity matching, three-way merge with explicit conflict resolution, RFC 6902 and RFC 7396 export.
JSONPath, JMESPath, JSONata and a compact SQL dialect. Then a 21-step visual pipeline with per-step previews and generated code.
HAR and cURL import, snapshot drift detection, TypeScript types, JSONL timelines, correlation tracing and log-level filtering.
There is no backend for document processing. Parsing, validation, profiling, queries, diffs and transformations execute in browser workers. Local persistence uses IndexedDB, and you can clear all application data from Settings at any time.
The public tool pages run the same local libraries as the studio. No document content is sent to an AI service. The optional assistant talks only to an Ollama endpoint you configure, and it is off by default.
Each page runs a real local tool and links into the full studio for deeper work.
A tool that hides its boundaries is harder to trust. These are the current constraints; the documentation covers each in more detail.
No sign-up. Drag a JSON file onto the studio, or start from a sample.