Ecosystem
One recurrence model, multiple product surfaces
rrule.net is the cloud platform for explainable scheduling. You can use it from the dashboard, automate it through the API, operate it from the CLI, and expose its scheduling logic to AI agents through MCP. The whole ecosystem is powered by the same recurrence engine: rrule-temporal.
rrule.net Cloud Platform
The primary product: hosted schedule management, webhook execution, dashboard workflows, account-bound usage, and operational reliability.
Use it when you want managed scheduling, persistent state, and hosted delivery.
REST API
The programmable interface to the cloud platform. Validate, simulate, create, list, pause, resume, and inspect schedules from your own systems.
Use it when you want direct integration into apps, services, and automation workflows.
Hybrid CLI
A satellite product that lets you run recurring jobs locally, manage cloud schedules on rrule.net, and keep one recurrence model across both worlds.
Use it when you want local scheduling, terminal UX, or mixed local/cloud workflows.
MCP Server
An AI-native interface that exposes deterministic scheduling tools to Claude and other agents through Model Context Protocol.
Use it when an AI assistant needs a reliable, testable understanding of recurring time logic.
Shared Foundation
Powered by rrule-temporal
The cloud platform, the CLI, and the MCP server all rely on the same recurrence engine. That means one timezone model, one DST story, and one deterministic interpretation of recurring schedules across every interface.
- Timezone-safe recurrence semantics across cloud, local, and AI surfaces
- DST-aware occurrence computation with one consistent interpretation layer
- A shared technical base that reduces drift between product interfaces
What to use when
Use the dashboard if...
you want the fastest path to managed schedules, webhook delivery, API keys, and account-level workflows without writing integration code first.
Use the API if...
you need a programmable interface to the cloud platform from your app, backend, CI pipeline, or internal tooling.
Use the CLI if...
you want local recurring jobs, operator-friendly terminal workflows, or one command surface for both local and cloud schedules.
Use MCP if...
you want AI agents to validate, simulate, and describe recurrence rules with the same deterministic logic as the rest of the ecosystem.