From a mesh to
globally distributed delivery.

Changes enter through ingestion services and move through the mesh using event streaming. Services process those changes and can have their own local state, allowing them to combine data from multiple sources into a continuously updated representation.

Historical events are offloaded to S3 in Parquet format for retention and replay, providing a single source of truth for new services, replicas, and clusters.

StreamX Cloud uses GitOps to manage project-level changes, including mesh deployments and cloud configuration such as replica counts, domains, and cluster locations. It applies these changes across locations and coordinates rollouts so healthy instances can continue serving during updates. Teams and tenants define the organizational and access boundaries for operating meshes on the shared platform.

Zero trust networking secures communication between mesh services across locations through service identity, mutual TLS, and authorization policies. Network policies restrict workload connectivity, while internal networking and infrastructure-level isolation provide additional protection for critical data paths where available.

StreamX Cloud exposes materialized data and mesh services through API gateways deployed at the edge. These gateways route requests and enforce security controls, including rate limiting and authorization. Geo DNS directs traffic to a location serving the project, while custom domains and managed TLS certificates provide secure public endpoints.