Claude Routines is great for the first 15. Rotor is for everything after.
No daily cap. Sub-minute schedules. Retries that work. State that survives crashes.
The cap
Why teams outgrow Claude Routines
5 runs a day on Pro. 15 on Max. 25 on Team.
One-hour minimum interval. Nothing sub-hourly.
No retries. No state between runs. No searchable logs.
Migration
What you keep
Your prompts. Your MCP servers. Your Anthropic API key.
Wrap them in Rotor steps. Schedule with no daily cap.
Upgrade
What changes
Schedule every minute, not every hour.
20,000 step-runs a month, not 450 routine runs.
Workflows that resume after crashes.
Logs you can search by step, status, or payload.
The math
How the volume works
Claude Max: 15 routine runs a day. That’s 450 a month.
Rotor Starter: 20,000 step-runs a month for $29.
Even with 10 steps per workflow, that’s 2,000 monthly runs.
Four times the volume. Plus retries, plus state, plus observability.
How Rotor compares to Claude Routines
| Feature | Rotor | Claude Routines |
|---|---|---|
| No daily run cap | Yes | No |
| Sub-minute schedules | Yes | No |
| Durable step state | Yes | No |
| Auto-retry on failure | Yes | No |
| Runs unattended (no approval)(Routines require manual trigger) | Yes | Yes |
| Searchable run history | Yes | No |
| MCP callable in production | Yes | No |
Rotor
YesClaude Routines
NoRotor
YesClaude Routines
NoRotor
YesClaude Routines
NoRotor
YesClaude Routines
NoRotor
YesClaude Routines
YesRotor
YesClaude Routines
NoRotor
YesClaude Routines
NoThe math
| Volume | Rotor | Claude Routines |
|---|---|---|
| 5,000 step-runs / mo | $9/moHobby | Claude Pro $20/mo (15 Routines/day cap) |
| Unlimited runs | $99/moPro | No equivalent in Routines |
30-day money back on any Rotor plan.
Switch in an afternoon
Export your Routine's prompt and tool calls
Wrap the logic in a Rotor TypeScript workflow function
Add step.run() around each tool call for memoized retry
Set a cron schedule with rotor schedules create
Deploy with npx rotor@latest init