Event delivery your auditors can sign off on
Send an event with one API call. Pingrail signs it, delivers it to every subscribed endpoint, retries with exponential backoff for up to 72 hours, and keeps a searchable log you can replay from.
Sending events in production at
- Tallyfox
- Brindle Pay
- Quillstack
- Orbitcart
- Ledgerline
- Nimbusly
Features
Everything your webhook queue should have had from day one
The boring, load-bearing parts of event delivery, built once and run for you.
Retries with backoff
Up to 12 attempts over 72 hours with jittered exponential backoff. Failed events land in a dead-letter queue, never on the floor.
Signed payloads
Every request carries an HMAC-SHA256 signature and timestamp. Rotate signing secrets with a 24-hour overlap and zero downtime.
Replay and debug log
Search 30 days of deliveries by event type, endpoint or status code. Inspect the exact request and response, then replay with one click.
Typed SDKs
Node, Python, Go, Ruby, PHP, Java, .NET and Rust. Event schemas generate types, so a renamed field fails your build, not your customer.
Regional endpoints
Send to us-east, us-west, eu-west, eu-central, ap-southeast or sa-east. Payloads stay in the region you pick.
Rate limits per endpoint
Cap delivery to 50 requests a second for a fragile customer server. We queue the rest and keep ordering per key.
Numbers we watch so you don't have to
- events delivered last month
- 2.1B
- uptime over 12 months
- 99.99%
- median delivery latency
- 38 ms
- delivery regions
- 6
How it works
From first event to production in an afternoon
No queue to run, no cron jobs, no retry table to migrate.
- 1
Send your events
Install the SDK and call send() wherever your app emits an event. Existing JSON payloads work as they are.
- 2
Set delivery rules
Pick a region, a retry policy and rate limits per endpoint. Defaults are sensible; every knob is optional.
- 3
Watch them land
Each delivery shows up in the log with status, latency and the response body. Replay anything that failed.
Testimonials
Engineers who stopped babysitting a queue
Sample reviews written for this template. Replace them with your own.
“A customer's endpoint was down for six hours over a weekend. Every event arrived when it came back, in order. I found out on Monday from the log.”
Grace LiuBackend Engineer“Signature verification took me ten minutes in Go. Our old setup had a shared secret nobody remembered how to rotate.”
Marcus BellPlatform Lead“Support can search the delivery log by customer ID and replay events themselves. That used to be an engineering ticket every day.”
Amara NwosuHead of Support“We needed EU data residency for a bank customer. Switching the workspace to eu-central was a dropdown, not a quarter.”
Jonas LindqvistCTO“The typed Python SDK caught a renamed field in CI before it reached 1,200 integrations. That alone paid for the year.”
Priya ShahSenior Developer“Per-endpoint rate limits saved us. One customer's tiny server kept falling over; now we cap them at 5 a second and move on.”
Kenji WatanabeSRE
Pricing
Pay for events, not for retries
Retries, replays and signature checks are always free. You only pay for events you send.
Hobby
For side projects and prototypes.
$0per month
Start free- 50,000 events / month
- 3 endpoints
- 7-day delivery log
- Community support
Scale
Most popularFor production apps with real customers.
$49per month
Choose Scale- 1M events included
- Unlimited endpoints
- 30-day log and replay
- Per-endpoint rate limits
- 99.99% uptime SLA
Enterprise
For regulated teams and high volume.
Customannual
Talk to sales- Volume pricing
- 90-day log retention
- SSO and SCIM
- Dedicated regions
- Named support engineer
Prices in USD, billed monthly. Overage on Scale is $20 per additional million events. Cancel any time.
FAQ
Questions from developers
Something missing? Email us; an engineer answers, usually within a few hours.
Contact supportWhat counts as an event?
One API call to send, regardless of how many endpoints it fans out to or how many retries it takes. An event delivered to five subscribers and retried twice is still one event on your bill.
How do retries work?
Any non-2xx response or a timeout after 30 seconds triggers a retry. The default schedule is 12 attempts over 72 hours with jittered exponential backoff. You can shorten it per endpoint, and after the last attempt the event moves to a dead-letter queue you can replay.
How do my customers verify payloads?
Each request includes a signature header with an HMAC-SHA256 of the timestamp and body. Every SDK ships a verify() helper, and the docs include copy-paste snippets for frameworks that don't have an SDK yet.
Where is my data stored, and for how long?
Payloads are stored in the region you choose when you create a workspace and are deleted when your log retention ends: 7, 30 or 90 days depending on plan. We never move data between regions.
We already have an in-house system. How do we migrate?
Most teams dual-send for a week: keep the old worker running, send the same events through Pingrail with delivery paused, compare the logs, then flip endpoints over one customer at a time. Our team will review your plan for free.
What happens if I go over my plan?
We never drop or throttle events because of billing. On Hobby we email you at 80% and 100% and ask you to upgrade; on Scale additional events are billed at $20 per million at the end of the month.
What does the SLA cover?
The 99.99% SLA covers the send API accepting events and our workers attempting delivery. If we miss it in a calendar month, you get service credits of 10 to 50% of that month's bill, applied automatically.
Can I cancel at any time?
Yes. Downgrade to Hobby or close the workspace from settings. Paid plans are billed monthly with no annual commitment, and you can export your delivery log as JSON before you go.