Enterprise-grade webhook delivery, billed purely by usage.
Herosite verifies Meta signatures and forwards every webhook to your destinations — at just $10/GB total traffic (in + out), postpaid, with zero prepaid lock-in. Pay only for the traffic you actually move.
Overview
Pro PlanEgress Used
0.24 GB
Ingress Used
0.24 GB
Projected Cost
$0.25
Active Projects
3
Active relay streams
Acme Main Relay
/webhook/acme-main
Nova App Relay
/webhook/nova-app
Overdue Corp Relay
/webhook/overdue-relay
Meta Relay
One callback URL per project. Herosite verifies the Meta signature, stores a receipt, and forwards the raw payload to up to five configured destinations.
Open Meta RelayPostpaid Billing
Usage-based invoicing measured in GB of egress. Invoices appear in your dashboard with a one-click pay option and a built-in grace period.
See pricingOne Meta callback, many downstream systems.
Create a relay project and Herosite hands you a single callback URL like https://5xgarkvobr49xr3o6zedhtnv.server.contabo.eu.skyfree.org.in/webhook/your-project. Meta verifies it once; Herosite validates every signature and forwards the raw payload to up to five destinations.
$ curl -X GET "https://herosite.win/webhook/meta-acme?hub.mode=subscribe&hub.verify_token=…"
→ Verify token OK ✓
→ 200 OK echo: challenge-abc-123
→ POST signature X-Hub-Signature-256 validated
→ Forward raw body to destination 1..5 200 OK
Receipt stored in shared event DB · usage metered
Answers to the full webhook ticket
?If I add both webhook URLs as destinations, does every event go to both?
Yes. Herosite currently forwards the same payload to every destination configured on that relay project.
?Do you support conditional routing by phone_number_id, display_phone_number, or WABA ID?
Not in this product yet. Conditional routing is not implemented in the MVP.
?Can I map phone number IDs to different destinations?
No. There is no mapping table in this version. Configuration is project-wide.
?How does verify token work?
Meta verifies Herosite's callback URL with the verify token you enter for the project. Destination URLs are not part of Meta's GET verification.
?Do you require Meta App Secret and preserve X-Hub-Signature-256?
Yes. Herosite validates incoming signatures with the project's App Secret and forwards the original request headers except transport headers that must be regenerated.
?Is the raw payload modified?
No. Herosite forwards the raw request body unchanged.
?Retry and replay support?
Failed deliveries are retried automatically (up to 5 attempts), deliveries interrupted by a restart resume on startup, and you can replay a failed delivery from the logs while its payload is still stored (7 days on Free, 30 days on paid plans).
?What logs can we see?
The dashboard shows webhook receipts, payload preview, destination URLs, response status codes, and failure messages.
?Do you store webhook payloads?
Payloads are stored only so you can debug and review deliveries. They are deleted automatically after 7 days on Free and 30 days on paid plans. Delivery counts and traffic totals are kept for billing.
?Should two isolated platforms use Herosite?
Use it only if both platforms are allowed to receive the same payload and safely ignore unrelated events. Strict isolation needs a routing product, not this relay.
?How will I manage the webhook and billing dashboard?
Create an account, open the dashboard, create a relay project, and manage billing through the Stripe buttons in the same dashboard.
?How many destinations can a single webhook event reach?
The destination limit follows your plan (Free: 2, Starter: 3, Pro: up to 5), and a webhook is currently dispatched to at most 5 destinations in parallel. Enterprise can raise this on request.
Start free, pay a flat price to grow.
Every plan includes monthly traffic. Starter and Pro keep forwarding past it and bill the extra to your saved card; Free stops at its limit.
Free
HobbyTry the relay with a small monthly limit.
- 7-day payload and log history
- 100 MB forwarded traffic per month (about 26,000 events)
- 1 Relay Project
- Up to 2 destinations per webhook
- Community support
Starter
For small setupsMore projects and a higher monthly limit.
- 30-day payload and log history
- 2 GB forwarded traffic per month (about 350,000 events)
- Keeps forwarding past the limit: extra traffic is billed at $1.00/GB to your saved card
- 5 Relay Projects
- Up to 3 destinations per webhook
- Flat monthly price
Pro
Most popularFor agencies and production workloads.
- 30-day payload and log history
- 5 GB forwarded traffic per month (about 520,000 events)
- Keeps forwarding past the limit: extra traffic is billed at $1.00/GB to your saved card
- Unlimited Relay Projects
- Up to 5 destinations per webhook
- Flat monthly price
Enterprise
CustomFor high volume and enterprise.
- Volume discounted rate
- 30-day payload and log history
- Unlimited Relay Projects
- Unlimited destinations per webhook
- Priority support
- Dedicated account manager