RequestBin

Best Self Hosted Alternatives to RequestBin

A curated collection of the 3 best self hosted alternatives to RequestBin.

SaaS webhook and HTTP request inspector that creates unique endpoints to capture, log, and display incoming HTTP requests and payloads for testing and debugging APIs and webhooks. Shows headers, bodies, query parameters, timestamps, and request metadata.

Alternatives List

#1
FlareSolverr

FlareSolverr

FlareSolverr is a proxy server with a REST API that uses a headless Chrome session to solve Cloudflare/DDoS-GUARD challenges and return HTML and cookies.

FlareSolverr is a lightweight HTTP API service that helps automate access to websites protected by Cloudflare and similar challenge pages. It launches a real browser on demand to solve the challenge, then returns the final page content and/or the resulting cookies for reuse.

Key Features

  • REST API for automated fetches that require solving Cloudflare or DDoS-GUARD challenges
  • Headless browser automation using Selenium with an “undetected” Chrome driver approach
  • Session management to reuse a browser profile and cookies across multiple requests
  • Supports upstream proxies (including authenticated proxies) for outbound requests
  • Can return full rendered HTML, response metadata, only cookies, or a rendered screenshot (Base64 PNG)
  • Designed for containerized operation with official Docker images

Use Cases

  • Integrating with automation tools (for example, indexers or scrapers) that need challenge-solving
  • Fetching cookies to use with other HTTP clients after the browser completes the challenge
  • Debugging challenge behavior by capturing rendered output or screenshots

Limitations and Considerations

  • Each request may launch a new browser instance unless sessions are used, which can be memory-intensive
  • Challenge-solving can fail or change over time as protection providers update their mechanisms

FlareSolverr is best suited for controlled automation scenarios where a real browser is required to pass anti-bot challenges. Used carefully with session reuse and sensible concurrency limits, it can provide reliable challenge handling behind a simple API.

12.2kstars
991forks
View Details
#2
Requestly

Requestly

Open-source API client and HTTP interceptor to test APIs, modify requests and responses, and create API mocks for faster development and debugging.

Requestly screenshot

Requestly is a local-first API client combined with an HTTP interceptor for capturing, inspecting, and modifying HTTP/HTTPS traffic. It helps developers test APIs, mock backend responses, and override network behavior from a browser extension or desktop app.

Key Features

  • REST API client with collections, environments/variables, and request history
  • HTTP interception and modification rules for requests and responses
  • URL redirects and rewrites (host, query params, map local/remote)
  • Modify request/response headers and bodies
  • Script injection and resource overriding for web pages
  • API mocking with static and dynamic overrides, including GraphQL targeting
  • Session recording for capturing and sharing relevant network traffic
  • Local workspaces stored on disk, with optional team sync workflows

Use Cases

  • Debug and test REST/GraphQL APIs with environment-specific variables
  • Mock backend APIs to unblock frontend development and E2E tests
  • Redirect traffic between staging/dev/prod endpoints and override scripts/resources

Limitations and Considerations

  • Some capabilities depend on where it runs (browser extension vs desktop app) and what traffic can be captured in that environment

Requestly is well-suited for developers who want a Postman-like API client combined with Charles/Fiddler-style interception. It provides practical tooling for request rewriting, API mocking, and repeatable debugging workflows without requiring heavy infrastructure.

6.1kstars
550forks
View Details
#3
Webhook Tester

Webhook Tester

Capture, inspect and debug webhooks and HTTP requests with customizable responses, real-time WebSocket UI, and memory/Redis/filesystem storage options.

Webhook Tester screenshot

Webhook Tester is a self-hosted application for receiving, inspecting and debugging HTTP requests and webhooks. It generates unique session URLs, records incoming requests, and provides a lightweight web UI with real-time notifications.

Key Features

  • Generate unique, randomly created session URLs to capture HTTP requests
  • Customize response code, headers, body and response delay for testing integrations
  • Built-in React-based UI compiled into the binary with WebSocket-driven real-time updates
  • Multiple storage drivers: memory (ephemeral), Redis (persistent / multi-instance), and filesystem (fs)
  • Pub/Sub drivers: memory and Redis to support real-time notifications across instances
  • Optional tunneling driver to expose local instances to the public internet (requires external tunnel auth)
  • Distributed-friendly: multi-architecture Docker images and single-binary releases; includes CLI and health endpoints
  • Binary view of recorded requests and configurable logging formats

Use Cases

  • Debug incoming webhook payloads from external services and inspect headers, bodies and timing
  • Test API integrations by simulating different response codes, headers and delays
  • Capture requests from CI, local development or remote services using a tunnel to a local instance

Limitations and Considerations

  • Default memory storage is ephemeral; use Redis or filesystem storage for persistence or multi-instance deployments
  • The tunneling feature relies on a third-party tunnel provider and requires an authentication token
  • README does not describe built-in access control or authentication; consider fronting with an auth/reverse proxy for public deployments

Webhook Tester is focused on low-oversight, high-performance request capture and inspection. It is suitable for development and staging environments and can be extended for more durable production use by enabling Redis or filesystem storage and adding external access controls.

367stars
43forks
View Details

Why choose an open source alternative?

  • •Data ownership: Keep your data on your own servers
  • •No vendor lock-in: Freedom to switch or modify at any time
  • •Cost savings: Reduce or eliminate subscription fees
  • •Transparency: Audit the code and know exactly what's running