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, trigger workflow tools such as n8n, and expose its scheduling logic to AI agents through MCP. The whole ecosystem is powered by the same @rrulenet recurrence stack: core, recurrence, rrule, and CLI.
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.
Event Scheduling
Explicit event snapshots, event-relative triggers, execution targets, target metadata, and contextual webhook payloads for workflows that depend on business timing.
Use it when static recurrence is not enough and the caller can provide the event context.
n8n Node
A workflow-facing integration that lets n8n use rrule.net as an advanced schedule trigger with managed recurrence and webhook delivery.
Use it when n8n should react to rich schedules without owning the scheduler itself.
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.
@rrulenet Libraries
The package family behind the platform: core recurrence computation, composed schedule expressions, classic RRule compatibility, and CLI workflows.
Use them when you want the same recurrence model inside your own software.
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 the @rrulenet libraries
The cloud platform, API, CLI, MCP server, and public packages share the same recurrence semantics. That means one timezone model, one DST story, one explanation layer, and one canonical JSON representation across every interface.
- Timezone-safe recurrence semantics across cloud, local, AI, and library surfaces
- DST-aware occurrence computation with one consistent interpretation layer
- Composable schedules stored as recurrence or explicit event schedule JSON instead of one flat rule
- Contextual webhook payloads with schedule, target, and execution metadata
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 event scheduling if...
you need schedules relative to explicit events, business windows, execution targets, or workflow-specific metadata.
Use the n8n node if...
you want n8n to receive advanced schedule triggers while rrule.net handles parsing, preview, persistence, and webhook delivery.
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.
Use the libraries if...
you want to embed the recurrence model directly in your own product instead of calling the hosted API.