Fliq vs Trigger.dev
Trigger.dev is a powerful platform for durable background jobs and long-running workflows written as code in your own repo — with steps, waits, and full TypeScript ergonomics. Fliq solves a narrower, different problem: it schedules and fires HTTP requests to any URL, regardless of language or framework. They're complementary more than head-to-head — pick based on whether you want to author workflow code or just trigger existing endpoints.
| Dimension | Fliq | Trigger.dev |
|---|---|---|
| Scheduling model | Cron + one-off, calls any URL | Durable functions (your code) |
| Automatic retries | Configurable backoff, per-job | Per-step retries in code |
| Crash recovery | Reaper reschedules crashed jobs | Durable execution / checkpoints |
| Execution history | Full per-attempt history | Run & step traces |
| Calls any HTTP endpoint | Yes — any URL, method, headers, body | Via your task code |
| AI agents (MCP) | MCP server (beta) | No native MCP scheduler |
| Self-host | Yes (open source) | Yes (open source) |
| Open source | Yes | Yes |
| Pricing model | Free in beta, then $1/100k | Usage-based, free tier |
| Best for | Scheduling HTTP calls, any stack | Code-defined durable workflows |
When Fliq fits
You just need to call existing HTTP endpoints on a schedule — any language, any framework — without writing or deploying workflow code. Fliq schedules the request, retries on failure, recovers from crashes, and records every attempt, with an MCP server in beta for AI agents.
When Trigger.dev fits
Your jobs are multi-step workflows with logic, waits, retries between steps, and fan-out, and you want to write them as durable functions in TypeScript inside your codebase. Trigger.dev is built for exactly that.