---
title: "Evaluation prerequisites and plan | Speedscale Docs"
description: "Prepare a Speedscale evaluation with a short readiness checklist, agreed success criteria, and a sample three-week plan."
canonical: "https://docs.speedscale.com/getting-started/evaluation/"
---

[Documentation index](https://docs.speedscale.com/getting-started/llms.txt) | [Markdown](https://docs.speedscale.com/getting-started/evaluation/index.md) | [Canonical page](https://docs.speedscale.com/getting-started/evaluation/)

# Evaluation prerequisites and plan

Evaluate Speedscale with one service to assess replay accuracy and performance in your environment. Agree on scope and success criteria with your account team before kickoff.

<a id="before-kickoff"></a>

## Before kickoff

*   **Service and traffic:** choose the service, endpoints and dependencies. Prepare representative requests, including authenticated flows and error cases. Test or UAT traffic is sufficient to start.
*   **Test environment:** provide a non-production deployment, test credentials, seed data and capacity for the agreed load. Identify which dependencies will be mocked or remain live.
*   **Owners:** name an application owner and a platform contact for installation and network access.
*   **Data handling:** agree on fields to redact, storage location, access and retention before capture. See [Data Loss Prevention](https://docs.speedscale.com/guides/dlp/).
*   **Access:** arrange Speedscale access, installation permissions and the required binaries or container images.

<a id="installation-requirements"></a>

## Installation requirements

| Environment | Prepare |
| --- | --- |
| Kubernetes, classic operator | Configure an API key and follow the [Quick Start](https://docs.speedscale.com/getting-started/quick-start/). Approve [RBAC and webhook access](https://docs.speedscale.com/security/kubernetes-permissions/) and confirm [eBPF compatibility](https://docs.speedscale.com/reference/ebpf-traffic-collection/), or agree on sidecar capture. |
| Kubernetes, namespace-only | For Deployment or StatefulSet targets, follow the [namespaced guide](https://docs.speedscale.com/getting-started/installation/install/kubernetes-namespaced/). Pre-provision the namespace and required Secrets, including the API key. Approve sidecar Pod Security exceptions and, on OpenShift, an SCC grant. eBPF is unavailable. |
| Local service | Install [proxymock](https://docs.speedscale.com/proxymock/getting-started/installation/) and activate through browser sign-in. Use an API key for headless runs. Confirm proxy routing and TLS trust; Kubernetes is optional. |
| VM or Docker | Configure an API key and review the [VM](https://docs.speedscale.com/getting-started/installation/install/vm/) or [Docker](https://docs.speedscale.com/getting-started/installation/install/docker/) guide. |

Confirm [network access](https://docs.speedscale.com/reference/networking/) for your deployment, including outbound cloud connections and TCP 9443 webhook access for the classic operator. If captured traffic must stay in customer-controlled storage, review [BYOC](https://docs.speedscale.com/byoc/). It requires Enterprise enablement and still needs Speedscale API connectivity.

<a id="success-criteria"></a>

## Success criteria

Agree on response-match accuracy, request rate or concurrency, test duration, error limits and p95/p99 latency targets. Confirm capture coverage, data redaction and which dependencies must be isolated. Assess results in [Cloud replay reports](https://docs.speedscale.com/guides/reports/) or [local proxymock replay results](https://docs.speedscale.com/proxymock/guides/replay-verdicts/), and verify detection of one controlled regression.

Load tests with mocked dependencies measure the service under controlled conditions, rather than the capacity of live downstream systems.

<a id="sample-evaluation-plan"></a>

## Sample evaluation plan

| Stage | Outcome |
| --- | --- |
| Week 1: install and capture | Verify installation, representative traffic coverage and agreed data redaction. |
| Week 2: establish a baseline | Create a reusable recording or snapshot, configure dependency mocks and obtain a baseline replay that meets the agreed response comparisons. |
| Week 3: test and review | Run the agreed load, compare latency and errors, demonstrate regression detection and review results together. |

Agree on dates once approvals, traffic and the application are ready. Share this checklist with your account team, or contact [support@speedscale.com](mailto:support@speedscale.com).
