Plans & Limits

Three tiers built around how serious you are. Free gets you started without a credit card. Pro unlocks the limits that matter for active bots and side projects. Business is for when cron jobs are load-bearing infrastructure.

Comparison

Free — no credit card, no pressure

Two jobs and a 30-minute minimum interval. Enough to keep a side bot alive, trigger a weekly digest, or learn how cron scheduling works before committing to anything. No time limit, no feature degradation — it stays free forever.

Pro — for serious side projects and active bots

The two things that matter when you're running a real bot: 1-minute intervals and 50 job slots. A Telegram bot on Render needs a ping every 5 minutes to stay alive — Pro handles that without workarounds. And 90 days of execution history means you can look back and understand what happened last month, not just the last 7 days.

Pro unlocks failure alerts via Slack, Discord, and Telegram. When a job fails, you get an alert straight to your preferred channel — not just an email. For bot developers who live in Telegram, that's the alert you'll actually see.

Pro also includes missed run alerts. If the scheduler goes silent and your job doesn't execute within 10 minutes of its scheduled time, you'll get notified immediately — via email and all connected channels. Critical for production bots where a silent failure is worse than a loud one.

Pro also gives you 5 heartbeat monitors and response assertion checks. Heartbeat monitors work in reverse — your bot pings QuzenixCron, and if it goes silent, we alert you. Response assertions let you define a string that must appear in the response body; if it's missing, the execution is treated as a failure even when the HTTP status is 200.

Business — when cron jobs are load-bearing

500 jobs and 30-second intervals for teams that rely on cron jobs as real infrastructure — health checks, background syncs, scheduled API calls that customers depend on. A full year of execution history so your postmortems have context.

Business also unlocks two features not available at lower tiers:

REST API + API keys — manage your jobs programmatically. Create, update, delete, and trigger runs from your own backend without touching the dashboard. Ideal for CI/CD pipelines or multi-tenant apps that spin up cron jobs on behalf of users. Full reference in the API Keys section.

Team / workspace access— invite collaborators by email so teammates can share visibility into jobs and executions. You stay the owner — teammates can't touch billing or delete the workspace.

How limits are enforced

Limits are checked server-side at the API layer, not just in the UI. Even if you bypass the form, the API rejects out-of-limit requests:

Upgrading

Go to Settings → Billing. Payments go through Lemon Squeezy — credit card and local payment methods. Your plan updates automatically via webhook the moment payment clears. No manual refresh needed.

Downgrading

When you drop to a lower plan, any jobs that exceed the new plan's limits are paused automatically — the ones beyond your job cap (newest first) and any firing faster than the new minimum interval. Your oldest jobs stay active. Nothing is deleted; re-upgrade and you can resume them.