Keploy

What it is

Keploy generates test cases and mocks/stubs automatically by recording real API traffic (HTTP calls, database queries, gRPC) and replaying it as a regression test suite. It uses eBPF to capture traffic at the kernel level, meaning no code instrumentation or SDK integration is required in most cases. The pitch: turn production/staging traffic into a maintainable test suite instead of hand-writing unit and integration tests, and auto-generate mocks for downstream dependencies (DBs, third-party APIs) so tests run without live infra. Written in Go, ships as a CLI plus Docker/Kubernetes-native tooling.

Who builds it and why

Maintained by Keploy (the company) with a community of 123 contributors on GitHub. This isn't a side project — it's a commercial open-source play: the core recorder/replayer/mocking engine is open source (Apache-2.0), and the company presumably monetizes around it (hosted/enterprise features, though specifics aren't publicly confirmed here). Founding date and formal CNCF maturity level are not publicly available, so treat this as an independent OSS project rather than a graduated CNCF project until you verify otherwise.

Production readiness signal

17,865 GitHub stars and 123 contributors indicate real community traction, not a ghost project. Commit activity through mid-2026 and a release cadence reaching v3.5.84 suggest active, frequent iteration — version numbers this high on a relatively young-looking project usually mean rapid, incremental releases rather than long-lived major versions, which is worth noting if you need API/CLI stability guarantees. Go as the implementation language is a sane choice for a CLI/eBPF-adjacent tool. No CNCF maturity badge is confirmed, so don't assume graduated-project levels of governance, security audits, or vendor-neutral stewardship — verify directly with the maintainers before betting critical CI/CD pipelines on it long-term.

Who should use this

• Teams drowning in manual API/integration test maintenance who want tests derived from real traffic instead of written by hand.
• Backend teams working in Go, Node, Java, Python stacks with typical REST/gRPC + SQL/NoSQL dependency chains — the mocking layer is built for this shape.
• Teams wanting to increase test coverage on legacy services quickly without refactoring for testability.
• CI/CD pipelines where flaky, environment-dependent integration tests are a recurring pain point and deterministic mocks would help.

Who should NOT use this

• Teams with highly custom or exotic protocols outside HTTP/gRPC/common DB drivers — mock generation quality drops fast outside supported integrations.
• Organizations that require a CNCF-graduated or incubating project for compliance/procurement reasons — maturity status isn't confirmed here, so this may fail vendor-vetting checklists as-is.
• Teams that already have a mature, hand-curated contract/integration test suite (e.g., Pact-based) — replacing intentional, well-designed contract tests with traffic-derived ones can reduce test intent clarity.
• Anyone expecting this to replace unit testing or property-based testing — it's fundamentally about integration/API-level regression capture, not logic-level correctness.
• Shops uncomfortable running eBPF-based tooling in their environments (restricted kernels, hardened containers, some managed CI runners) — check compatibility before adopting broadly.

Alternatives

• Pact — consumer-driven contract testing; better fit if you want explicit, versioned contracts between services rather than traffic-derived tests.
• WireMock — mature, widely adopted HTTP mocking/stubbing tool; more manual setup but battle-tested and protocol-focused.
• VCR / VCR.py / go-vcr — record/replay HTTP interaction libraries integrated directly into test code; lighter-weight, language-specific alternative to Keploy's traffic-capture approach.

Pricing

Core Keploy (recording, replay, mocking, CLI) is fully open source under Apache-2.0 — no cost to self-host and run. Any paid/hosted enterprise tier offered by the company is not detailed in the data available here; check Keploy's official site/pricing page directly before assuming feature parity between OSS and any commercial offering.