graph TB
subgraph "Internet"
ISP1[ISP]
ISP2[ISP]
end
subgraph "Tessera (legacy topology)"
subgraph "PublicSubnet"
LB[Load Balancer]
FW[Firewall]
end
subgraph "AppSubnet"
WS[Web Server]
AP[App Server]
DB[Database]
end
subgraph "ManagementSubnet"
DC1[Domain Controller]
DC2[Domain Controller]
end
NAT[NAT Device]
RTR[Router]
LB -- HTTPS --> FW
FW -- HTTP --> WS
WS -- "App traffic" --> AP
AP --- DB
DC1 --- DC2
ISP1 -->|Internet| NAT
ISP2 -->|Internet| NAT
NAT --> RTR
RTR -- "App subnet" --> AP
RTR -- "Mgmt subnet" --> DC1
RTR -- "Mgmt subnet" --> DC2
end
Network Diagram (legacy)
IT Infrastructure
Network Management
Legacy network-logical diagram for the Tessera platform. Superseded by the cloud-native architecture diagram (DOC-NET-001) and retained for historical reference.
| Title | Network Diagram (legacy) |
| Doc# | DOC-ITIN-002 |
| Version | 1.0 |
| Date | 08-03-2023 |
SUPERSEDED: This legacy network-logical diagram depicted an earlier load-balancer / firewall / web / app / database topology and no longer reflects the platform as operated. The current, cloud-native reference architecture — VPC topology, multi-tenant application and data tiers, encryption, identity and AI services on AWS — is the Cloud-Native Architecture Diagram (DOC-NET-001, v2.0). Refer to that document for anything relating to the ISO/IEC 27001:2022 certification-readiness audit or to the TSR-INC-2025-031 incident. This page is retained for historical comparison only.
The diagram below shows the earlier logical layout, in which traffic entered through a public-facing load balancer and firewall, reached a web and application tier, and was served from a database tier, with a separate management subnet for domain controllers. It predates the move to the VPC-based, containerised, multi-tenant design documented in DOC-NET-001.