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. The Speedscale Forwarder sends the captured traffic to an OpenTelemetry Collector that you operate, and the collector writes to the destinations you choose.
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 collector, destination credentials, storage lifecycle, network policy, and access controls. Speedscale supplies the capture components, Forwarder exporters, public reference charts, and product updates.
BYOC export keeps captured RRPairs in destinations you control. It does not, by itself, make the Speedscale installation offline: account registration, configuration downloads, and operational telemetry can still use the Speedscale API. Configure the cloud exporter separately if captured RRPairs must not be sent to Speedscale Cloud.
Typical workflow
- Choose a backend based on retention, query, and replay requirements.
- Install its collector and configure the Forwarder.
- 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