DCS Intelligence is live: first-party analytics with an honesty rule

Second entry in the weekly series — a plain account of what actually went live this week, what's committed but not yet verified, and what we deliberately left showing a blank. As always: if something here can't be checked from the outside, we say so.

The headline this week is that DCS Intelligence — our own analytics dashboard — is deployed and network-verified live at intel.dcsai.ai. It supersedes an earlier internal note that had it only as "claimed deployed." It is no longer claimed; it's confirmed: a custom domain with SSL, a /health endpoint that returns {"service":"DCS Intelligence"}, and the new build serving its UI.

What shipped

1 · The dashboard — live at intel.dcsai.ai

DCS Intelligence runs on its own service (Railway, Node 22). It's a full-page sidebar app with nine analytics tabs — Overview, Pages, Visitors, Geography, Acquisition, Behaviour, Health, Social & Ads, and DCS Verified — plus a Connect tab for managing what feeds it. A range selector spans 7-day through one-year and custom windows, bucketing by day, week, or month as the range widens. The point of building our own rather than renting a dashboard is the same reason we build everything else: we want to own the spine the data sits on.

2 · A first-party data spine

Underneath the UI is a first-party schema — Supabase tables for events, identities, agent runs, receipts, web vitals, page errors, and system errors, with a set of dashboard views over them. Seven token-guarded ingest endpoints sit in front of those tables, so that as each surface starts reporting, the corresponding tab fills from data we collected ourselves rather than a third party's aggregate. The architecture is deliberately ours end to end; the tradeoff is that a tab only lights up once its producer is actually wired in.

3 · Real traffic, today

The live-traffic source is connected and flowing. A PostHog snippet is installed in the shared layout script for both dcsai.ai and dcslabs.ai (deployed via Cloudflare Pages), and PostHog's web-analytics view shows real visitors and pageviews from dcslabs.ai. With that connected, the Overview, Pages, and Geography tabs fill with live numbers rather than samples.

4 · A login wall and a no-placeholders rule

Access sits behind a shared-token login that remembers the device and locks out after three wrong attempts, blocking both the IP and the device until an admin unblock. More important than the gate is the rule behind the data: every Math.random placeholder was removed. Where a source isn't connected, the dashboard shows a literal "—", not an invented number. Raw IP addresses are never returned. An analytics tool that quietly fabricates plausible figures is worse than no tool; this one would rather show you a blank.

The week behind the launch

The other large body of work this week was wiring DCS Verify into the website-build flow — so that a site built on our platform carries a verifiable trust badge, and each agent run produces a linkable receipt that resolves through to an on-chain anchor. Across several repositories, the receipt modal's on-chain view, the badge stamping, the receipt emitters, and the storage-backend anchor worker were all built, committed, and pushed.

I want to be precise about its status, because it's exactly the kind of thing that's easy to over-claim: this work is committed and pushed, but not yet independently verified as live. The repositories are clean and in sync with their remotes, and the git-connected pages should auto-deploy on push — but until we've confirmed the resolved badge-to-receipt-to-anchor path from the outside, we're calling it built, not shipped. When it's verified live, it'll get its own entry here.

In the same window, we also opened a site bug-fix campaign across the three public surfaces — a consolidated tracker of broken links, stale labels, and cross-mentions to clear before the next set of launches. Unglamorous, and exactly the work that should happen before, not after, a launch.

The rule for this dashboard is the rule for the company: show what's real, mark what isn't connected, and never let a placeholder pass for a measurement.

What is not done yet (and we want you to know it)

The cadence holds

Same pattern as last week: build it on a spine we own, verify the live surface from the outside before we claim it, and write down — by name — the parts that aren't connected yet. A dashboard that shows you a blank where it doesn't have an answer is, oddly, the most trustworthy kind. That's the standard we're trying to hold everywhere, and this week it shipped as a product.

— Deepak