What is Fliq?

Fliq is a serverless HTTP workflow platform. You give it a URL and a time — it fires the request, retries on failure, and keeps a full execution history.

The problem it solves

Most backend applications eventually need to do something at a specific time: send a reminder 24 hours after signup, charge a card on a contract start date, sync data every hour. The usual answers — cron jobs, worker queues, background threads — all require infrastructure to run, monitor, and recover from failures.

Fliq replaces that entire layer with a single API call. You POST a job, we handle delivery, retries, and logging.

Core concepts

Job

A one-time HTTP request fired at a specific moment. You provide a url, an optional http_method, a scheduled_at timestamp, and optionally headers, a body, and a retry limit.

Schedule

A recurring rule that creates a new job execution at each interval. Schedules use standard 5-part cron expressions (0 9 * * 1-5 = 9 AM every weekday).

Execution

Each HTTP attempt — the original fire or a retry — is one execution. Executions are logged with the HTTP status code, response time, and any error. Every execution counts toward your billing usage.

How Fliq executes your jobs

• At the scheduled time, Fliq dispatches the HTTP request from the edge region geographically closest to your endpoint.
• If your endpoint returns a non-2xx status or times out, Fliq retries automatically with exponential backoff up to your configured max_retries limit.
• Every attempt is recorded — status code, duration, error — and available via the dashboard and API for up to 7 days (free) or 1 year (Growth).

What Fliq is not

• Not a message queue. Fliq fires HTTP requests on a schedule — it doesn't buffer or fan out messages to multiple consumers.
• Not a workflow engine. Jobs are independent; there's no built-in DAG or step sequencing.
• Not a monitoring service. Execution logs are for your records; Fliq doesn't alert on failures (yet).