# proxymock overview

[Site index](https://docs.speedscale.com/llms.txt)

## Pages

- [Agent skills](https://docs.speedscale.com/proxymock/agent-skills/index.md): The agent skills Speedscale publishes for AI coding agents, what each one is for, and a prompt that installs them all.
- [Chapter 2: Deploy the demo app](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/deploy-the-demo-app/index.md): Your coding agent clones mock-lab, deploys the tutorial orders service and its Postgres into the cluster with kubectl apply -k, and checks it with the traffic Job.
- [Agent tutorial in your cluster: start here](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/index.md): A hands-on tutorial where your coding agent installs the Speedscale operator, records a demo workload in a Kubernetes cluster, and replays it there as a regression test and a load test, one pasted prompt per chapter.
- [Chapter 1: Install the operator](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/install-the-operator/index.md): Your coding agent uses the install-speedscale skill to install proxymock and the Speedscale operator, creating a local minikube cluster when you have none.
- [Chapter 7: Run a performance test](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/performance-test/index.md): Your coding agent load tests the tutorial-orders workload in the cluster with APP_SLOW=0 and APP_SLOW=1, with the CNCF API mocked and the real database, and finds the N+1 query that makes GET /orders slower.
- [Chapter 3: Record traffic](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/record-traffic/index.md): Your coding agent uses the record-traffic skill in cluster mode: it turns eBPF capture on for the tutorial-orders workload, runs the traffic Job, and pulls the inbound requests, CNCF API calls and Postgres queries into a recording named baseline.
- [Chapter 6: Run a regression test](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/regression-test/index.md): Your coding agent sets APP_VERSION=v2 on the tutorial-orders workload, replays the recording in the cluster with the tutorial test config, finds that total_cents became a string, and confirms the gate passes again on v1.
- [Chapter 4: Replay and tune the tests](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/replay-the-tests/index.md): Your coding agent replays the baseline recording against the tutorial-orders workload in the cluster with its dependencies mocked, reads what the regression verdict checks, and makes a test config that also checks value types.
- [Chapter 5: Tune the mocks](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/tune-the-mocks/index.md): Your coding agent uses the improve-mock-match-rate skill on the recording pulled from the cluster: it measures the mocks with the app on your machine, fixes a ts query parameter and order-dependent SQL reads, and confirms the fix with a replay in the cluster.
- [Chapter 8: Do it to your own workload](https://docs.speedscale.com/proxymock/agent-tutorial-cluster/your-own-workload/index.md): Your coding agent uses the quality-loop skill on a service it has not seen: it builds an image, deploys it, records it in the cluster, tunes the replay, and leaves a regression gate script that replays the recording in the cluster before every change.
- [Agent tutorial: start here](https://docs.speedscale.com/proxymock/agent-tutorial/index.md): A hands-on tutorial where your coding agent records a demo service with proxymock, tunes its mocks and tests, and runs a regression test and a performance test, one pasted prompt per chapter.
- [Chapter 1: Install proxymock](https://docs.speedscale.com/proxymock/agent-tutorial/install-proxymock/index.md): Your coding agent installs proxymock with the install-speedscale skill, connects the proxymock MCP server, and proves that record and mock work.
- [Chapter 7: Run a performance test](https://docs.speedscale.com/proxymock/agent-tutorial/performance-test/index.md): Your coding agent uses the proxymock-load-test skill to load-test the tutorial app with APP_SLOW=0 and APP_SLOW=1, with the CNCF API mocked and the real database, and finds the endpoint that got slower and why.
- [Chapter 3: Record traffic](https://docs.speedscale.com/proxymock/agent-tutorial/record-traffic/index.md): Your coding agent uses the record-traffic skill to record the tutorial app's inbound requests, its CNCF API calls and its Postgres queries into a recording named baseline.
- [Chapter 6: Run a regression test](https://docs.speedscale.com/proxymock/agent-tutorial/regression-test/index.md): Your coding agent uses the proxymock-regression-test skill to replay the baseline recording at a changed build of the tutorial app, explain what broke, and confirm the original build passes.
- [Chapter 2: Run the demo app](https://docs.speedscale.com/proxymock/agent-tutorial/run-the-demo-app/index.md): Your coding agent clones mock-lab, starts the tutorial app's Postgres with tutorial-db (no Docker), runs the app, and sends it the tutorial traffic once.
- [Chapter 4: Tune the mocks](https://docs.speedscale.com/proxymock/agent-tutorial/tune-the-mocks/index.md): Your coding agent uses the improve-mock-match-rate skill to replay the baseline recording with the app's dependencies mocked, mask a cache-busting query parameter, and key SQL reads so each one gets its own row.
- [Chapter 5: Tune the tests](https://docs.speedscale.com/proxymock/agent-tutorial/tune-the-tests/index.md): Your coding agent uses the tune-snapshot-replay skill to create a strict test config named tutorial, find the response fields that change on every run with proxymock drift, and ignore them until the replay passes.
- [Chapter 8: Do it to your own service](https://docs.speedscale.com/proxymock/agent-tutorial/your-own-service/index.md): Your coding agent uses the quality-loop skill to record a service it has not seen before, tune the replay and the mocks, and leave a regression test script you run before every change.
- [DynamoDB](https://docs.speedscale.com/proxymock/aws/dynamodb/index.md): Explore how to use Speedscale's pre-made DynamoDB mock for quick API testing, including importing, inspecting, and modifying request and response formats.
- [Mock AWS Services](https://docs.speedscale.com/proxymock/aws/index.md): Mock AWS services with Speedscale to easily record and replay traffic, utilizing pre-made mocks and detailed guides for seamless API testing.
- [AWS SES Mocking](https://docs.speedscale.com/proxymock/aws/ses/index.md): Mock AWS SES connections for local development using proxymock to test email functionality without sending real emails or incurring costs with Speedscale.
- [Export a SQL script](https://docs.speedscale.com/proxymock/databases/export-sql-script/index.md): Turn recorded PostgreSQL and MySQL traffic into a .sql script that psql or mysql can run: every executed statement in recorded order with its bound values filled in, from proxymock web, the Live SQL lens or the proxymock sql-script command.
- [Databases](https://docs.speedscale.com/proxymock/databases/index.md): Record your app's PostgreSQL and MySQL traffic with proxymock, then watch it live, inspect each statement with its bound values, link queries to the request that ran them, compare two runs, export runnable SQL, mock the database, and replay the traffic against a database.
- [Inspect a statement](https://docs.speedscale.com/proxymock/databases/inspect-a-statement/index.md): Open a recorded PostgreSQL or MySQL call in proxymock web to see the statement with its bound values, who ran it, how it ended or why it failed, the request that caused it, and every other call on the same database connection.
- [Link queries to the request that ran them](https://docs.speedscale.com/proxymock/databases/link-queries-to-requests/index.md): Tag your SQL with the request's W3C trace context (sqlcommenter, Rails query log tags, Datadog DBM) so proxymock links every recorded Postgres and MySQL statement to the exact request that ran it, even when requests overlap.
- [Load and Regression Test a Database](https://docs.speedscale.com/proxymock/databases/load-and-regression-testing/index.md): Record your app's real PostgreSQL or MySQL traffic once, then replay those exact statements to regression test a schema change or a database upgrade and to load test the database, from an AI coding assistant, the proxymock CLI or the Speedscale dashboard.
- [Mock a database](https://docs.speedscale.com/proxymock/databases/mock-a-database/index.md): Run your app against a mock of its PostgreSQL, MySQL, MongoDB or Redis database built from a proxymock recording, so tests and AI coding assistants run with no database at all.
- [MongoDB Mocking](https://docs.speedscale.com/proxymock/databases/record/mongodb/index.md): Mock MongoDB database connections and queries for local development using proxymock to record and replay real MongoDB wire protocol traffic.
- [MySQL Mocking](https://docs.speedscale.com/proxymock/databases/record/mysql/index.md): Mock MySQL database connections and queries for local development using proxymock to streamline your API testing and enhance your testing environment.
- [PostgreSQL Mocking](https://docs.speedscale.com/proxymock/databases/record/postgresql/index.md): Mock PostgreSQL database connections and queries for local development using proxymock with this comprehensive guide on recording and testing techniques.
- [Redis Mocking](https://docs.speedscale.com/proxymock/databases/record/redis/index.md): Capture Redis traffic and replay recorded RESP2 and RESP3 responses without a live Redis backend.
- [Compare SQL between runs](https://docs.speedscale.com/proxymock/databases/sql-compare/index.md): Record two releases of a MariaDB-backed app, then diff their database workloads in proxymock — new and removed statements, N+1 detection, latency regressions, schema changes, and DB-time shift by table — with no database access required.
- [SQL inventory and sql-report](https://docs.speedscale.com/proxymock/databases/sql-inventory/index.md): List every distinct SQL statement your app ran in a proxymock recording, busiest and slowest first, with rows, tables and the routes that ran it, and see how many statements each kind of request runs, which is where N+1 query loops show up.
- [Watch live SQL](https://docs.speedscale.com/proxymock/databases/watch-live-sql/index.md): Watch your app's PostgreSQL and MySQL statements arrive as proxymock records them, like a database profiler: filter them with templates, pause and clear, save what you caught as a recording, and copy it as runnable SQL.
- [FAQ](https://docs.speedscale.com/proxymock/getting-started/faq/index.md): Explore the FAQ for proxymock, covering supported protocols, Windows compatibility, differences from Speedscale Enterprise, and mock server functionality.
- [Help](https://docs.speedscale.com/proxymock/getting-started/help/index.md): Get help with proxymock by connecting on the Speedscale Slack or emailing support@speedscale.com for assistance with your API testing needs
- [Install proxymock CLI](https://docs.speedscale.com/proxymock/getting-started/installation/index.md): Install and initialize the proxymock command-line tool on macOS, Linux, or Windows to record traffic, mock dependencies, and replay tests.
- [Language Configuration](https://docs.speedscale.com/proxymock/getting-started/language-reference/index.md): Configure language-specific settings for proxymock to route traffic effectively without modifying application code, ensuring seamless API testing and traffic replay.
- [In-Cluster (Web)](https://docs.speedscale.com/proxymock/getting-started/quickstart/in-cluster/index.md): Use proxymock web to connect to your Kubernetes cluster, enable capture, and run replays in cluster with live results.
- [Live Tail (Web)](https://docs.speedscale.com/proxymock/getting-started/quickstart/live-tail/index.md): Stream live RRPairs from your cluster in proxymock web, view counters and logs, and pivot to captured requests.
- [Local Recording (Desktop)](https://docs.speedscale.com/proxymock/getting-started/quickstart/local/index.md): Record locally on your desktop using proxymock CLI or MCP, then inspect and replay in proxymock web.
- [proxymock CLI quickstart](https://docs.speedscale.com/proxymock/getting-started/quickstart/quickstart-cli/index.md): Record traffic, mock dependencies, and replay tests with the proxymock CLI using a demo Go app. Start locally, then choose CI/CD, Kubernetes, or cloud workflows.
- [Schema coverage and contract checks](https://docs.speedscale.com/proxymock/graphql/coverage-and-validate/index.md): Measure which GraphQL queries, mutations and response fields a proxymock recording reaches with proxymock coverage, and check every recorded response against the schema with proxymock validate: type, non-null, enum, missing and unselected fields, with exact JSON paths and CI exit codes.
- [Generate tests and mocks from a schema](https://docs.speedscale.com/proxymock/graphql/generate/index.md): Turn a GraphQL schema (SDL, an introspection result, or a running endpoint) into proxymock tests and mocks: one named operation per root query and mutation field, with synthesized variables and a response matching its selection.
- [GraphQL](https://docs.speedscale.com/proxymock/graphql/index.md): Record your app's GraphQL traffic with proxymock, then read each request as an operation, mock a GraphQL API, replay recorded operations as tests, generate tests and mocks from a schema, and measure a recording's coverage of the schema and its conformance to it.
- [Mock a GraphQL API](https://docs.speedscale.com/proxymock/graphql/mock-graphql/index.md): Run your app against a mock of the GraphQL API it calls, built from a proxymock recording: what a GraphQL mock matches on, why rotating variables miss, and how the Mocks view masks exactly those variables.
- [Record GraphQL traffic](https://docs.speedscale.com/proxymock/graphql/record/index.md): Record the GraphQL requests your server receives or your app sends with proxymock, see what each recorded call holds, how persisted queries and other request shapes are kept, and read every request as an operation in proxymock web.
- [Replay GraphQL operations](https://docs.speedscale.com/proxymock/graphql/replay/index.md): Replay recorded GraphQL operations at your server with proxymock as a regression test: results grouped by operation, GraphQL errors inside an HTTP 200 caught as body mismatches, and expired tokens in variables fixed with a semantic-path transform.
- [Generate tests and mocks from a .proto](https://docs.speedscale.com/proxymock/grpc/generate-from-a-proto/index.md): Turn a gRPC service's .proto file into proxymock tests and mocks, one per unary RPC, then record the service's real responses with them when no traffic has been recorded yet.
- [gRPC](https://docs.speedscale.com/proxymock/grpc/index.md): Record your gRPC services and their gRPC dependencies with proxymock, mock a dependency, generate tests and mocks from a .proto file, and check recorded responses against the .proto contract.
- [Mock a gRPC dependency](https://docs.speedscale.com/proxymock/grpc/mock-a-grpc-dependency/index.md): Answer your service's calls to a gRPC dependency from a proxymock recording, so tests and AI coding assistants run with no dependency, and fix calls the mock does not match.
- [Record gRPC traffic](https://docs.speedscale.com/proxymock/grpc/record/index.md): Record the gRPC calls your service receives and the gRPC calls it makes to its dependencies with proxymock, then read each recorded call as an editable file.
- [Native server streaming](https://docs.speedscale.com/proxymock/grpc/server-streaming/index.md): Record bounded native gRPC server streams, mock their paced responses and replay every message with explicit partial-call diagnostics.
- [Validate and measure coverage](https://docs.speedscale.com/proxymock/grpc/validate-and-coverage/index.md): Check recorded or replayed gRPC responses against the .proto message types with proxymock validate, and see which RPCs, status codes and response fields a recording reaches with proxymock coverage.
- [Create and Verify Blueprints](https://docs.speedscale.com/proxymock/guides/blueprints/index.md): Save reusable transforms in proxymock blueprints, preview their changes, and verify that their rules run during replay.
- [Export traffic to Bruno](https://docs.speedscale.com/proxymock/guides/bruno/index.md): Turn recorded HTTP traffic into a native Bruno OpenCollection with local files and explicit credential placeholders.
- [Choose What a Replay Tests](https://docs.speedscale.com/proxymock/guides/choose-replay-tests/index.md): Use a tests filter to choose which recorded traffic a replay sends as tests and which it serves as mocks, so traffic your app sent to a database or API can drive load or regression tests against that dependency.
- [CI/CD](https://docs.speedscale.com/proxymock/guides/cicd/index.md): Integrate proxymock into your CI/CD pipeline to enhance deployment confidence with automated traffic replay and testing before production release.
- [Replay a Speedscale Cloud Snapshot Locally](https://docs.speedscale.com/proxymock/guides/cloud-snapshot-local/index.md): Pull an existing Speedscale Cloud snapshot with proxymock, mock its dependencies, and replay its requests against an app on your laptop.
- [Work a Kubernetes Cluster with proxymock CLI](https://docs.speedscale.com/proxymock/guides/cluster/index.md): Use the proxymock cluster verbs to turn eBPF traffic capture on and off for a workload, run a recorded replay inside the cluster, and read topology, pod logs, and Kubernetes events, all from your kubeconfig. The same surface is available as the cluster MCP tool and the proxymock web Observability vi
- [Swap HTTP Basic Auth Credentials Between Environments](https://docs.speedscale.com/proxymock/guides/credentials-swap/index.md): Swap recorded HTTP Basic auth credentials for replay credentials using proxymock's one-click workflow, with cloud staging via S3 and end-to-end replay verification.
- [Datadog Synthetics](https://docs.speedscale.com/proxymock/guides/datadog-synthetics/index.md): Convert recorded proxymock traffic into a Datadog Synthetics test suite — one multistep API test per snapshot, with all auth headers redacted into global variables and automatic variable chaining between steps.
- [Docker](https://docs.speedscale.com/proxymock/guides/docker/index.md): Run proxymock with Docker to seamlessly integrate traffic recording and mocking for your applications running in local containers with easy configuration steps
- [Guides](https://docs.speedscale.com/proxymock/guides/index.md): Explore practical how-to guides for using proxymock effectively in your API testing and traffic replay scenarios.
- [Initialize API Key](https://docs.speedscale.com/proxymock/guides/initialize/index.md): Initialize your API key for proxymock by following simple command prompts, ensuring secure management with Speedscale for your development needs.
- [Java with proxymock](https://docs.speedscale.com/proxymock/guides/java/index.md): Record and mock Java traffic locally or in CI with HTTP proxies, SOCKS, port mappings, and JVM truststore settings.
- [Integration testing with Kiro and proxymock](https://docs.speedscale.com/proxymock/guides/kiro/index.md): Install proxymock in Kiro, review a testing spec, and verify recorded behavior with dependency mocks, evaluated assertions and native schema coverage.
- [Mocking LLM APIs](https://docs.speedscale.com/proxymock/guides/llm-simulation/index.md): Use proxymock to record and mock LLM API calls from OpenAI, Anthropic, Gemini, and other providers for zero-cost local development and CI testing.
- [Author DLP and Filter Rules Locally](https://docs.speedscale.com/proxymock/guides/local-rules/index.md): Build and test DLP redaction rules, traffic filters, and transforms against local RRPair files with no cloud, no API key, and no network. The rule is the same JSON document Speedscale Cloud uses, so it round-trips through cloud pull and push. Available as CLI verbs, MCP tools, and web editors.
- [Improve Mock Match Rate with AI](https://docs.speedscale.com/proxymock/guides/mock-match-rate/index.md): Use the improve-mock-match-rate skill and the proxymock MCP tuning tools to find why replayed requests miss their mocks and fix them until the match rate is 100%.
- [Modifying Tests/Mocks](https://docs.speedscale.com/proxymock/guides/modify-rrpairs/index.md): Modify tests and mock responses in proxymock recordings effortlessly with this guide, ensuring updates reflect in future test runs.
- [Topology and cluster visibility](https://docs.speedscale.com/proxymock/guides/observability/index.md): How proxymock web's Topology and Nodes tabs connect to a Speedscale cluster, and how the inspector-backed workload drawer and Resources views expose Kubernetes describe, events, logs, dependencies, ConfigMaps, Secrets, and Services for troubleshooting.
- [Generate Mocks from OpenAPI](https://docs.speedscale.com/proxymock/guides/openapi/index.md): Generate mocks from OpenAPI specifications using proxymock to create instant mock API responses for rapid testing and development.
- [Fix Replay Failures with Recommendations](https://docs.speedscale.com/proxymock/guides/recommendations/index.md): Fix replay failures with proxymock recommendations. proxymock detects values that change between runs — expired bearer tokens, dynamic cart/order/item IDs — and generates smart_replace blueprints that correlate the new value forward on every dependent request.
- [Debug a Replay Step by Step](https://docs.speedscale.com/proxymock/guides/replay-debugger/index.md): Park a proxymock replay before each recorded request, run to the first failure, and inspect what was sent and what came back, from the CLI, proxymock web, or an AI agent through MCP.
- [Choose Where a proxymock Replay Runs](https://docs.speedscale.com/proxymock/guides/replay-paths/index.md): proxymock can replay recorded traffic in three places: in-process on your machine, inside your Kubernetes cluster with no Speedscale cloud involved, or through Speedscale cloud like a dashboard replay. Compare the three and run each one from proxymock web, the CLI, or the MCP server.
- [Tune a Replay Locally](https://docs.speedscale.com/proxymock/guides/replay-tuning/index.md): Use mock-lab and the proxymock replay tuning script to measure replay misses and gate a match-rate threshold, offline and in CI.
- [Gate CI on Replay Results](https://docs.speedscale.com/proxymock/guides/replay-verdicts/index.md): Use proxymock replay verdicts, baseline regression gates, and fix verification to decide whether a CI run passes.
- [REST API for CI and scripts](https://docs.speedscale.com/proxymock/guides/rest-api/index.md): Drive proxymock from CI jobs and scripts over a stable, versioned REST API: pull snapshots, run the mock server, replay traffic and fail the build on the result.
- [Secrets](https://docs.speedscale.com/proxymock/guides/secrets/index.md): Use the ${{secret:name/key}} syntax to inject sensitive values like database credentials, JWT signing keys, and API tokens into proxymock transforms without storing them in your recording.
- [Compare Response Meaning](https://docs.speedscale.com/proxymock/guides/semantic-comparison/index.md): Configure semantic response comparison in proxymock with explicit similarity thresholds and optional model judging.
- [Explore and Replay Sessions Locally](https://docs.speedscale.com/proxymock/guides/sessions/index.md): Group recorded traffic by actor in proxymock web, walk each user's journey, export one session as a standalone snapshot, and replay it back against your app — with the mock-lab demo, entirely on your desktop.
- [Configure a Replay with Test Configs](https://docs.speedscale.com/proxymock/guides/test-configs/index.md): A proxymock test config sets how a replay runs: load stages, responder replicas and resources, chaos, and more. Test configs are JSON files in your workspace at proxymock/testconfigs/.json. Author them in the proxymock web editor, the CLI or the MCP server, and use one on a local, in-cluster or Spee
- [Trace a request without traces](https://docs.speedscale.com/proxymock/guides/trace-without-traces/index.md): Follow one customer's request across every service it touches in proxymock web — with no trace IDs, no OpenTelemetry, and no code changes — by filtering recorded traffic on a business identifier (an email) and reading the trace waterfall.
- [Architecture](https://docs.speedscale.com/proxymock/how-it-works/architecture/index.md): Explore the architecture of proxymock to understand how it captures and replays traffic for API testing without modifying your application setup
- [proxymock CLI overview](https://docs.speedscale.com/proxymock/how-it-works/cli/index.md): Learn the proxymock CLI workflow for recording traffic, mocking dependencies, and replaying tests, with links to installation, quickstart, and command reference.
- [Data and Privacy](https://docs.speedscale.com/proxymock/how-it-works/data_and_privacy/index.md): Ensure data security and privacy with proxymock, which handles your data responsibly and complies with strict best practices during API testing.
- [How it works](https://docs.speedscale.com/proxymock/how-it-works/index.md): Discover how proxymock captures real traffic through a proxy to create automated mocks and tests without changing your application code.
- [Lifecycle](https://docs.speedscale.com/proxymock/how-it-works/lifecycle/index.md): Explore the Lifecycle of proxymock to learn how to record, replay, and manage traffic for effective API testing and mocking with Speedscale.
- [MCP Tools & Prompts Reference](https://docs.speedscale.com/proxymock/how-it-works/mcp-tools/index.md): Reference for every tool, prompt, and resource the proxymock MCP server exposes to AI coding assistants.
- [Model Context Protocol (MCP)](https://docs.speedscale.com/proxymock/how-it-works/mcp/index.md): Explore the Model Context Protocol (MCP) for proxymock to enable seamless integration with AI tools and enhance your API testing and mocking capabilities.
- [REST API Reference](https://docs.speedscale.com/proxymock/how-it-works/rest-api-reference/index.md): Every stable operation of the proxymock REST API, its request fields and its result, generated from the OpenAPI document.
- [Markdown Format Specification](https://docs.speedscale.com/proxymock/how-it-works/rrpair-format/index.md): Explore the RRPair markdown format in proxymock for recording and replaying API traffic with Speedscale, ensuring human readability and easy debugging.
- [Signature Matching](https://docs.speedscale.com/proxymock/how-it-works/signature/index.md): Implement signature matching with proxymock to create realistic service mocks that accurately simulate external APIs and databases for your testing environment
- [Workspace Layout](https://docs.speedscale.com/proxymock/how-it-works/workspace-layout/index.md): Reference for the proxymock workspace directory layout — what each directory holds, when it is created, and what is safe to delete or gitignore.
- [proxymock overview](https://docs.speedscale.com/proxymock/index.md): Use proxymock CLI, web, or MCP to record traffic, mock dependencies, and replay tests locally, in Kubernetes, or through Speedscale Cloud.
- [Kafka consumer-group health and kafka-report](https://docs.speedscale.com/proxymock/kafka/consumer-group-health/index.md): Report how your app's Kafka consumer groups behaved in a proxymock recording or a Speedscale snapshot: members, rebalances, per-partition lag and commit lag, and findings for consumer lag, stuck partitions, poll timeouts, offset resets and repeated rebalances, with no broker access.
- [Kafka](https://docs.speedscale.com/proxymock/kafka/index.md): Record your app's Kafka producer and consumer traffic with proxymock, then read it record by record, check the health of its consumer groups, run the app against a mock broker, and replay the recorded records into a real broker to test a consumer or a producer.
- [Mock a Kafka broker](https://docs.speedscale.com/proxymock/kafka/mock-kafka/index.md): Run a Kafka producer or consumer against a mock broker built from a proxymock recording: producers get their acknowledgements, consumers join their group and read the recorded records, and no broker has to run.
- [Record Kafka traffic](https://docs.speedscale.com/proxymock/kafka/record/index.md): Record a Kafka producer or consumer with proxymock: give the broker a listener that advertises proxymock's port so every call goes through it, map that port with --map, and read what each recorded call holds.
- [Replay Kafka traffic](https://docs.speedscale.com/proxymock/kafka/replay/index.md): Test a Kafka consumer by replaying the records it read into a real broker, with their original keys, partitions, timestamps and compression, or replay a producer's output, with proxymock replay and --tests-filter.