Backend
API foundation
NestJS 11 with global config, healthcheck, Mongo platform DB, and tenant connection service ready for schema-per-tenant databases.
- NestJS API with MongoDB (platform db) and schema-per-tenant connection hooks
- Magic link auth flow placeholder + App Owner seeding
- Tenant onboarding endpoint scaffolding
- Validation, global prefix, healthcheck, queue-ready
Seed script readyValidation on
Frontend
Web shell
Next.js app router with SREonCall-inspired theme. Auth helper at /auth now sets httpOnly cookie sessions (consume-cookie) and verifies via /auth/me.
- Theme inspired by sreoncall.com: crisp, dark-on-light with electric blue accents
- Simple call-to-action to track delivery status
- Cards outlining backend + frontend scaffolding
Theme baselineApp router
Next
Upcoming steps
Wire magic link emailer, session issuance, tenant provisioning flow, and start incident/work-ticket models with SLA timers.
- Role-based dashboard surfacing incidents/work tickets
- Email & Slack integration endpoints
- Escalation jobs + notifications
API surface
Latest endpoints
Hit these now; tenant is derived from JWT, roles enforced server-side.
- Magic link auth (+ cookie option): /api/auth/request-magic-link, /api/auth/consume-cookie
- Incidents/work tickets (tenant-scoped, role-gated): /api/incidents, /api/work-tickets
- SLA scaffold via BullMQ + Redis (ack/resolve timeouts on incident create)