TECHNICAL DOSSIER // TITN SMS // BUILD 2.3.1-web
UNDER THE HOOD.NOTHING TO HIDE.
Most vendors hand you a brochure. This is the architecture. If your IT people have questions after reading it, they're the kind we like answering.
← MARKETING BRIEF01 // STACK
THE STACK
02 // TOPOLOGY
ONE ORIGIN. ONE PORT. ONE RECORD.
In the LAN reference deployment a single Nginx listener fronts everything: `/api/*` is reverse-proxied to FastAPI, everything else is the static React bundle with client-side routing. Same-origin cookies, no CORS games, one place to put TLS.
░░░░░░░░░░░░░░░░░░░░░░░░░ ░░░░░░ ░░░░░░ ░░░░░░░░░░░░░░░░░░░░░░░░░░ ░░ ░░░░░░░ ░░░ ░░░░░ ░░░░ ░░░░░░ ░░░░░░ ░░░ ░░░░░░░ ░░░░░ ░░ ░░░░ ░░ ░░ ░░░░ ░ ░ ░░ ░░░░ ░░ ░░░ ░░░░░░ ░░░░░ ░░░░░ ░░ ░ ░░ ░░░░░░░ ░░░░░░ ░░░░░░░░░░░░ ░░ ░░░░░░ ░░░░░░░ ░░░░░░░░░░ ░░░░░░░░░ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ░ ░░░░░░░ ░░░░░ ░░░░░░░░░░░ ░░░░░░ ░░ ░░░░░░ ░░░░░░░░░░░░░░ ░░░░░░░░░░ ░░░░░░░ ░░░░░░░░░░ ░░░░░░░
03 // SECURITY MODEL
ASSUME THE AUDITOR IS HOSTILE.
ENCRYPTION AT REST
Sensitive fields and evidence are AES-256-GCM encrypted before they touch disk. Keys come from the environment, never from the repo.
SESSIONS & RBAC
Server-issued sessions, role dependencies on every route, a full roles[] array per user, and per-role route guarding in the SPA.
RATE LIMITS & LOCKOUT
Per-IP rate limiting and per-account lockout on authentication endpoints.
SIGNED CAPTURE INTENT
Fingerprint capture is authorized by a short-lived, claim-bound signed challenge. The bridge verifies it; the server verifies the result. Replays die.
AUDIT LOG
Every state-changing action writes an audit event: who, what, when, from where. Append-only by design.
OFFLINE LICENSING
HMAC-SHA256 signed license keys generated offline by the vendor. The server validates without phoning home.
04 // CAPTURE PIPELINE
EVIDENCE WITH PROVENANCE.
05 // COMPLIANCE EXPORTS
WHAT TEXAS WANTS, IN THE FORMAT TEXAS WANTS.
06 // OPERATIONS
BUILT TO BE RUN, NOT DEMOED.
07 // API SURFACE
ROUTE DOMAINS
Every route is namespaced under /api and documented in the API reference. Domain routers:
WANT THE REST OF THE DOCS?
Architecture, API reference, deployment guide, security model — we'll walk your team through all of it.
CALL (346) 787-3662