The operating system I run my companies from
An internal platform that aggregates analytics across nine services and keeps every product, credential, and venture in one private place.
The challenge
Running several products at once means data scattered across the App Store, Google Play, Firebase, payment processors, Vercel, Cloudflare, and more. No single tool shows the whole picture, and checking seven dashboards a day is how things quietly slip through the cracks.
The build
A Next.js and TypeScript application on Vercel that pulls and caches metrics from every platform on a schedule, alongside registries for products, credentials, and ventures and the internal tooling for day-to-day operations. It's cron-cached so it loads instantly, and auth-gated so it stays private. The public marketing page you're reading right now is its front door.
By the numbers
Nine services tracked. Two pull live through their APIs on a six-hour schedule; three more integrations are built but have never returned data — one is deliberately unimplemented rather than approximated, and the other two are waiting on credentials. The dashboard says so on their face instead of rendering them as zero, because a source that failed and a source with nothing to report must not look alike. Seventeen API routes, every one of which either verifies the caller is the owner or is listed as deliberately public with a written reason — enforced by a test that fails the build if a new route is added without one. More than five hundred automated tests, including ten suites whose only job is to fail when a future change quietly drops a guard. Uptime checks against every monitored site every fifteen minutes. And the whole thing has been through two independent adversarial audits, where the findings were fixed and then pinned by tests so they cannot come back.
The result
One place to run everything — and a working example of exactly the kind of internal platform I build for teams drowning in scattered tools and manual reporting. If your team lives in a dozen tabs and a spreadsheet, this is the shape of the fix. The numbers above are the part worth borrowing: not that the software exists, but that it is measured, guarded, and audited — which is what I would build into yours.