Multi-surface foundation

One codebase now, clean subdomains when you are ready.

The project is structured so the root site stays marketing-focused while dashboard and admin grow behind separate internal namespaces that can be rewritten from dedicated hosts later.

Open dashboard shell Open admin shell

Request routing

Local development still works directly on path-based routes, which keeps auth, links, and feature development straightforward before DNS is in place.

secunit.cloud              -> /
dashboard.secunit.cloud    -> /dashboard/*
admin.secunit.cloud        -> /admin/*

secunit.cloud

Landing

Public marketing pages, docs, signup flows, and SEO-facing content.

Visit landing

dashboard.secunit.cloud

Dashboard

Customer workspace, authenticated product flows, billing, and settings.

Visit dashboard

admin.secunit.cloud

Admin

Operational tools with tighter auth, audit requirements, and stricter guardrails.

Visit admin

Prepared now

The structural work is already in place, so the remaining product work can happen inside each surface without changing the domain model again.

Marketing, dashboard, and admin are now isolated behind their own route roots and layouts.

Subdomain routing is handled in one root-level proxy file instead of leaking host checks across pages.

Domain names and subdomain labels are centralized in a config helper and can move to env without touching route code.