Blog: Verified — The Main Dashboard Runs on 100% Live Data
Verified: The Main Dashboard Runs on 100% Live Data
Release v1.0.70 — DepthAudit Series
One of the quieter but most important things a platform can do is prove that what it shows is real. In v1.0.70 we completed a formal depth audit of the SaaS Factory main dashboard — and it passed cleanly.
What Is a Depth Audit?
A depth audit is a structured inspection of a UI component or page that answers one question: is this showing real data, or is something faked? Mock data, hardcoded counts, and placeholder states are common shortcuts during early development. Left undetected, they erode trust and hide real system state from operators who depend on accurate information to make decisions.
The audit examines the component's data-fetching layer, how computed values are derived, and whether conditional UI behaves correctly under edge cases.
What Was Audited
The audit targeted dashboard-content.tsx, the server component that powers the top-level dashboard view. This is the first screen operators see after logging in — it surfaces products, pipeline status, recent releases, and the agent job queue.
What the Audit Found
Five Parallel Server-Side tRPC Calls
The dashboard component fires five tRPC calls in parallel at render time, each pulling from a distinct domain:
| Call | What It Fetches |
|---|---|
project.list | All registered products |
pipeline.list | Active development pipelines |
release.list | Recent releases across all products |
observability.getJobsTodayCount | Number of agent jobs run today |
approval.listPending | Approvals waiting for review |
Running these in parallel keeps the dashboard fast while ensuring all panels reflect the same moment in time.
"Products Needing Attention" Is Genuinely Computed
The attention indicator — which surfaces products that require human review — is derived entirely from live data. The component cross-references failed pipelines and pending approvals to produce its count. There is no threshold configuration or hardcoded list involved.
The First Run State Is Properly Gated
New installations see a FirstRunHero component that guides them through setup. The audit confirmed this component is shown only when projectCount === 0. Once a project exists, it disappears and real dashboard content takes over. This prevents the onboarding UI from leaking into active accounts.
Status Badges and Timestamps Are Live
Pipeline and release entries in the dashboard use StatusBadge and TimeAgo components that reflect actual record state. There are no static strings masquerading as dynamic values.
Verdict
No issues were found. No code changes were required. The main dashboard is a reliable, real-time view of platform state.
This audit establishes a verified baseline for the dashboard before future development iterates on it. Subsequent audits will be able to compare against this record.
Depth audits are part of SaaS Factory's ongoing commitment to operational transparency. Every major UI surface is subject to periodic verification to ensure the platform always shows what is actually happening.