Skip to content
GitHubLinkedIn

Infra enablers

Use this section when you need the shared infra mental model that enables many systems:

  • identity and authentication,
  • network access (VPN),
  • name resolution (DNS),
  • trust (TLS/certificates),
  • service endpoints (HTTP ingress, DB endpoints, storage endpoints),
  • and a high-level topology snapshot (public vs private).

For the architecture entry points, start at Architecture.

  • Identity (IdP): Microsoft Entra ID is the default for SSO/MFA when available.
  • Private network: core infrastructure runs in the EVEO private cloud (including EVEO DBaaS) and is protected behind SSL‑VPN.
  • Public services: some workloads live on public platforms such as Hostinger (websites) and SaaS providers.
  • Access model: public traffic is limited to HTTP(S); admin and operator access is generally VPN-only.
AreaUse this when…
AccessYou need VPN/SSO context or to understand traffic flow.
ServicesYou’re starting from a service name/URL and need entry points.
EnvironmentsYou want the environment bundle view (GUI → middleware → DB).
ServersYou need “where to log in” and what runs where.
Proxy & routingYou’re tracing HTTP(S) routing (vhosts/upstreams).
DatabasesYou’re working on DB endpoints, connectivity, or ops.
CertificatesYou’re working on TLS trust, renewal, or certificate troubleshooting.
Middleware (runtimes)You’re mapping upstreams to app runtimes/containers.
Infra servicesYou need shared infra services (what/why/entry points).
Operate & TroubleshootYou want runbooks, monitoring, and operational procedures.
TroubleshootingYou want symptom-based entry points (DNS/VPN/TLS/proxy/DB).