Technical overview
The AstraCloudBox architecture separates transport, routing, cache behavior and operational checks so each part of the delivery path can be managed deliberately.
Architecture
Origins remain authoritative for content. The edge layer applies the configured delivery policy, maintains connection state and serves eligible cached responses.
A distributed edge design places delivery functions separately from the origin layer. The architecture supports public IPv4 connectivity and is prepared for IPv6-enabled service profiles. Upstream paths can be arranged redundantly where workload and deployment requirements justify it.
Client-facing delivery uses TLS with support for modern protocol versions. Origin connections can also use TLS, including hostname validation and certificate checks appropriate to the configured source.
Routing decisions are based on the requested hostname, delivery profile, origin health state and content policy. The service is designed to preserve predictable request handling rather than obscure origin behavior.
Availability practices include health-aware origin handling, separation of delivery roles and upstream redundancy where supported. No single design eliminates every failure mode, so maintenance state and active notices are published separately.
Changes are reviewed against the intended workload, cache behavior and transport requirements. Routine operations include reachability checks, configuration validation, capacity review and maintenance communication.
Protocol baseline
The exact profile depends on the workload, but the following characteristics define the common service baseline.
| Layer | Characteristic | Notes |
|---|---|---|
| Transport | TLS 1.2 and TLS 1.3 | Applied to compatible HTTPS delivery and configured secure origin connections. |
| Application | HTTP/2 | Negotiated with compatible clients through standard protocol selection. |
| Addressing | IPv4, IPv6-ready design | Address-family availability depends on the active service profile. |
| Content | Cache metadata | Cache eligibility and freshness can use explicit origin headers and configured policy. |
| Operations | Health monitoring | Reachability and service-state checks support maintenance and incident response. |
Security note. This overview intentionally omits addresses, host internals, private paths and deployment-specific configuration. Operational details are disclosed only when they are necessary for an approved service change.
