Fliq vs Inngest
Inngest is an event-driven platform for durable functions — you write steps in code, trigger them from events, and Inngest handles retries, concurrency, and flow control. Fliq is a focused HTTP scheduler: it fires cron and one-off requests at any URL, no workflow code required. The choice comes down to whether you're building event-driven function logic or simply scheduling HTTP calls.
| Dimension | Fliq | Inngest |
|---|---|---|
| Scheduling model | Cron + one-off, calls any URL | Event-driven durable functions |
| Automatic retries | Configurable backoff, per-job | Built-in step retries |
| Crash recovery | Reaper reschedules crashed jobs | Durable execution / replay |
| Execution history | Full per-attempt history | Function run history |
| Calls any HTTP endpoint | Yes — any URL, method, headers, body | Via your function code |
| AI agents (MCP) | MCP server (beta) | AgentKit (different scope) |
| Self-host | Yes (open source) | Yes (open source core) |
| Open source | Yes | Yes (core) |
| Pricing model | Free in beta, then $1/100k | Usage-based, free tier |
| Best for | Scheduling HTTP calls, any stack | Event-driven function workflows |
When Fliq fits
You don't want an event/function framework — you just need to schedule HTTP requests to existing endpoints, with retries, crash recovery, and per-attempt history, controllable by AI agents via MCP (beta), on a simple Postgres-native stack.
When Inngest fits
You're building event-driven workflows — fan-out, concurrency limits, debouncing, multi-step functions — and want to define them as code triggered by events. Inngest is purpose-built for that model.