Recuro.

About

Reliable job scheduling,
without the headaches.

Recuro is a cloud-hosted HTTP job scheduler built for developers who'd rather write code than babysit cron daemons.

Why we built Recuro

Every production application eventually needs scheduled tasks -- syncing data, sending reports, cleaning up stale records, pinging health checks. The usual solution is a cron daemon on a server you have to provision, patch, and monitor yourself. When that server goes down at 2 a.m., your jobs stop silently and nobody notices until the damage is done.

Recuro exists to eliminate that failure mode. We built a cloud-hosted scheduler that calls your HTTP endpoints on a cron schedule or on demand, with automatic retries, failure alerting, and a complete execution log. You focus on the code that does the work -- we make sure it actually runs.

How it works

You give Recuro a URL, an HTTP method, optional headers and payload, and a cron expression. We execute the request on schedule, record the result, and retry on failure according to rules you define. If something keeps failing, we alert you. When it recovers, we tell you that too. The entire execution history -- status codes, response bodies, latencies -- is available in the dashboard and via the API.

For one-off work, push a job to a named queue via a single API call. Useful for webhooks, delayed tasks, and event-driven workflows where a fixed schedule doesn't make sense.

Built for teams

Recuro supports team workspaces with admin and member roles. Everyone on the team sees the same crons, queues, and execution history. No more sharing a single login or wondering who changed what.

Open and extensible

The full REST API lets you manage schedules, queues, and jobs programmatically. MCP (Model Context Protocol) support means AI agents can schedule and monitor jobs directly. If your workflow can make an HTTP request, it can use Recuro.