---
title: "BYOC Examples | Speedscale Docs"
description: "End-to-end BYOC deployment and traffic-reuse examples."
canonical: "https://docs.speedscale.com/byoc/examples/"
---

[Documentation index](https://docs.speedscale.com/byoc/llms.txt) | [Markdown](https://docs.speedscale.com/byoc/examples/index.md) | [Canonical page](https://docs.speedscale.com/byoc/examples/)

# BYOC Examples

Use these examples after reviewing [How BYOC works](https://docs.speedscale.com/byoc/how-it-works/) and the backend-specific prerequisites.

<a id="deployment-examples"></a>

## Deployment examples

*   [BYOC on ECS/Fargate](https://docs.speedscale.com/byoc/examples/ecs/) captures ECS application traffic and writes it to S3 with an OpenTelemetry collector and ECS task role.
*   [Kubernetes configuration](https://docs.speedscale.com/byoc/configure-kubernetes/) installs a reference collector and connects one or more named Forwarder exporters.

<a id="traffic-reuse-examples"></a>

## Traffic reuse examples

*   [Use BYOC traffic with proxymock](https://docs.speedscale.com/byoc/use-traffic/) imports S3 or GCS traffic through the CLI, MCP, or web interface.
*   [Export BYOC traffic to Locust](https://docs.speedscale.com/guides/integrations/export/locust/) turns imported inbound requests into a load test and links to a runnable Kubernetes scenario.
*   [Datadog export and trace correlation](https://docs.speedscale.com/guides/integrations/export/datadog/) connects captured traffic with APM data and includes a trace-to-proxymock workflow.

Each example names the boundary it validates. Treat synthetic validation results as functional checks, not capacity benchmarks.
