Pricing, plainly
Before you wonder.
Honest about what you pay for — and what you never will.
What counts as a job?
One scheduled target — a URL, method, headers, and a cron or interval. The cap counts all jobs on your account, enabled or not, the same way the engine's MAX_JOBS_PER_ACCOUNT knob does. Disable or delete one to free a slot.
Why is sub-minute firing a Pro thing?
Sub-minute intervals can only fire at a verified host you own, and they put more load on the fleet. Free runs at ≥ 60s; Pro lets verified destinations fire to the second and raises the per-account fire-rate. It's a limits decision, not a safety one.
Is security ever behind a paywall?
No. Encrypted secrets, verified destinations, SSRF-safe firing, and auto-disable are included on Free and Pro alike. We tier on how much you can run — never on how safely it runs.
What happens at the Alpha's end?
Everything is free during early access, no card required. The Pro price shown is a placeholder the owner will finalise before billing is switched on — and you'll be told well ahead of any charge. Your jobs keep running on Free either way.
When is Team available?
After the MVP. Team needs multi-user accounts, roles, and audit — none of which are built yet — so it's marked coming, not sold. Single-user Free and Pro are the plans today.