We're exploring whether teams would want to run Json Web Viewer on their own infrastructure. Nothing like this exists yet — this page is how we find out whether it should. If your team would use it, one email is all we're asking for.
Json Web Viewer is a set of client-side JSON tools — format, validate, repair, diff, and query
documents, or explore them as a tree, table, or graph. It runs entirely in the browser: the public
site's own security policy (connect-src 'self') means the browser is structurally
prevented from sending your document anywhere. Your JSON stays on your machine, and that's enforced
by the browser, not promised in marketing copy.
A self-hosted deployment would take that one step further: the same app, the same feature set as the public site — nothing more — served from infrastructure you control. Behind your firewall, on your intranet, or in your own cloud account. No traffic to our domain at all, not even to load the page. For teams whose policies rule out pasting internal payloads into any external website, however client-side it is, that's the difference between "can't use it" and "can use it."
To be plain about it: a self-hosted version is not built, not priced, and not committed. We are gauging interest before deciding whether to offer one. There's no order form and no waiting list mechanics — just an inbox. If enough teams tell us they'd want this, we'll work out what a real offering (pricing, delivery, support) would look like and come back to the people who wrote in.
Send us a short email — a sentence or two about your team and what you'd use it for is plenty. It commits you to nothing, and it's the only signal we're collecting: this page has no form, no tracking, and no analytics.
No. This page exists to measure interest before anything is built. The public app at jsonwebviewer.com is real and free to use; the self-hosted deployment described here is an idea we will only pursue if teams tell us they want it.
The same application and feature set as the public site — no more, no less — deployed on infrastructure you control, so no traffic leaves your network. Anything beyond that, such as pricing, delivery mechanism, or support, has deliberately not been decided yet.
There is no price, because there is no product yet. If enough teams express interest, pricing would be worked out as part of deciding whether to build the offering — and emailing us commits you to nothing either way.
Yes. The public app runs entirely in your browser, and its Content Security Policy (connect-src 'self') structurally prevents the browser from sending your document anywhere. Self-hosting extends that same guarantee to infrastructure you control, for teams whose policies rule out using any external website at all.
Want to try the app itself? Open the editor or browse every tool in one place.