Request Inbox
Request Inbox is an open-source web application that lets developers self-host a free alternative to hosted webhook testing services by creating unique…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
59/100 Fair
- Maintained
- 82last commit 18 days ago
- Popular
- 176 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 100no serious findings, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed today
- GitHub stars
- 6
- Open issues
- 0
- Last commit
- 2026-11-02
- Latest release
- v1.2.0
- License
- Apache-2.0
- Activity
- declining
Checked yesterday - source: GitHub (jesusnoseq/request-inbox)
Resources & Compatibility
Requirements not published yet.
Checked yesterday - source: Docker Hub image tags and published docs
First-install notes
- Installation Request Inbox is a self-hosted web application; the repository README documents setup and self-hosting steps. source
Fetched yesterday - each note links to its source
Variants
Alternatives (2)
- Webhook.site - Webhook.site is a tool for building software that not only use webhooks but other types of communication, either by allowing developers to…
- webhookinbox.com
Checked yesterday - source: AlternativeTo
Common questions
Which ports does the Dockerized app use?
In the standard Docker setup, expose ports 80 and 8080 so the app is served at localhost. If using the development compose file, the API runs on port 8080 and the frontend runs on port 3000.
Where should I persist stored inbox data?
Mount a persistent volume at /app/data, such as a named volume like inbox-data, when running the Docker container.
How can users authenticate to a self-hosted instance?
Request Inbox supports user authentication with GitHub and Google OAuth. It also supports private inboxes and API keys for programmatic access.
Can I forward webhooks to another service when a request is captured?
Yes, it supports callbacks that call another service when a request lands, forwarding headers and templating the body. You can also resend a captured callback and inspect the new response.
Answers sourced from github.com
Community
No community discussions collected yet.