JSON Crack

Yes — the JSON Crack core is open-source under AGPL on GitHub (35k+ stars), and you can self-host it via the published Docker image. The hosted jsoncrack.com Editor is a paid SaaS layer built on top with additional features (AI assistant, team workspaces, large-file mode). Self-hosting gives unlimited file size and full privacy, which matters when visualizing JSON that contains production data.

The hosted free tier on jsoncrack.com is free with no account up to roughly 4MB documents and basic visualization (no AI, no team features). The Editor Pro tier is $9/month and adds AI summarization, large-file support, schema generation, and shareable workspaces. The open-source core is free to self-host indefinitely, which is the path most engineering teams take for private data.

Traditional JSON tree viewers (browser DevTools, jq, IntelliJ's JSON viewer) display the structure as indented text — fine for shallow JSON, painful for deep API responses. JSON Crack's graph view reveals relationships and array structure at a glance, which is particularly valuable for understanding GraphQL responses, OpenAPI examples, and config files. For one-off reading of a 200-line config, a tree viewer is fine; for grokking a complex API response, JSON Crack is faster.

JSON Crack installs as a PWA and the rendering runs client-side, so once cached you can paste local JSON and visualize without a network. The AI features (when subscribed) require network. The recommended path for offline or sensitive use is to self-host the open-source core via Docker, which removes any dependency on the hosted instance.

JSON Crack is used by backend engineers debugging GraphQL and REST responses, frontend developers exploring third-party API contracts, data engineers visualizing nested Kafka payloads, and DevOps teams reading Kubernetes manifests and Helm values files. It is also commonly used by technical writers building API documentation, since the exported PNG/SVG graphs are clearer than indented JSON in published docs.