In-house tool

Insanity Logs

Gigabyte-scale logs, analysed entirely in the browser

Product
Insanity LogsDeveloper tooling
Engagement
In-house build
Stack
  • Next.js
  • React
  • Sanity
  • TypeScript
  • Vercel
Related service
Technical partnerships
Everything runs in the browser; the only optional external call is IP location, off by default.YOUR BROWSERFile pickerup to 2GBStreaming parserWeb WorkerIn-memory indexSeven analysistabsIP locationlookupoptional, off bydefault
Everything runs in the browser; the only optional external call is IP location, off by default.

The challenge

Sanity CMS request logs are dense, gigabyte-scale JSON. Somewhere in there are the slow queries and cost outliers that explain a surprising API bill, but no tool existed to find them.

We kept needing those answers for client work. After the second time hand-rolling scripts, the conclusion was obvious: build the tool properly, once.

What we built

Insanity Logs parses request-log exports entirely in the browser: your logs are never uploaded, which for client logs isn’t a feature so much as a requirement. The only optional external call is an IP location lookup, off by default. Files up to 2GB stream through a background worker, so the statistics cover the whole export without freezing the tab.

Seven analysis tabs cover slow GROQ queries, cost outliers, traffic anomalies, and suspicious IPs. We released it free for any developer. It’s also the self-serve tier of our Sanity CMS audit: run it yourself for nothing, and if the findings warrant a deeper look, that’s the audit.

The results

  • Freefor any developer, no signup
  • 7 tabsof analysis, from GROQ queries to anomalies
  • Tier 0of the Sanity CMS audit funnel

Have a similar problem?

Tell us what you're working on. We'll tell you how we'd approach it.

We reply within one working day.