Keeper.sh vs Morgen

By Rida F'kih · August 11, 2026 · Updated August 12, 2026

Morgen is a calendar app you install and live in. It shows all your calendars together, plans your day, and brings in tasks from tools like Notion and Todoist.

Keeper.sh is not a calendar app at all. It runs in the background and keeps busy time visible across the calendars you already use. Both can block out your personal events on your work calendar, and the difference is timing.

How often does each one block out your time?

Morgen's Calendar Propagation workflow "will run daily at 6:00 pm" and covers "the upcoming 14 days" (Morgen's guide). The same guide is upfront about the consequence. When an event is cancelled or moved, "there will be a lag as the workflow runs daily at 6pm".

Say you book a dentist appointment at 9am, for 2pm the same day. Your work calendar still looks free at 2pm all morning, because the workflow has not run yet. Anything more than two weeks out is not blocked at all until the day gets close.

Keeper.sh reads your calendars every minute, on every plan. On Pro the block appears on your other calendar in about a minute, two at the outside. On the free plan it is usually about fifteen minutes, and thirty-one at the very most.

Keeper.sh also covers a month back and two years ahead, so a specialist appointment booked eighteen months early is blocked from the day you make it.

Which calendars can each one connect?

Morgen connects more, and most of the difference is task apps rather than calendars.

Morgen connects Google Calendar, Outlook Calendar, Apple Calendar, Fastmail, generic CalDAV, and subscription feeds (integrations). It also connects Notion, Todoist, Obsidian, ClickUp, Linear, Apple Reminders, and more.

Keeper.sh connects Google, Outlook, iCloud, Fastmail, and any CalDAV server. It reads public calendar links but cannot write to them, and it connects no task tools at all.

For calendars specifically, the two lists are close to equal. There is one limit worth noting on Morgen's side. Their guide says the blocking workflow supports "Outlook, Google, iCloud, and Fastmail Calendars", which is narrower than the calendars Morgen can display.

What does a blocked-out copy look like?

Morgen writes a plain placeholder instead of the event. Copies appear as "Private Event (from Morgen)" with no details listed, so you check the original calendar for specifics.

Keeper.sh does much the same, with one difference. A calendar you connect is copied out under the name of the calendar it came from, with the description and location stripped.

So where a Morgen copy reads "Private Event", ours reads "Personal", or "Family", or whatever you named the calendar.

That cuts both ways. Ours tell a colleague a little more at a glance, so a revealing calendar name is worth renaming before you connect it.

Free keeps the anonymised default. Changing what shows through is a Pro feature.

How much control do you get over what copies?

Morgen's guide describes a "Nerd Mode" that lets you add custom filters on things like business hours, event tags, and whether an event has invitees. It also lets you choose between copying every event or only events marked busy.

Keeper.sh switches are per calendar. You can let event names, descriptions, and locations back through, and exclude all-day events, focus time, or out-of-office blocks.

If you want to write filter rules that decide event by event, Morgen's controls go further than ours.

Where does your calendar data live?

Morgen's FAQ states: "We do not store your calendar data in the cloud. Instead, our servers act as a proxy, transmitting data as needed to your devices without persisting it" (Morgen FAQ). The same page describes them as a Swiss company, subject to Swiss privacy law.

Their privacy policy adds that "Our data centers are located in Switzerland or in the European Union, while some partners are located in the United States" (privacy policy).

Keeper.sh keeps a copy of your events in a database. That copy is what makes minute-level timing possible, and it is why a block can appear while you are still walking out of the dentist.

It is a real trade. If you would rather no service held a copy of your events, Morgen's design suits you better. If you want that copy in a database you own, see the self-hosting section below.

What apps does each one have?

Morgen ships desktop apps for macOS 12 and above, Windows 10 and above, and Linux on x86 64-bit (downloads). There are iOS and Android apps too, though the download page says to set up your account on desktop first.

Keeper.sh is a web app you open in a browser, set up once, and close.

If part of what you are buying is a calendar client that lives on your laptop and your phone, that is Morgen.

What does each one cost?

Morgen Pro is $30 a month, or $15 a month billed annually (pricing). Team plans are $25 per seat monthly, or $10 per seat billed annually, with a minimum of two seats.

There is no free tier at all. Morgen offers a 14-day trial with no credit card, and a 30-day money-back guarantee.

Keeper.sh is $0 or $5 a month, flat, for one person. The free plan covers two linked accounts and three connections, and Pro removes both limits.

The prices are not really comparable. Morgen is a full calendar client you sit in all day. Keeper.sh is plumbing you set up once and then forget about.

Can an assistant act on your calendar?

Keeper.sh ships an MCP server with 14 tools, so Claude or ChatGPT can list your calendars, read events, and create, move, cancel or RSVP to them. The same actions are available in the REST API, free at 25 calls a day and uncapped on Pro.

Can you use both?

Yes, and for some people this is the right answer.

Run Morgen as your calendar app, for the interface, the task tools, and the native apps. Run Keeper.sh underneath for the blocking, so your availability is right within about a minute on Pro. The two do not conflict, because Morgen reads your calendars and Keeper.sh writes to them.

Can you run Keeper.sh yourself?

Yes, and this is where the data question gets a different answer.

The whole codebase is on GitHub under AGPL-3.0, with Docker images for a quick first deployment. Self-hosting turns on every Pro feature at no cost, deliberately.

That means the copy of your events sits in a database you own, on hardware you chose. For some people, that settles the privacy question entirely.

It is also genuine work. You need a host, a Postgres database, and Redis. You register your own Google and Microsoft credentials, which takes an afternoon the first time.

Upgrades, backups, and uptime are yours after that. Most people should use hosted Keeper.sh and pay the $5 instead.

So which should you pick?

Pick Morgen if you want a calendar app you enjoy opening every morning. Pick Morgen if you need native desktop apps, and especially if you are on Linux.

Pick Morgen if EU or Swiss hosting matters, or if you want your tasks and calendar in one place.

Pick Keeper.sh if a stale calendar has already got you double-booked. Pick Keeper.sh if you need your time blocked further out than the next two weeks.

Pick Keeper.sh if $5 a month is the right size for a background job, or if you would rather run the whole thing on your own server.

If you are not sure, ask one question. Has anyone booked over you because your other calendar looked free? If the answer is no, Morgen's timing will not bother you.

FAQ

How often does Morgen block out my events?

Once a day. Morgen's guide states that the workflow runs daily at 6:00 pm and covers the upcoming 14 days. Keeper.sh reads every minute, and a block lands in about a minute on Pro, or about fifteen minutes on the free plan.

Can Keeper.sh sync in both directions?

Only by setting up two connections, one pointing each way, because each connection moves events one way. Morgen's blocking workflow runs one way per workflow too.

Does Keeper.sh copy attendees or video call links?

No. A copy carries the times, the busy or free status, and whatever detail your settings let through.

Attendees, meeting links, and reminders are never copied across. Keeper.sh does read attendees, so you can see pending invites and RSVP.

Sources

Every claim about Morgen above comes from Morgen's own public pages, linked inline. Those pages were checked on 11 August 2026, and Morgen may have changed since.

Can Keeper.sh use cookies for analytics?