Current architecture and planned extensions.
The request path, active services and the formula for each hosting account’s web limit.
The path of a request
All hosting accounts use one shared logical web cluster. Session, file and database services connect to this cluster; email follows a separate path.
Active services and planned extensions
The planned extensions below are not active yet.
Filer 01 is active. Filer 02 is a planned storage extension and is not active.
SQL Pool 01 is active. SQL Pool 02 is a planned database extension and is not active.
SQL Pool 01
ActiveFiler 02
Planned — not activeSQL Pool 02
Planned — not activeCurrent capacity reference
Each hosting account’s distributed limit is calculated from active web nodes and the configured limit on each one. Planned services are excluded from this calculation.
- Active web nodes
- 4 nodes
- Per-account ceiling on each node
- 4 vCPU / 8 GB
- CPU ceiling per hosting account
- 4 × 4 vCPU = 16 vCPU
- RAM ceiling per hosting account
- 4 × 8 GB = 32 GB
Shared resources, allocated dynamically according to load and the plan’s limits.
Services that grow independently
Each addition to web capacity triggers a new calculation of the plan’s limit. Storage, databases and email can evolve separately.