DEV Community

Collabier
Collabier

Posted on

I got tired of bloated dev utility sites leaking tokens, so I built an 80-tool offline suite in Next.js 16 and WASM

Title: I got tired of bloated dev utility sites leaking tokens, so I built an 80-tool offline suite in Next.js 16 and WASM

Link: https://omnikite.vercel.app

GitHub: https://github.com/nadim-chowdhury/omnikite-project

Hey everyone,

Like most developers, I regularly need quick tools throughout the day: formatting a JSON dump, checking an expired JWT signature, calculating a CIDR subnet, or merging two PDF files.

The problem is that 90% of the top Google results for these tools are either:

  • Sending your confidential strings/tokens to a remote backend API.
  • Covered in popups and auto-playing ads that shift the layout.
  • Slow and bloated.

So I spent the last few weeks building Omnikite β€” an open, zero-install workspace with 80 tools that run 100% client-side in your browser memory.

Features & Highlights:

  • πŸ”’ Zero Data Transmission: Sensitive JSON, JWTs, and files never leave your machine. It works completely offline.
  • ⚑ Instant Execution: Sub-millisecond speeds using WebAssembly (WASM), Web Workers, and the native crypto.subtle API.
  • ⌨️ Command Palette: Press ⌘K anywhere to search and launch any tool instantly.
  • ⭐ Local Favorites & Recents: Pin your daily tools with zero signup required.
  • πŸ“± Clean UI & Dark Mode: Built with Next.js 16 App Router, React 19, and Tailwind CSS v4.

A few of the flagship utilities:

It’s completely free to use: https://omnikite.vercel.app

I'd really appreciate any feedback, bug reports, or suggestions for new tools!

Top comments (1)

Collapse
 
amitfeldman profile image
Amit Feldman

Congrats on the launch β€” an offline-first, no-tracking tool suite is exactly the right instinct.

I ran a quick public check of omnikite.vercel.app (headers + public config only):

  1. No Content-Security-Policy β€” for a suite whose pitch is "nothing leaves your browser," an enforcing CSP is the header that proves it.
  2. X-Content-Type-Options, Referrer-Policy, and Permissions-Policy are all unset.
  3. X-Frame-Options missing, so any tool page can be iframed by a lookalike domain (clickjacking).

The good news: you're on Vercel, so this is one block β€” a headers() entry in next.config.js (or vercel.json) attaches all five headers to every route, no app code touched. HSTS preload-grade and the TLS setup are already solid, and ~600 ms response is quick.

Happy to re-run the check free once the headers land β€” the before/after delta on a privacy-positioned product is a nice trust artifact. Good luck with launch week!