Keploy

AI-powered test generation and record-replay testing tool. Keploy captures real API traffic and automatically generates integration tests + mocks/stubs from captured traffic. Uses eBPF for network-level traffic capture (no code changes needed). When re-run, Keploy replays the captured API calls against your application and mocks external dependencies. Designed to dramatically reduce the effort of writing integration tests for backend services.

Evaluated Mar 06, 2026 (0d ago) v2.x
Homepage ↗ Repo ↗ Developer Tools testing api-testing test-generation record-replay ebpf mocking open-source
⚙ Agent Friendliness
61
/ 100
Can an agent use this?
🔒 Security
84
/ 100
Is it safe for agents?
⚡ Reliability
65
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
--
Documentation
75
Error Messages
72
Auth Simplicity
95
Rate Limits
92

🔒 Security

TLS Enforcement
85
Auth Strength
88
Scope Granularity
85
Dep. Hygiene
80
Secret Handling
82

Apache 2.0 open source. Recorded traffic may contain sensitive data — test recordings must be sanitized before committing to git. eBPF-level access requires elevated privileges — run in isolated test environments only.

⚡ Reliability

Uptime/SLA
65
Version Stability
65
Breaking Changes
62
Error Recovery
68
AF Security Reliability

Best When

You want to generate integration tests from real traffic with minimal effort — especially for existing backend services that lack test coverage.

Avoid When

You need fine-grained control over test logic, front-end testing, or performance testing — specialized tools are more appropriate.

Use Cases

  • Generate integration tests automatically by recording real API traffic to your backend — no manual test writing for existing flows
  • Capture agent-to-service API calls in production and replay them in CI to ensure backend changes don't break existing agent integrations
  • Mock external service dependencies (databases, third-party APIs) automatically from recorded traffic for isolated testing
  • Test backend changes against real production traffic patterns without manually maintaining test fixtures
  • Generate regression test suites for AI agent backends by recording a diverse set of real interactions

Not For

  • Unit testing or front-end testing — Keploy focuses on API and integration testing at the network level
  • Teams needing manual, hand-crafted test scenarios with complex test logic — use Jest, Pytest, or Playwright for programmatic test control
  • Performance/load testing — Keploy captures functional correctness, not performance metrics

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
Yes
Webhooks
No

Authentication

Methods: none
OAuth: No Scopes: No

Keploy runs as a local CLI tool — no auth for local operation. Keploy Cloud (if applicable) uses account-based auth. No API keys for the open-source local version.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

Apache 2.0 open source, free for local development. Keploy Cloud adds team collaboration and AI-powered test enhancement. Core testing functionality is free.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Keploy uses eBPF for traffic capture — requires Linux with kernel 5.4+ and appropriate privileges (root or CAP_NET_ADMIN); not compatible with macOS in production mode
  • Recorded tests include timestamps and unique IDs from captured requests — replay failures can occur if your application validates timestamps or generates non-deterministic responses
  • External API mocks are generated from recorded responses — if external APIs return different data between record and replay (time-based, random data), tests fail with mismatch
  • gRPC support is limited compared to REST/HTTP support — verify gRPC compatibility for agent services using gRPC protocols
  • Database mocking captures SQL queries and responses — schema changes between record and replay cause mock mismatches; re-record after significant schema changes
  • Docker networking mode required for container-based services — Keploy must run in the same network namespace as the service being tested

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Keploy.

$99

Scores are editorial opinions as of 2026-03-06.

5208
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered