The corporate software market is undergoing a shift as vendors move to lock users into proprietary ecosystems, specifically through calendar and email services. Microsoft historically dominated this space using its MAPI/RPC protocol, which created compatibility issues with external systems. While the iCalendar standard (RFC 5545) was introduced in 2009 to facilitate data exchange, Microsoft maintained its market position by promoting the proprietary Exchange ActiveSync (EAS) protocol.
EAS became the industry standard for mobile synchronization because it combined email, calendars, contacts, and tasks into a single connection, while also offering features like delegation and resource management. Competitors including Apple and Google were forced to license EAS to ensure their devices functioned within corporate environments. This dependency created a significant barrier to migration, as users became tethered to the Microsoft ecosystem.
To challenge this monopoly, the IETF is developing the JMAP (JSON Meta Application Protocol) suite. JMAP aims to replace fragmented protocols like IMAP, CalDAV, and CardDAV with a unified, efficient API. The core JMAP specifications were published in 2019, and the ecosystem is now expanding to include advanced calendar and contact management capabilities through JSCalendar (RFC 8984) and JSContact (RFC 9982).
The upcoming JSCalendar 2.0 standard introduces features previously exclusive to Microsoft Exchange, such as sophisticated delegation, consensus scheduling, and automated corporate scoping. These tools allow for granular control over calendar events and seamless integration with external CRM or task management systems. The JMAP for Calendars specification is currently in the final stages of review by the IESG for official publication.
Independent platforms like Fastmail, Nextcloud, and Mozilla Thunderbird have already begun adopting JMAP to provide open alternatives to Big Tech solutions. By utilizing a single HTTP-based API, these services aim to reduce technical debt and eliminate the need for complex, vendor-specific integrations. This transition represents a broader effort to standardize corporate data and regain control over semantic context.
