Infrastructure services with clear operational scope

Edge Delivery receives standards-based HTTPS requests and serves eligible content from the delivery layer. Cache policy, content type and origin behavior remain explicit so delivery decisions can be reviewed and adjusted without changing application code.

• TLS delivery
• HTTP/2
• Cache policy
• Origin retrieval

Static Content Delivery is intended for assets that benefit from stable paths and predictable cache metadata: images, scripts, stylesheets, documents, release files and other downloadable resources. Content headers are preserved or normalized according to the selected delivery profile.

• Images
• Documents
• Application assets
• Downloads

Object Storage organizes content around durable object names, content types and delivery metadata. It is suitable for static asset repositories, release artifacts and file collections that do not require a server-side application runtime.

• Object paths
• Metadata
• Content types
• Static files

Origin Connectivity defines how delivery services reach customer-controlled content sources. Profiles can account for transport security, hostname validation, request headers, reachability checks and controlled response handling.

• Origin TLS
• Hostname validation
• Health state
• Request controls

Infrastructure Monitoring provides operational signals for reachability, delivery health and maintenance state. Checks are kept separate from customer application logic and are interpreted alongside configuration changes and upstream conditions.

• Reachability
• Health checks
• Service notices
• Maintenance state