A SaaS dashboard template is usually just a UI kit
Search "SaaS dashboard template" and you get UI kits: beautiful screens, charts full of placeholder data, and a README that says "connect your own API." That last line is the entire problem. The visual layer is a weekend; the dashboard that customers actually use is the two-to-four weeks of plumbing nobody shows you — authentication, route guards, the tenant filter on every query, the billing wiring, the audit log, the data layer behind every chart.
Archiet takes the opposite approach. You describe the SaaS you are building in plain English, and it generates the dashboard and the backend it depends on. Every chart reads from a real table. Every admin action is permission-checked and logged. Every query is scoped to the signed-in user's workspace. The output is plain source code in the stack of your choice — not a no-code lock-in and not a UI kit you still have to wire up.
What "the whole dashboard" actually means
A real SaaS product has three distinct dashboards, not one. Archiet generates all three from the same spec.
The user dashboard
What a customer sees when they log in:
- An onboarding/empty state for brand-new accounts (a checklist that drives activation, not a blank screen)
- Quick-stat tiles wired to real database tables, scoped to the user's workspace
- A recent-activity feed sourced from the audit/event log
- A quick-actions toolbar for the product's primary jobs-to-be-done
- A notifications dropdown backed by a notifications table
- Search across the entities the user is allowed to see
The admin dashboard
The internal console your team runs the business from:
- Org-wide metrics — MRR, active users, sign-ups today, churn — computed from real billing and event data
- User management: list, search, assign roles, suspend, and (audited) impersonate
- Workspace management: list, suspend, delete, with cascade handled correctly
- Billing overrides: manual subscription edits for support cases
- Feature-flag toggles per workspace for staged rollouts
- An audit log of every privileged action, so the admin console is itself accountable
The analytics dashboard
The reporting surface buyers ask about in demos:
- Sign-ups over time, with range and segment filters
- Active users (DAU / WAU / MAU) computed from the event pipeline
- Revenue: MRR, ARR, and churn pulled from the subscription tables
- Top features by usage, ranked from real event counts
- Funnel and retention charts for the user journey you configured
Because the analytics views read from an actual aggregation pipeline — typed event ingestion, hourly/daily rollups, and a query API with time-range, segment, and cohort filters — the numbers on screen are real on day one, not seeded demo data you have to rip out before launch.
The settings surface every SaaS needs
The unglamorous pages that take longest to build and that customers judge you on:
- Profile — name, email, avatar
- Password change — with a current-password challenge
- MFA — TOTP enrollment plus recovery codes
- SSO — connected Google, Microsoft, and GitHub accounts
- Billing — current plan, invoices, payment method, upgrade and cancel flows
- Team — invite, assign roles, remove members
- API keys — create, list, and revoke, with last-used tracking
- Webhooks — register endpoints and inspect delivery logs
- Notifications — per-channel preference toggles
A generated dashboard vs. a UI-kit template
| | UI-kit dashboard template | Archiet generated dashboard | |---|---|---| | Visual design | Pixel-perfect | shadcn/ui or your chosen design preset | | Auth wired in | No | Yes — httpOnly-cookie sessions, route guards | | Tenant-scoped data | No | Yes — workspace_id filter on every query | | Billing wired in | No | Yes — Stripe / Paddle / Flutterwave | | Role-based access | Stubbed | Real RBAC with policy checks | | Audit log | No | Yes | | MFA | No | Yes — TOTP + recovery codes | | Database schema | No | Yes — PostgreSQL + migrations | | API + OpenAPI spec | No | Yes | | Tests | No | Yes | | Time to first deploy | 2–4 weeks of wiring | Hours |
The data model and architecture you get
The dashboard is generated on top of a real architecture, not bolted onto one later:
- Data model — PostgreSQL schema with the entities your product needs, every tenant-owned table carrying a
workspace_idforeign key and migrations to evolve it safely. - Auth — session auth on httpOnly cookies (never tokens in
localStorage), with role and permission checks enforced at the route layer. - Tenancy — workspace isolation enforced structurally: the filter is in the query helpers, not a convention you have to remember on every endpoint.
- API — REST endpoints documented by a generated OpenAPI spec, so the frontend and any future integrations share one contract.
- Charts — line, bar, funnel, and retention components wired to the query API, reading the aggregation pipeline rather than hard-coded arrays.
Any stack, your design language
Pick a backend — Flask, FastAPI, NestJS, Django, Laravel, Rails, Go, Java, or .NET — and a design preset (shadcn/ui, Material, brutalist, soft-pastel, glassmorphism, or editorial). Archiet generates the same fully-wired dashboard in that combination, so the template matches the stack your team already runs in production.
What you ship vs. what you'd build
A dashboard assembled from a UI kit costs two-to-four weeks of plumbing before a paying customer can do anything useful with it — and that work is identical to what every other SaaS has already built. A generated dashboard is wired end-to-end from the first commit, which frees your engineering time for the differentiated part of your product instead of rebuilding the admin console everyone else already has.
Generate your SaaS dashboard
Generate your dashboard on the free plan — one project per month, no credit card. For deeper background, see the analytics dashboard generator, the multi-tenant SaaS architecture template, and Archiet for SaaS teams. Compare plans on pricing.