Dimension Fliq Hookdeck
Trigger model Time-triggered: cron + one-off jobs Event-triggered: inbound webhook → delivery
Scheduling (cron / one-off) Yes — native No — events, not a clock
Outbound rate limiting Buffers: queue + rate-limited release Destination rate limits (Outpost)
Inbound webhook ingestion No — you call Fliq's API Yes — the core product
Automatic retries Configurable backoff, per-job Yes, with replay
Execution history Full per-attempt history Event & delivery logs
AI agents (MCP) MCP server (beta) No
Self-host Yes (open source) Outpost self-hostable; gateway managed
Open source Yes Outpost yes; platform proprietary
Pricing model Free in beta, then $1/100k Freemium, tiered by throughput
Best for Scheduled jobs + rate-limited outbound Inbound webhook infra & delivery

When Fliq fits

Your trigger is time, not an inbound event — cron schedules and one-off jobs — and you want to release outbound calls to a rate-limited API at a steady pace (buffers) without standing up Redis. Fliq is Postgres-native, open source, records every attempt, and exposes an MCP server (in beta) so AI agents can schedule and pace jobs.

When Hookdeck fits

Your work is driven by inbound events: you need to receive webhooks from Stripe, GitHub, or partners, verify and transform them, fan out, and deliver reliably with full observability. Hookdeck is purpose-built for that webhook-infrastructure job, and Outpost open-sources the outbound-delivery half.