Skip to content
Our mission

Making event distribution and sharing accessible and affordable for everyone.

Add to Calendar PRO grew from a practical open-source solution into a managed way to publish, distribute, and support dependable event journeys.

The mission remains simple: give organizers reliable tools while keeping event sharing fair and accessible.

Note from the founder

I built the first version because I needed a dependable calendar button for my own wedding website. What started as a small open-source fix became a bigger promise: make event sharing reliable, fair, and accessible.

Jens Kürschner, Founder
01 / ORIGIN

A wedding site exposed a wider problem.

In 2021, the founder needed an add-to-calendar experience for a wedding website. Existing options were expensive and limited, or unreliable. So the founder built one.

The solution became a public open-source project. A community formed around it, and maintenance continued as calendar providers changed their behavior.

That work made the missing operational layer visible: RSVP, email delivery, server-side ICS generation, and implementation friction.

Non-live usage snapshot

Usage visible in the open.

The usage of our Add to Calendar Button is public. While it only represents a fraction of our offering, it already illustrates our technological leadership.

10,055,236npm installations
622,122monthly npm installations
161,480,118monthly CDN hits
02 / EVOLUTION

From public component to managed workflow.

All PRO features

Build the dependable core

The open-source Button addressed calendar-provider behavior and made the implementation publicly inspectable.

Learn from real friction

Community use revealed work beyond the button: RSVP, email, server-side ICS, changing providers, and maintenance.

Add the managed layer

PRO adds server-side reliability and managed publishing, distribution, response, and follow-up.

Keep the posture

Transparency, fairness, and authenticity carry from the public project into the managed service.

See the work in context

Follow the product workflow.

Move from the origin story into the managed event journey and its open-source boundary.