Scheduled jobs — cron#

Replaces Vercel Cron (and every other hosted scheduler).

Want something to happen on a schedule — a nightly cleanup, a weekly digest, an hourly sync? Tell your agent: "run this every night at 3am." It sets the schedule up on your machine, and because the machine is always-on, the job just runs — on time, every time.

Why there's nothing to rent#

Hosted "cron" products exist to paper over a gap: serverless platforms have no always-running machine to schedule against, so they sell you a scheduler. Your machine is always-on, so it doesn't have that gap — a scheduled job simply fires. Underneath, it's the standard system cron that's been on every Linux for decades; your agent handles the mechanics, so you don't have to.

It's on the same machine as everything else#

A scheduled job can reach the rest of your stack directly — hit your database, push a report to storage, or send a digest with wrkr email — all on one box, with no glue services in between. Just describe what the job should do, and your agent builds it against the primitives.

Related#

• Your apps in production
• Database — wrkr db
• Email — wrkr email