An open-source calendar core, advanced planning modules and a production scheduler, all sharing one interaction model across React, Vue, Angular and Svelte. Start free, then add capability when the requirements actually arrive.
Each one solves a different stage of the same problem, and they share a design language, an interaction model and a data shape, so moving up never means starting over.
DayFlow CalendarOpen source coreDay, week, month, year and agenda views that share the same interactions, colours and keyboard model. Drop it in, connect your events, and keep full control of the data layer.
DayFlow ProAdvanced modulesResource timelines, operational grids, self-service booking and print-ready output, layered onto the same open-source core. Nothing has to be rebuilt when the product gets serious.
DayFlow SchedulerPlanning componentA dedicated planning surface for teams that coordinate people, crews and equipment. Change the horizon from a single day to a full year without changing the workflow underneath.
Pro is built on the calendar core, so the two line up feature by feature. Scheduler is a different surface altogether: a standalone planning component rather than a bigger calendar.
| Capability | Calendar | Pro |
|---|---|---|
| Best for | Apps that need a real calendar | Calendars that grew into operations |
| Licence | Open source | Commercial |
| Calendar views | Day → year, agenda | Inherits the full core |
| Event editing & search | Included | Included |
| Resource timeline | Not included | Included |
| Resource grid | Not included | Included |
| Appointment booking | Not included | Included |
| Print-ready output | Not included | Included |
| Frameworks | React, Vue, Angular, Svelte | React, Vue, Angular, Svelte |
| Source code access | Public repository | Lifetime plan |
| Starting price | Free | $89 / year |
Direct manipulation, resource planning, search and printable output. These are the parts that take a quarter to build well and a year to make feel right.
Group resources, scan for gaps and conflicts, then drag or resize the work directly on the timeline as the plan changes.
Group and reorder resource rows, then change the horizon without changing how anyone works with the plan.
Search lives inside the calendar, so the surrounding week stays visible while users narrow down a dense day.
Drag out a block, resize it, edit the details inline. The component owns the mechanics, your app owns the rules.
A dense grid for products that need to see every resource side by side before committing to a slot.
Connect visual availability setup to a self-service flow, with slots, buffers and capacity staying aligned.
Turn any range into a clean, paginated layout for reports, customer handoff or the wall in the ops room.
Typed adapters, sensible defaults and render hooks everywhere you need to take over. Your app keeps the data model and the business rules.
DayFlowSTUDIOnpm create dayflow@latest wires up the adapter for React, Vue, Angular, Svelte or plain TypeScript.import { DayFlowCalendar } from '@dayflow/react'; export function TeamCalendar({ events }) { return ( <DayFlowCalendar events={events} defaultView="week" onEventChange={save} editable /> );}The calendar foundation stays open source. A commercial licence only comes into play when you need the advanced planning surfaces, and a lifetime option is available on both.
Open source and safe to ship in production without a licence of any kind.
Annual per developer, per-seat for teams, or $299 once for a lifetime licence.
Annual per developer, per-seat for teams, or a one-time lifetime licence. Every plan includes source access.
Start with Calendar. It covers the views, editing and search most products need, and it is free. Add Pro when you need resource planning, booking or print, and reach for Scheduler when planning is the product rather than a feature inside it.
Yes. The calendar core is open source and can go to production without a licence. Only the Pro modules and the Scheduler component require a commercial licence.
Pro is built on top of the open-source core, so everything you learn there carries over. Scheduler is a standalone planning component that shares the same design language and interaction model.
Calendar and Pro ship typed adapters for React, Vue, Angular and Svelte, plus a framework-free build. Scheduler currently targets React.
Scheduler ships source access on every plan. Pro includes it with the Lifetime licence, while the annual plans deliver the modules as private npm packages. The calendar core is public either way.
Yes. Custom features, tailored UI and integration support are all available. Write to [email protected] with what you are building.
Pick a starting point and ship a scheduling experience your users will not have to fight.