Challenge
A growing product needed clear ownership boundaries without fragmenting design foundations, security contracts, or future authentication.
Platform architecture
ThreatCues ecosystem architecture
A multi-host cybersecurity ecosystem that separates the company, professional portfolio, learning application, API, identity, and administration boundaries.
Technical response
Define explicit hostname ownership, separate information architectures, shared low-level tokens, and a versioned Django API boundary instead of cloning one marketing shell.
Outcome
The repository now documents the domain model, keeps each public experience independently canonical, and provides a foundation for staged deployment.
04
Architecture
The delivery path.
- 01Public hosts
- 02Host-aware edge routing
- 03Next.js experiences
- 04Django REST API
- 05PostgreSQL + object storage
05
Security
Controls in context.
- Explicit trusted origins
- Server-managed session direction
- Host isolation
- Security headers and CSP
06
Evidence map
Where the claims can be inspected.
These repository paths are references, not public downloads. They make the scope of each statement explicit.
- docs/domain-architecture.md
- web/src/config/ecosystem.ts
- backend/config/settings/base.py