Settings
Workspace, profile, and API configuration
Read-only demo: this template ships without a backend, so everything below renders from mocks/org.json. Wire these fields to your own API when you add one.
Workspace
- Organization
- Atlas Labs
- Workspace slug
- atlas-labs-prod
- Plan
- Scale (annual)
- Region
- eu-central-1 · Frankfurt
- Data retention
- 90 days
- Created
- Nov 2, 2023
Profile
- Name
- Dana Okafor
- dana@atlaslabs.example
- Role
- Workspace admin
- Timezone
- UTC+02:00 · Europe/Vilnius
- Two-factor auth
- Enabled · TOTP app
API credentials
Placeholder credentials — the demo never signs or sends anything.
- Environment
- Production
- Publishable key
- wr_pub_demo_4f8a2c1b9e77
- Signing secret
- whsec_····························
- Webhook API version
- 2026-06-01
About this template
How the demo works and how to make it yours.
Where do the numbers come from?
Every metric, chart point, table row, and settings field renders from committed JSON files in mocks/. Headline totals are computed from the same series the charts draw, so the overview always agrees with itself, and builds are deterministic because nothing is randomized at runtime.
Is any of this live data?
No. Windrose and Atlas Labs are fictional, and the console never calls a network API. It is an honest, fully populated shell that demos before any backend exists.
How do I connect a real backend?
Replace the typed loaders in lib/data.ts with your own fetches. Components receive plain typed props, so once your API returns the shapes defined in lib/types.ts, every page renders your real data.
Does it include auth or a database?
Neither. The build is a fully static export (out/) you can host anywhere. Add authentication and persistence in whatever stack you prefer — nothing in the template assumes one.
How do I add another page?
Create app/your-page/page.tsx and add the route to NAV_ITEMS in lib/nav.ts so it appears in the sidebar. The shared shell, fonts, and design tokens apply automatically.