I’m a web developer based in South Korea.
When working on my projects, I always felt a bit uneasy pasting my code, database logs, or API payloads into random online tools. Even if the website claims they do not save anything, I just did not like the idea of my work data being sent to an external server.
So I decided to make a simple toolkit ( https://juicydevs.com ) that runs 100% client-side. Since all the calculations are done locally inside the browser, no data ever leaves your computer.
Since I mostly work on backend tasks, I first built tools to automate my database workflows:
SQL Log Binder: Merges MyBatis or JPA debug logs into runnable SQL queries so I can easily run them in DBeaver.
Excel to DDL: Converts copy-pasted Excel tables into SQL DDL or JPA Entities.
But I did not want to limit it to just backend utilities. I also added features that frontend developers might find useful:
JSON to Zod: Generates Zod validation schemas and TypeScript types from JSON payloads.
SVG Multi-Format Converter: Encodes SVGs for Tailwind background classes, CSS Data URIs, or React Native.
Of course, it also includes standard formatters and decoders (JSON, SQL, JWT, etc.), all running locally without any sign-ups or tracking.
I would love to get your feedback on the project, and please let me know if there are any other tools you would like me to add.
Thank you!
Top comments (3)
Client-side tools have a strong trust story if the boundary is obvious. I would make the “nothing leaves your browser” proof visible in the UI, not just mention it in the README.
Thank you so much for your valuable feedback! I completely agree. I will definitely reflect this and make sure the 'nothing leaves your browser' proof is clearly visible directly in the UI.
Nice, that is the right place to make the promise visible. The strongest version is not just a sentence in the README, but a small trust surface in the product itself: what runs locally, what storage is used, and a clear empty state when there is no network call to inspect.