Skip to main content

Fully Managed
Open Web Calendar
as a Service

Deploy Open Web Calendar as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Open Web Calendar is an open-source calendar embed — it aggregates multiple iCal/ICS feeds into one customisable web view — combining the convenience of a hosted SaaS calendar with the control of self-hosted infrastructure.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

Open Web Calendar

Open Web Calendar

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Open Web Calendar Preview Image

ABOUT THE SOFTWARE

What is Open Web Calendar

Open Web Calendar is an open-source calendar embed. It fetches multiple iCal/ICS feeds server-side, normalises their timezones and recurrences, and renders a single customisable calendar view that drops into any website via an iframe.

The project is licensed under GPL-2.0 and is maintained by Nicco Kunzmann and a small group of contributors who also maintain the broader Python iCalendar ecosystem (icalendar, recurring-ical-events, x-wr-timezone). Development received public open-source grant funding in both 2024 and 2025 through the NGI0 Core Fund administered by the NLnet foundation. The codebase is Python 3 on Flask, served by gunicorn, and ships as an official Docker image — the same image the maintainer runs for the project's own public demo instance.

The project sits at roughly 300+ GitHub stars and 85+ forks at the time of writing, with active issue triage and a release cadence of every few weeks. It's packaged for YunoHost and available on PyPI under the open-web-calendar package. Open Web Calendar is widely used by community organisations, schools, sports clubs, and parishes that need to aggregate multiple separate calendar sources into one public-facing embed without sending visitor data through a third-party SaaS.

FEATURES

What Open Web Calendar does

A short tour of the capabilities you'll actually use day to day. These are app-level features, not platform features — they describe what Open Web Calendar itself ships, separately from what DANIAN runs around it.

Multi-source ICS aggregation

Point at any number of iCal/ICS URLs — Nextcloud shares, Google Calendar public links, Microsoft 365 published calendars, plain ICS files — and they render as one unified calendar.

Per-viewer time zone

The embed can serve a different time zone to each visitor based on browser detection or a fixed setting. Useful for international communities where the same event reads as 9pm in Berlin and 12pm in San Francisco.

Cache TTL per source

The server-side fetch cache holds remote responses for a configurable window. Faster TTL means fresher events; slower TTL means kinder to upstream calendars that throttle.

Tor and HTTP proxy routing

Optional Tor proxy for privacy-preserving fetches; optional HTTP proxy for allow-listed URL access. Default deployments use neither, but both are documented and we set them up on request.

Custom CSS and JSON specification

Theming via CSS and behaviour via a JSON spec block. Colour-code per source, hide weekends, set the default view, override fonts, restyle event rendering — all without forking the codebase.

Month, week, agenda, list views

Four view modes per embed, switchable at runtime or fixed in the spec. A homepage strip might lock to a 7-day list while a dedicated /events page offers month plus filtering.

Recurring event normalisation

The project's own libraries (recurring-ical-events, x-wr-timezone) handle the awkward cases — annual feasts, weekly trainings with one-off cancellations, recurring rules with exceptions.

Internationalisation

UI translations contributed via Weblate. The calendar embed renders day and month names in the viewer's locale, not just the operator's.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Open Web Calendar

In December 2025, the dominant hosted alternative announced a price adjustment, citing currency depreciation and rising operational costs. Renewals from early 2026 onward pay the new rate. That's the trigger event most of our current Open Web Calendar customers cite when they tell us why they moved.

The new rate isn't itself the problem. The problem is the structural mismatch: SaaS calendar tools price per master calendar, so a parish with five sub-calendars, or a school with eight, pays the per-seat tax linearly forever. Open Web Calendar removes that scaling — one instance aggregates as many ICS feeds as you can point it at. The economics tip the moment you cross two or three calendars.

Running Open Web Calendar yourself isn't free either, and the work that "just deploying the container" doesn't include is what teams underestimate. The most consequential one is the SSRF fetch surface: the calendar server fetches arbitrary ICS URLs on behalf of every visitor, which means without explicit network isolation it will happily fetch private addresses on its own host — including internal admin panels, metadata services, or other tenant containers. The official upstream docker-compose ships a network-shielded example for exactly this reason. Many self-hosters never read that page, or read it and skip the step, and find out the hard way.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Open Web Calendar on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

4-TEAM HANDBALL CLUB

Replacing per-master-calendar SaaS pricing after a December 2025 rate change

A regional handball club with four senior teams runs one Open Web Calendar instance pulling six feeds: each team coach publishes a Nextcloud calendar of training and away fixtures, the venue publishes hall availability, and the league publishes the official fixture schedule. Region: Germany. Custom domain: calendar.club.de. Embed colour-coded per team.

4-PARISH DENOMINATION

One instance, four region-specific embeds for parish websites

A four-parish denomination in the south-west runs one Open Web Calendar instance serving four parish-specific embeds. Each parish's Google Calendar plus a shared lectionary feed flow into a unified view per parish website. Region: United Kingdom. Cache TTL bumped to 30 minutes so worship calendars don't hammer the source during Sunday traffic spikes.

COMMUNITY ARTS VENUE

Twelve resident-artist calendars into one public events page

A community arts space hosts twelve resident performers, each running their own calendar across Google, Nextcloud, and Outlook. The public events page renders one Open Web Calendar embed pulling all twelve. Custom CSS colour-codes by discipline; the source-filter UI lets the public toggle music, theatre, and spoken-word. Region: Canada.

COMPARISON

Four ways to run Open Web Calendar

A flat path comparison — proprietary SaaS, self-hosted on a VPS, self-hosted on a home server, or managed with us. The math is shown at 1, 5, and 10 calendars because most real teams scale past one within the first quarter.

 PATH1 CALENDAR5 CALENDARS 10 CALENDARSOPERATIONAL TIME
Proprietary SaaS
e.g. a Swiss-based hosted calendar tool, Pro tier, per master calendar
$29/mo$145/mo$290/moNone — but a December 2025 price adjustment, with renewals re-rated through 2026
Self-host on a VPS
$24/month production-class VPS (2 vCPU, 4 GB RAM) + $5/mo backup + $15/mo monitoring
$44/mo + time$44/mo + time$44/mo + time5–10 h setup, then 1–2 h/month patching, SSL, backup verification, on-call
Home server
HP ProLiant ML30 Gen10 or similar, amortised over 36 months, plus electricity and business uplink
€210–667/mo
effective
€210–667/mo
effective
€210–667/mo
effective
2–4 h/month, plus carrying the on-call yourself
DANIAN Managed Open Web Calendar€9/mo€9/mo€9/moNone. We patch, monitor, back up, and stay on call.

BY INDUSTRY

Open Web Calendar for specific industries

Four sectors that put particular demands on a calendar embed. Each summary names the regulation that shapes the configuration, the choice we make on the customer's behalf, and the rough scale of feeds the typical organisation in that sector aggregates.

A parish or congregation typically maintains separate calendars for worship services, pastoral visits, lifecycle events (baptisms, weddings, funerals), and community groups. Each is run by a different person — often using a personal Nextcloud or Google calendar — and the unified view needs to land on the parish website without exposing personal calendars publicly. Open Web Calendar fetches every source server-side; the embed shows only the events, not the credentials.

Privacy regulation in this sector tends toward minimum-data: parishioners' attendance at private pastoral events shouldn't render on a public page, and the source-filtering controls let you mark sources as title-only or hidden. We configure recurring-event handling carefully — feast days that repeat annually but with date variance (Easter, Ramadan, Diwali) need normalisation — and we set the cache TTL to 30 minutes to balance freshness against quiet upstream calendars. Typical parishes aggregate 4–8 feeds.
An academic calendar is rarely one calendar. It's the term calendar from the registrar, the exam schedule from each department, athletic fixtures from the sports office, and society events submitted by students. Embedding eight ICS feeds into a school website with a per-master-calendar SaaS tool means eight subscriptions; Open Web Calendar aggregates them server-side into one embed.

Data-protection regulation in education emphasises minimising the exposure of student identifiable information. We configure the JSON specification to strip personal-data fields from event descriptions before rendering, leaving only the room, time, and subject. Schools usually want separate embeds per audience — parents, students, staff — and one Open Web Calendar instance produces all three from different URL parameters. Typical academic clients aggregate 8–15 ICS feeds across departments.
A club's fixtures are scattered: each team's coach maintains a training calendar, the venue manager publishes pitch and hall availability, the league publishes the match schedule, and the social secretary runs the events calendar. Open Web Calendar pulls every source into one club-facing embed. The configuration choice that matters here is per-team filtering: parents of an under-13 team don't need to see the reserves' fixture list.

We use the source-tagging feature to surface only the calendars relevant to whichever page is embedding the calendar. Sports clubs run with intermittent maintenance — the calendar must keep working when the volunteer treasurer is on holiday. Cached fallbacks and our monitoring catch broken upstream feeds before parents start emailing the club secretary. Typical clubs aggregate 6–12 feeds, and we often pre-configure two embeds: a full members view and a parents-only view.
Member-led organisations face a particular shape of calendar pain: every committee, every working group, every chapter runs its own calendar. The AGM is on someone's personal Outlook; the volunteer cleanup is on a steward's Google Calendar; the lecture series is on the events officer's Nextcloud. Open Web Calendar fetches each, normalises the timezones, and renders one consolidated public-facing view.

Transparency expectations in this sector run high — donors and members expect to see what the organisation is doing without having to contact the office to ask. We set the embed to display two months of history alongside three months ahead, so a curious visitor can verify the public meetings actually happen. We also configure a separate dashboard embed for officer-only feeds (board agenda items, draft event proposals) on a path that's not publicly indexed. Typical associations aggregate 5–10 feeds.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

Yes. Open Web Calendar pulls any reachable ICS URL — including the public-share links Nextcloud generates per calendar. We've run instances aggregating up to 30 Nextcloud feeds from separate accounts into a single embed. The fetch happens server-side, so even ICS endpoints behind basic auth or path-secret tokens work.
Out of the box, the cache holds remote ICS responses for 10 minutes. We tune this down to 5 minutes by default on managed instances, since most customers care about adds and edits surfacing fast. If you have feeds that rarely change — or upstreams that throttle — we can push the TTL higher per source.
Open Web Calendar uses the maintainer's x-wr-timezone library to normalise the X-WR-TIMEZONE attribute that most calendar exporters set but few interpret consistently. Source feeds with floating times or missing VTIMEZONE blocks render predictably as a result.
Yes. Week view supports a working-days display that hides Saturday and Sunday — useful for office, training, or class schedules where weekends would add visual noise. The setting is per-embed, so a sports section can keep weekends visible while an academic-calendar embed hides them.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Most SaaS calendar tools expose an ICS export per master calendar, usually under Settings → Export or Sharing → Public Link. Plug that URL into your Open Web Calendar instance, repeat per calendar, and the embed renders.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Open Web Calendar for 7 days

No card. Cancel from the dashboard.