Open source vs fully managed
Self-hosting means you own upgrades, uptime, security patches, and data pipelines forever. That can be the right trade-off for internal tools with spare engineering time. Festivo carries those burdens as a service — with status pages, support intake, and subscription-aware behaviour across API and portal.
- Product surfaces: Nager.Date does not ship a customer portal, embeddable widgets, ICS exports, HiBob integration, or OIDC/SAML administration — you build those layers yourself if you need them.
- Governance: Festivo's draft → publish model, version compare, and membership are built for regulated teams that cannot treat holiday data as a mutable file on a server.
When Nager.Date is the better choice
If you want full source visibility, zero vendor spend, and you already run the surrounding platform, OSS can win. Festivo is for organisations that want the holiday platform maintained for them — with the same definition of truth in JSON, browsers, calendars, and HR tools.
A workspace on top of the same holiday data
Many vendors stop at “here is JSON for a country/year.” Festivo keeps that contract for engineers, then adds a control plane so product, HR, and operations can agree on what “a holiday” means for your organisation before it hits production code or customer-facing calendars.
Governed calendars, not ad-hoc spreadsheets
- Named calendars composed from authority sources, with draft → publish, immutable snapshots, and version compare for approvers.
- Blackouts and working-day exceptions layered on official data — carried through publish so APIs, widgets, and exports stay aligned.
- Per-calendar timezones and working-hours profiles so downstream consumers see holidays the way your business actually runs.
Public pages, ICS, and embeddable widgets
- First-party read-only calendar views (month, week, agenda) with stable URLs people can bookmark — not only machine-readable JSON.
- ICS exports and a hosted widget path with scoped publish tokens and origin controls where your plan allows embeds.
- Optional org-branded public paths so intranet and marketing surfaces sit under a namespace you recognise.
Business-time APIs tied to those calendars
Scheduling helpers (next working day, inclusive counts, overlap probes) run against the same published rules as your widgets — not a generic weekend skip disconnected from your blackout list.
An authenticated Business Time Lab lets engineers and PMs probe behaviour before wiring production services.
HR signals, SSO, and automation
- HiBob integration (Growth and above) to align company calendar and time-off signals with Festivo calendars, publish, ICS, and widgets — see HR integrations.
- Enterprise OIDC / SAML for how staff sign in to the workspace — see Enterprise SSO.
- Signed user webhooks with test delivery so Slack, Teams, or internal orchestration can react when publishes and related events happen — see Webhooks.
Portal built for B2B operations
- Playground with persisted requests, OpenAPI / Postman export, holidays explorer with watchlists and share links, and usage-aware analytics.
- Billing depth (cards, EU tax IDs, invoices, purchase orders on supported plans), notification centre, and clear quota / lifecycle banners.
- Help hub, structured support intake, public status, and documentation that covers both API and portal workflows.
Pricing · Calendars & widgets · Documentation · All comparisons