Bring Your Own Cloud
Speedscale Bring Your Own Cloud (BYOC) routes captured request and response pairs (RRPairs) to storage and observability systems in your cloud account. For named BYOC exporters, the Speedscale Forwarder sends captured traffic to an OpenTelemetry Collector that you operate. A separate customer-owned replay storage mode writes captures, replay inputs, and reports directly to your S3 or S3-compatible bucket.
Use BYOC when your organization needs to control where captured traffic is stored, apply its own retention and access policies, or connect traffic capture to an existing observability platform.
BYOC requires a Speedscale Enterprise plan. Contact support@speedscale.com to enable Forwarder BYOC exporters on your account.
Choose a path
| Goal | Start here |
|---|---|
| Understand the components and data boundaries | How BYOC works |
| Choose S3, GCS, Loki, Elasticsearch, Azure, or an observability backend | Storage and observability backends |
| Install BYOC on Kubernetes | Configure BYOC on Kubernetes |
| Confirm traffic reaches the destination | Verify a BYOC deployment |
| Pull stored traffic into a local workspace | Use BYOC traffic with proxymock |
| Deploy without Kubernetes | BYOC on ECS/Fargate |
| Diagnose missing traffic or connection failures | Troubleshooting |
What you operate
You operate the destination credentials, storage lifecycle, network policy, and access controls. Named BYOC exporters also require a collector that you operate. The direct S3 replay storage mode uses the public Speedscale Helm chart and does not require a collector for storage.
The direct S3 replay storage mode keeps captures and reports in customer-owned storage and does not request Speedscale-managed AWS credentials. It still needs the Speedscale API for account validation, Forwarder registration, and configuration. The exact network route and proxy authentication depend on your environment. Named BYOC exporters remain a separate option for observability destinations.
Typical workflow
- Choose a backend based on retention, query, and replay requirements.
- Configure the Forwarder and, for a named exporter, install its collector.
- Enable capture on a workload and verify each hop.
- Query traffic in the destination or import it into proxymock for analysis, mocking, and replay.
Related resources
Continue from the previous BYOC guide
The original single-page guide is now split by task. These compatibility anchors preserve its deep links and point to the new canonical pages.
- Architecture and transport: How BYOC works
- Reference architectures and Azure Blob: Storage and observability backends
- Prerequisites and installation: Configure BYOC on Kubernetes
- Deployment checks: Verify a BYOC deployment
- Replay and local use: Use BYOC traffic with proxymock