WireMock Alternative — Hosted, No Java or Docker

Feature Comparison

When WireMock Still Wins

• Record-replay: WireMock can proxy a real backend and record responses for replay. Requex does not.
• Deep Java integration: Embedding WireMock inside JUnit/Spring tests keeps everything in-process.
• Self-hosted on private networks: Regulated environments where the mock cannot leave the VPC.
• Stateful scenarios: WireMock scenarios step through sequential states on repeated requests.
• Custom extensions: Java-based response transformers for complex logic.

When Requex.me Is the Better Choice

• Your team is not on the JVM and running a Docker container per dev is friction
• You need a mock URL a remote teammate or CI job can hit without network gymnastics
• Auth simulation is important — Bearer, HMAC, API key, Basic Auth all work without plugins
• You want conditional responses (return 429 when rate-limit header absent, 200 otherwise) without learning WireMock's matcher DSL
• You do not need record-replay and do not want to pay $49+/month for WireMock Cloud

Migrating WireMock Stubs to Requex

A WireMock stub like this:

{
  "request": {
    "method": "GET",
    "url": "/api/users/42",
    "headers": {
      "Authorization": { "matches": "Bearer .+" }
    }
  },
  "response": {
    "status": 200,
    "headers": { "Content-Type": "application/json" },
    "body": "{\"id\":42,\"name\":\"Alice\"}",
    "fixedDelayMilliseconds": 150
  }
}

Maps to Requex as:

• Route: GET /api/users/42
• Server auth: Bearer token
• Response: status 200, header Content-Type application/json, body {"id":42,"name":"Alice"}, delay 150

FAQ