The calendar is where lock-in hides, so ours speaks the open standard

Calendars are the quietest lock-in in a workspace. Mail you can imagine moving. Files you can imagine copying. But the calendar is wired into everyone's phone, everyone's laptop, the meeting room display, and the scheduling link on your website, and untangling that feels like the sort of project that ends careers.

That feeling is mostly a consequence of how the big providers built theirs: as a proprietary service with an API, where the standard protocol is a grudging export path rather than the actual product.

Ours is the standard protocol. That one decision changes what the calendar can do for you.

Open protocol, so your apps just work

Calendars at email.eu speak CalDAV, and contacts speak CardDAV. These are the open standards for exactly this, they predate every proprietary calendar you have used, and essentially every calendar application supports them.

In practice that means Apple Calendar on a Mac or an iPhone, Thunderbird on a desktop, DAVx5 on Android, and whatever else your team has already decided they like. Not a compatibility mode. The native protocol, with two-way sync.

And because discovery is set up properly, most of those apps find the calendar by themselves when someone types their email address. Nobody is copying a server URL out of a support article.

The portability consequence is the real prize. A calendar you sync with a standard protocol is a calendar you can point at any other provider, or at your own server, whenever you want. There is no export step, because there was never an import step. That is the same principle as everywhere else here, and the calendar is where it is least common.

Shared calendars, and seeing when people are free

A team calendar is the point of having a team calendar. You share one from the webmail in a couple of clicks: pick the calendar, pick the colleague, choose what they may do with it. One calendar at a time, so the team-wide one is editable by the people who run it and readable by everyone else, without that being a decision about your personal calendar too.

The rights are more granular than a read or write toggle, which matters more than it sounds. Seeing that you are busy, seeing what the entries actually say, editing your own entries, editing anyone's, replying to invitations, and sharing the calendar onward are all separate permissions. So "the whole company can see when the meeting room is taken" and "three people can move things in it" are different grants on the same calendar rather than a choice between locking it down and opening it up.

Separately from sharing, the system can answer availability questions: is this person free at this hour. That is what makes scheduling a meeting a matter of looking at a grid rather than sending four messages asking. Importantly, availability is a different thing from access. Someone can see that you are busy on Thursday afternoon without being able to see what you are doing, which is exactly the right default in a company. Your calendar reveals a lot about you, and colleagues need your availability, not your business.

Guests who do not have an account

Here is a detail we spent real effort on, because it is where most invitations quietly fail.

You invite someone at another company to a meeting. They receive an invitation by email. Their calendar app may understand it, or may not, depending on what they use. If it does not, historically what they get is an attachment and a shrug.

Ours includes a link to a page where they can simply say yes or no, in a browser, with no account and nothing to install. Their answer comes back to your calendar as a proper response, and the page they land on looks like it belongs to us rather than like a debug screen.

It is a small thing. It is also the difference between knowing who is coming to the meeting and guessing.

Meetings that carry their own room

Add a video room to an event and everybody invited gets a link in the invitation. Guests join from the link, in the browser, with no account and no download. That is Meet, our video pillar, and the reason it is one click from the calendar rather than a separate errand is that a meeting without a room is not a meeting.

Tasks live here too, and one thing that does not

Two honest notes about what you will and will not find.

Tasks are in the calendar. Not a separate product, not an integration. Things with a due date sit alongside things with a start time, which is where they belong.

The out-of-office reply is not in the calendar. It is in your mail settings, because it is a rule about mail rather than about time. This trips people up regularly enough that it is worth saying plainly: if you went looking for it next to your calendar and did not find it, that is why, and it does exist. It is the same server-side rule machinery as your other filters, so it runs whether or not any of your devices are switched on.

Google's "working location" does not exist here. That is a Google-proprietary event type, not part of the calendar standard, and nothing outside Google implements it. If your team has come to rely on it, you will use a recurring all-day event or a naming convention instead. Better you know now than discover it in week two.

Why the standard was the whole point

We could have built a calendar that was slightly more polished by being slightly more proprietary. Plenty of good products make that trade.

But the calendar is where lock-in hides. It is the piece that makes people say "we cannot leave", not because the calendar is good, but because it is entangled. Building on the open standard means the entanglement is with the standard rather than with us, and the day you want to go somewhere else, your apps keep working and point somewhere new.

Calendar is included on every plan, in the same webmail as your mail and contacts.