One person, one extension.

I’ve worked on local-first apps and offline-capable web tools for years, and IndexedDB has always been the part where tooling falls off a cliff. Chrome’s built-in Application panel can list databases and dump records, but the moment you need to filter, project, edit at scale, or export — you’re either pasting cursor code into the console or wishing for a real database client. IdxBeaver is that client, sitting inside DevTools where you’re already debugging.

It’s deliberately scoped: zero network, zero accounts, zero telemetry. The whole thing is MIT-licensed and runnable from source.

I’m a product-minded engineer who likes shipping small, well-built tools. Beyond IdxBeaver, you can see other things I’ve worked on — design, code, writing — at adysfolio.vercel.app.

• Portfolio: adysfolio.vercel.app
• GitHub: github.com/adityaongit
• Source for IdxBeaver: github.com/adityaongit/idxbeaver

• Inspect the inspector. A tool that reads storage data should be auditable end-to-end. Source is open; there are no obfuscated bundles.
• No network unless you ask. The extension never talks to a server. There are no analytics events, no crash reporters, no remote configs.
• Stay close to the platform. The query language compiles down to native IndexedDB cursors and indexes — no shadow database, no shadow APIs.
• Density beats decoration. The UI is built for power users with hundreds of stores and thousands of rows. Pinning, resizing, sticky headers, keyboard navigation — the things you actually use every day.

Bugs, feature requests, and feedback are all welcome on GitHub Issues. If you want to install the extension, that lives on the Chrome Web Store.