Stop guessing which one. Put them side by side.

The grid says what these tools are. This says what builders did about it — one decision per person, changeable whenever you change your mind.

# Tool comparison — Supabase Cron + Queues vs pg-boss vs Activepieces

Source: Kbaise, a directory of tools that work with Lovable projects.
Pick one and tell me why before writing any integration code.

## Supabase Cron + Queues (supabase-cron-queues)
- URL: https://supabase.com/docs/guides/cron
- Category: Automation & background jobs
- Cost: mixed — Included on all plans including Free (500MB database, 2 active projects, pauses after 1 week idle). Pro from $25/mo. No separate per-job or per-message charge.
- What it is: Supabase Cron wraps pg_cron for schedules ranging from every second to once a year, and Supabase Queues wraps pgmq for durable message queues with guaranteed delivery. Both are managed from the dashboard, callable from plain SQL, and consumable from Edge Functions.
- Why builders pick it: If your app state already lives in Supabase, this is the fewest moving parts possible: schedule a job and enqueue work with SQL, no extra vendor, no extra invoice, no extra dashboard to check.
- Trap: Supabase advises no more than 8 concurrent jobs and under 10 minutes per job: this is a database extension, not a compute platform. Free-tier projects pause after a week of inactivity, which silently stops your crons.
- Full dossier: /api/public/tools/supabase-cron-queues

## pg-boss (pg-boss)
- URL: https://github.com/timgit/pg-boss
- Category: Automation & background jobs
- Cost: free — Free and MIT-licensed, no hosted tier and no per-job billing. Your only cost is whatever your Postgres instance already costs.
- What it is: A Node.js job queue that uses Postgres SKIP LOCKED for concurrency instead of Redis. Provides cron-scheduled jobs, deferred and throttled jobs, retries with exponential backoff, job dependencies via completion callbacks, and automatic archiving and pruning of finished jobs.
- Why builders pick it: The zero-new-infrastructure option: if you have Postgres you already have a queue, and jobs can commit in the same transaction as your data, which kills the dual-write bug where the row saves but the job vanishes.
- Trap: Needs a long-running Node process, so it does not work on serverless. Throughput ceiling is your database: fine for thousands of jobs a minute, not hundreds of thousands.
- Wiring: npm install pg-boss
- Full dossier: /api/public/tools/pg-boss

## Activepieces (activepieces)
- URL: https://www.activepieces.com
- Category: Automation & background jobs
- Cost: mixed — Community edition free under MIT with no cap on runs, users or flows. Cloud Free: daily refreshing credits. Plus $16/mo (up to 5 users), Team $166/mo (25 users). Overage $0.007/credit.
- What it is: Open-source Zapier alternative under a true MIT licence. One credit per flow run regardless of how many steps it contains, which makes long workflows cheap. Ships Flows, Agents, Chat, Tables and MCP servers on every tier, and pieces are TypeScript so you can write your own.
- Why builders pick it: The pick when licence purity matters: MIT lets you embed and resell it, which n8n's fair-code licence forbids. Per-run rather than per-step billing rewards big workflows, and self-hosting has no artificial run cap.
- Trap: The open-source build excludes Agents, Chat, Projects, API access, SSO and audit logs, so 'MIT licensed' does not mean feature parity with cloud. AI model steps cost 2 to 20 credits unless you bring your own key.
- Wiring: docker run -p 8080:80 activepieces/activepieces
- Full dossier: /api/public/tools/activepieces

## Quick read

- Free with no card: pg-boss.

## Rules
1. Prefer the free tier when no budget was stated, and say what the ceiling is.
2. Read the full dossier before integrating.
3. Fetch /api/public/models before writing any AI model ID.

Agents can fetch the same thing: GET /api/public/compare?slugs=supabase-cron-queues,pg-boss,activepieces