Centrali vs Hookdeck
Both offer webhook reliability at scale, but they solve different problems — delivery vs. data integration.
Centrali
Centrali stores webhook events as queryable records that become part of your backend data. Query them, join them with orders or users, and keep them indefinitely. Functions react to events, and outbound webhooks deliver with HMAC signing and configurable retries — all without leaving your backend.
Hookdeck
Hookdeck is an event gateway that routes webhook requests from sources to destinations with reliability built-in. It offers up to 50 automatic retries with configurable backoff, dead-letter handling via Issues, and monitoring dashboards. SOC 2 Type II certified.
Feature Comparison
| Feature | Centrali | Hookdeck |
|---|---|---|
| Compliance & Security | No SOC 2 Does not hold SOC 2 Type II, HIPAA, or PCI-DSS certification | SOC 2 Type II only SOC 2 Type II certified; GDPR, CCPA, PIPEDA compliant (no HIPAA or PCI-DSS) |
| Event Storage Model | Queryable records Events stored in your collections as queryable data, joinable with other records | Request/delivery logs Stores HTTP requests and delivery attempts for 3–30 days; primarily for monitoring |
| Retention Policy | Indefinite Keep webhook events permanently for compliance, auditing, or historical queries | 3–30 days Retention depends on plan tier; Developer (3d), Team/Growth (7-30d) |
| Retry Configuration | Flexible 1–20 attempts, exponential or fixed backoff, up to 7 days; per-subscription | Very flexible Up to 50 automatic retries, linear or exponential backoff, Retry-After header support |
| Dead-Letter Handling | DLQ with reasons Failed deliveries tagged with reason (max attempts or window expired), queryable and replayable | Issues (DLQ) Failed events tracked as Issues; can be replayed or discarded from dashboard |
| Inbound Webhook Verification | Provider presets Built-in presets for Stripe, GitHub, Shopify, Slack, or raw HMAC configuration | Manual inspection Request logs include headers and payloads; you verify independently |
| Serverless Functions | Built-in JavaScript functions react to webhook events; no separate job queue needed | Not included Hookdeck routes and monitors; you handle processing in your application |
| Queryability | Full platform query Saved queries, joins, text search, and filters on webhook events from your backend | Dashboard views View requests/events in Hookdeck console; API available for read-only access |
| Deduplication | Webhook filters Filter inbound webhooks by event type, collection, or payload predicates | Built-in Automatic deduplication based on matching strategies configured per source |
| Pricing Model | Usage-based Pay for platform operations and storage; webhooks are integral | Event-based Developer free (10k/mo), Team $39/mo, Growth $499/mo; pay-as-you-go for overage |
Which should you choose?
Choose Centrali if you...
- Webhook events need to become persistent, queryable business data — not just delivery notifications
- You want to run functions (transformations, validation, workflows) on webhook events without extra tooling
- Historical webhook data is critical for reconciliation, auditing, or fraud detection beyond your sender's retention window
- You're building a complete backend where webhooks integrate into your data model
Choose Hookdeck if you...
- Your primary goal is reliable delivery to existing endpoints, not storing events as data
- You need a thin, specialized event routing layer separate from your backend
- You use multiple webhook sources and want a centralized monitoring dashboard
- Integration with 3rd-party SaaS tools or existing systems is sufficient for your use case
Migrating from Hookdeck
Export request history and mapping from Hookdeck (retention window closes at 3–30 days depending on plan)
Create a Centrali collection schema matching your webhook payload structure
Bulk import historical requests into Centrali (if needed for audit trail)
Update all webhook source endpoints to point to your new Centrali webhook trigger URL
Set up inbound webhook signature verification using Centrali's provider presets or raw configuration
Move Hookdeck's event routing and deduplication logic into Centrali functions or workflow automation
Configure outbound webhook subscriptions in Centrali if you were using Hookdeck to deliver to downstream systems
Validate end-to-end: send a test webhook and verify it lands in your Centrali collection with full provenance
Ready to try Centrali?
Start building with a unified backend. No credit card required.