Infrastructure — Cloudexa

01 Edge

Public edge

Traffic enters through Cloudflare and terminates TLS at the web server.

Internet

Public requests

Cloudflare DNS / proxy
TLS / HTTPS

Web Server online

Cloudexa control plane

nginx
cloudexa
hosting-router
cloudexa-worker-manager
Project storage service

02 Control

Orchestration

Cloudexa routes deployments to workers over Tailscale and tracks failover.

Cloudexa Infra

orchestration / routing

Deployment routing
Worker selection

Cloudexa HA

lease / health / failover

Lease management
Health checks
Failover

03 Workers

Docker workers

Application containers run on isolated Docker workers.

Worker 1 active

primary Docker worker

Project containers
Build execution

Worker 2 standby

failover Docker worker

Failover capacity

04 Storage

Persistent storage

Project source files live on NAS storage and are the deployment source.

Persistent Storage

project source files / NAS

Project directories
Uploaded sources

05 Data

Database services

Managed PostgreSQL and MySQL databases sit behind the database server.

Database Server

Azure · migration planned

PostgreSQL & MySQL

managed database engines

PostgreSQL :5432
MySQL :3306

pgAdmin

PostgreSQL web admin

pgadmin.cloudexa.dev

phpMyAdmin

MySQL web admin

phpmyadmin.cloudexa.dev

Connections

Public HTTPS: Internet to the web server through Cloudflare.
Control plane: Web server to Cloudexa Infra for orchestration and routing.
Tailscale worker link: Cloudexa Infra to Docker workers over the private Tailscale network.
HA / worker sync: Lease, health and failover coordination between the control plane and HA service.
Persistent storage: Project source files stored on the NAS and mounted by the deployment pipeline.
Database connection: Applications connect to PostgreSQL or MySQL through the database server.
Web administration: pgAdmin and phpMyAdmin provide browser access to the managed databases.