Reduce helpdesk tickets. Fix legacy Exchange/ERP exports for modern BYOD iOS & Android fleets.
Paste the URL of your broken calendar feed
Detect 36+ RFC 5545 violations including missing VTIMEZONEs, broken RRULEs, and invalid UIDs. Get detailed error report.
Our repair engine automatically detects and remediates these common failures found in Internal IT calendar feeds at the network edge.
Events lack start time property
Impact
Calendar clients reject event or default to epoch time (Jan 1, 1970)
How Lokr Fixes It
We inject DTSTART using DTSTAMP or current time as fallback
RFC 5545 §3.6.1 requires DTSTART for all VEVENT components
DTSTART is DATE but DTEND is DATETIME (or vice versa)
Impact
Events show incorrect duration or fail to render
How Lokr Fixes It
We normalize both to same type, preferring DTSTART type
RFC 5545 §3.6.1 requires DTSTART and DTEND to have same value type
Events lack creation timestamp property
Impact
Some calendar clients reject events or fail to sync updates
How Lokr Fixes It
We inject DTSTAMP with current UTC time
RFC 5545 §3.8.7.2 requires DTSTAMP for all VEVENT components
Lines exceed 75 octets without proper CRLF folding
Impact
Some strict parsers reject file or truncate long lines
How Lokr Fixes It
We apply RFC 5545-compliant 75-octet line folding with CRLF
RFC 5545 §3.1 requires lines to be folded at 75 octets
Need a deep dive into all 36+ RFC violations we support?
Legacy formats and device fragmentation break your infrastructure. Standardize your delivery layer today.
Personal iOS and Android devices handle VTIMEZONE data differently, creating 'it works on my machine' issues.
Old on-prem systems generate non-compliant ICS feeds that modern clients reject.
Exchange, G-Suite, and iCloud all interpret RFC 5545 differently.
Specialized infrastructure to remediate vertical-specific edge cases.
We enforce strict compliance on all outgoing feeds, guaranteeing compatibility with Apple, Google, and Microsoft clients.
Sit Lokr in front of your old Exchange 2010 or on-prem ERP servers to modernize their output instantly.
Inspect raw ICS data and identify validation errors in real-time.
We don't sell to end-users. We build for the engineers and admins who have to keep the systems running.
"ServiceNow change management calendars were unreadable on Mac. Lokr standardized the output so our devs see the freeze windows."
Eric D.
Senior SysAdmin, Financial Institution
"Jira release calendars needed to be visible to non-Jira users. Lokr proxied the feed, making it compatible with default Outlook subscriptions."
Jessica L.
Engineering Manager, Software Platform
"We decommed our Exchange 2010 server but kept the calendar archives. Lokr converts the legacy data for modern Office 365 clients."
Brian K.
Network Architect, Government Contractor
Diagnose errors and test the fix instantly.
Fix one critical feed.
Department-wide infrastructure.
Organization-wide infrastructure.
Most IT departments choose Standard to fix calendar fragmentation across BYOD fleets.
Ready to eliminate calendar support tickets forever?
Contact Sales, we’ll set up your perfect feed today.
Launch a production-grade proxy with Zero-Persistence security.
Review technical standards across Higher Ed, Logistics, and Enterprise IT.
Step-by-step remediation for Canvas, Greenhouse, Ellucian, and PeopleSoft.