keploy
Keploy is an open-source API and integration testing platform that automatically generates tests and mocks by recording real traffic at the network layer using eBPF. It works language-agnostic and can capture database queries, streaming events, and external API calls to create deterministic offline test suites.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | keploy/keploy |
| Owner | keploy |
| Primary language | Go |
| License | Apache-2.0 — OSI-approved |
| Stars | 18k |
| Forks | 2.3k |
| Open issues | 679 |
| Latest release | v3.5.84 (2026-07-01) |
| Last updated | 2026-07-08 |
| Source | https://github.com/keploy/keploy |
What keploy is
Go-based tool that uses eBPF for kernel-level traffic interception to record and replay API flows, database interactions (Postgres, MySQL, MongoDB), and message queues (Kafka, RabbitMQ) as executable test cases. Supports statement, branch, and API schema coverage analysis with AI-assisted test expansion.
Get the keploy source
Clone the repository and explore it locally.
git clone https://github.com/keploy/keploy.gitcd keploy# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- eBPF requires Linux kernel support (typically kernel 4.15+); verify host kernel version and container runtime compatibility before production rollout.
- Record-replay workflow requires capturing representative user flows; plan data collection strategy to ensure captured scenarios cover critical paths and edge cases.
- Time-freezing feature used for deterministic replay—verify system clock handling does not conflict with time-sensitive application logic or external integrations.
- Mock registry and cloud features mentioned but availability, SLA, and pricing in enterprise context require clarification with vendor.
- Language and protocol coverage is broad but some proprietary protocol parsings noted as non-open-source; review dependency list for your stack before commitment.
When to avoid it — and what to weigh
- Unit Test Replacement Need — Keploy focuses on API, integration, and E2E testing—not unit test generation. If your primary need is fine-grained unit test creation, consider tools like Pex or Diffblue.
- Strict Sandbox Isolation Required — Keploy uses eBPF and network interception; teams requiring air-gapped or strictly isolated sandboxes may face deployment constraints in hardened environments.
- Minimal Infrastructure or CI/CD Overhead Budgets — eBPF interception, time-freezing, and mock registry features add operational overhead. Organizations with tight resource constraints should evaluate trade-offs.
- Legacy Windows-First Shop — eBPF is primarily Linux-based. Windows deployments may have limited or no eBPF support, requiring evaluation of workarounds.
License & commercial use
Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved license allowing commercial use, modification, and distribution with attribution and liability disclaimer.
Apache-2.0 permits commercial use without royalty or vendor lock-in. However, cloud features (mock registry, time-freezing, console) may have separate commercial terms not covered by the license. Review vendor's enterprise offerings for clarification on SLAs, support, and hosted service terms.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
eBPF operates at kernel level—verify that process privileges, SELinux/AppArmor policies, and container capabilities align with security posture. Network traffic capture and mock replay could expose sensitive data (API keys, PII); ensure recorded traffic is encrypted, access-controlled, and compliant with data retention policies. Vendor security audits, vulnerability disclosure policy, and data handling for hosted cloud features require review. No exploit details or threat model provided in source data.
Alternatives to consider
Postman + Newman
Lower operational overhead for API testing; requires manual test authoring but no kernel-level interception or infrastructure virtualization. Better for smaller, simpler test suites.
VCR.py / Betamax
Language-specific HTTP record-replay libraries; simpler setup but limited to HTTP mocking and lack distributed infrastructure support (databases, queues). Suitable for single-service testing.
Wiremock / Mountebank
Standalone mock servers offering HTTP/gRPC stubbing with no infrastructure recording; more manual configuration but no eBPF dependency and easier Windows deployment.
Build on keploy with DEV.co software developers
Evaluate Keploy's record-replay and infrastructure virtualization capabilities for your team. Review kernel requirements, cloud feature terms, and CI/CD integration fit before pilot deployment.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
keploy FAQ
Do I need to modify application code to use Keploy?
What happens if my Linux kernel does not support eBPF?
Can Keploy replace all my existing tests?
What is included in the Apache-2.0 license vs. enterprise/cloud offerings?
Software development & web development with DEV.co
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If keploy is part of your open-source testing roadmap, our team can implement, customize, migrate, and maintain it.
Ready to automate your API testing?
Evaluate Keploy's record-replay and infrastructure virtualization capabilities for your team. Review kernel requirements, cloud feature terms, and CI/CD integration fit before pilot deployment.