I’ve always found managing large, nested JSON structures a bit of a nightmare - especially when trying to keep the documentation, the raw data, and the validation logic in sync.

So I built Bassanite, a tool focused on the Visual Construction and Editing of JSON schemas.

The Core Focus:

1. Visual Schema Builder: Instead of hand-coding JSON, you build it visually. It handles deeply nested objects and arrays with a clean UI, allowing you to define types, constraints, and default values without losing track of the structure.

2. Integrated Content Editor: Once the schema is defined, you can immediately switch to the "Content Editor" mode to input data that strictly adheres to your schema. It’s like having a dynamic CMS interface for any JSON structure you create.

3. Local-First & Privacy: I built this for developers who handle sensitive data. All parsing and building happen 100% in your browser using local AST processing. No JSON data ever touches my server.

Technical "Quality of Life" Features:

• Zero-DB Sharing: I used URL hash encoding to store the entire schema state. You can share your custom builder with others via a simple link—no database required on my end.

• Auto-Inference: You can paste an existing JSON blob, and the tool will reverse-engineer the schema tree for you.

• Optional Code Generation: If you need to bring your schema into a codebase, it can export to Zod, TypeScript, and Prisma (though the focus is on the builder itself).

I'm currently a solo dev working on this and would love to hear from this community: How do you currently visualize and maintain your JSON schemas, and what’s the biggest pain point in your workflow?

I’m also planning to add DuckDB-WASM support for handling massive local datasets soon.

Link: https://bassanite.dev

I built a local-first visual schema builder to manage complex JSON structures without "Schema Drift" also to fix my "JSON Anxiety".