webhookstorage is live
Source: Dev.to
Overview
webhookstorage is a lightweight service that receives webhook payloads that are too large for typical automation platforms, stores them in S3, and returns a signed link for on‑demand retrieval. The service is live, accepts traffic, and the free tier requires no credit card.
How It Works
- A webhook is sent to an ingest endpoint.
- The full payload is stored in S3 (KMS‑encrypted, per‑tenant key isolation).
- A lightweight JSON notification is sent to your automation tool containing:
- event ID
- endpoint ID
- payload size
- a presigned S3 download URL (expires in 15 minutes)
- Your workflow fetches the payload only when needed.
Features
- Single static IP (allow‑listable)
- Per‑endpoint secrets for authentication
- Signed S3 links with 15‑minute expiry
- Event trail for re‑fetching failed deliveries
- Up to 250 MB payload size per request
The Problem It Solves
Automation platforms such as Zapier, Make, and n8n impose request‑body limits (typically 5–16 MB). When a payload exceeds these limits, the platform may silently drop the webhook or return a vague error, leaving the sender unaware that the data was not delivered. Common work‑arounds—trimming fields, splitting requests, or polling later—add complexity and fragility.
webhookstorage separates transport from processing: accept the full payload once, store it durably, and provide a small reference for downstream consumption.
Pricing Plans
| Plan | Cost | Included Credits | Retention | Usage Limits |
|---|---|---|---|---|
| Free | $0 | — | 1 day | 5 webhooks/month |
| Activated | $25 one‑time activation (includes $25 credits) | $25 | 7 days | $0.03 per webhook + $0.10 per GB‑month after credits |
| Business | Custom | — | Custom | Custom limits, retention policies, and support |
All plans share the same endpoints, signed links, and static IP. No credit card is required for the free tier.
Technical Architecture
- Ingress: AWS Network Load Balancer with a fixed Elastic IP.
- Storage: S3 with KMS encryption; per‑tenant key isolation.
- Metadata: DynamoDB (timestamp, size, content‑type, sender IP).
- Notification: Small JSON payload sent to the configured outbound URL.
- Authentication: Per‑endpoint secret; secrets can be rotated without breaking existing traffic.
- Codebase:
- Frontend: Preact (zero runtime dependencies).
- Backend: SST v3 on AWS (Hono, Lambda, DynamoDB, S3).
- Auth: WorkOS AuthKit.
- Billing: Stripe metered billing.
Use Cases
- Automation builders whose Zapier/Make scenarios fail on large payloads.
- Ops teams needing a fixed IP and per‑endpoint authentication for webhook traffic.
- Agencies managing multiple clients, each with isolated webhook endpoints.
- Developers wanting to capture and inspect webhook payloads during development (free tier).
Roadmap
- Additional integration guides (e.g., Shopify, Zapier, Make, n8n).
- Webhook signature verification for more source providers.
- Per‑endpoint retention policy controls.
- Future features: event replay, payload transformation rules, CLI for local development.
Get Started
- Free tier: Sign up, receive an endpoint, and start sending test payloads (no payment required).
- Activated tier: One‑time $25 activation (includes $25 credits) and pay‑as‑you‑go thereafter.
- Business tier: Contact us to discuss custom limits and support.
Check out the integration guides and API documentation for detailed setup instructions.