Beeceptor vs Wilma

Beeceptor is a developer-focused API simulation platform for mocking services, virtualizing them, testing contracts, and simulating failures. It supports HTTP, HTTPS, HTTP/2, mTLS, REST/OpenAPI, SOAP, GraphQL, and gRPC. Users can build no-code mocks with request-matching rules and set response status codes, headers, and bodies. Uploading an OpenAPI specification can create a populated mock server with AI-generated data. Beeceptor can proxy requests to live backends, record traffic, and switch to mock behavior when a backend is unavailable. Latency, timeouts, and errors can be simulated to check client resilience. Its CLI exposes a localhost service through a public HTTPS URL and runs on Windows, macOS, and Linux. Management APIs support mock-server configuration, while MCP connectivity supports AI agents including Claude and Cursor. API Connections store OAuth credentials and generate tokens for outbound requests. Beeceptor says it is SOC 2 Type II audited, adheres to ISO 27001, and complies with GDPR; it also says data is encrypted in transit and at rest. The free plan has public endpoints, a 1 MB request payload limit, and cleanup rules for unclaimed endpoints.

Wilma is free, GPLv3-or-later software for developing and testing applications that depend on other services. It combines a service stub with an HTTP/HTTPS transparent proxy, allowing teams to capture, decode, save, and forward traffic, including two-way SSL, or generate configured responses. It can operate as a proxy, a stub, or both. JSON files define stub behavior, and configurations can be uploaded or changed through the interface or service while Wilma runs. Real-time interceptors can inspect or modify requests and responses; custom interceptors, condition checkers, and response formatters can be added, including through classes or JAR files. Message Search finds logged request-response pairs. Wilma supports unit, integration, functional, end-to-end, performance, and manual testing. It is available as Docker images, GitHub release ZIP files, or source builds. The application requires JRE 11, while Message Search requires JDK 11. Logging can be controlled and old logs deleted on schedules.