Architecture

Full platform topology and how components connect.

High Level Topology

Internet
  |
  v
Public IP 5.39.37.7
  |
  v
Nginx reverse proxy
  |
  +-- /          -> cloud-dashboard container
  +-- /docs/     -> static documentation pages
  +-- /grafana/  -> Grafana container
  +-- /prometheus/ -> Prometheus container
  +-- /portainer/  -> Portainer container
  |
  +-- Future domain routes -> Kubernetes Ingress -> Services -> Pods

Component Responsibilities

Layer	Component	Responsibility
Network	Public IP	Receives external client traffic.
Edge	Nginx	Terminates HTTPS and reverse proxies requests.
Runtime	Docker	Runs isolated service containers.
Orchestration	Kubernetes	Future cluster for scaling and rolling updates.
Observability	Prometheus/Grafana	Collects and visualizes metrics.

Why This Architecture Is Production-Style

The design separates public entry, application runtime, monitoring and future orchestration. Nginx controls public exposure. Containers remain behind the proxy. Monitoring observes the system. Kubernetes can be added later when the host environment supports it.