Sam Benson

Getting Synara ready for launch & solving the last hard problems before we ship

by

Hey everyone, here's a quick update on Synara, my API for delivering calendar invites that don’t break across Google, Outlook, Apple, and ICS.

We’re finally getting close to launch, and I wanted to share where things stand and what’s left.

Where we're at

Over the last few weeks, I’ve been tightening the fundamentals:

  • Google Calendar sync is done
    Real two-way updates, no hacks, no scraping, no unofficial endpoints.
    Proper conflict handling + clean ACE envelopes.

  • Microsoft is next
    Graph is a minefield of inconsistent behaviours depending on account type, delegated vs. app-only permission, and how aggressively Outlook caches. But we’re getting there.

  • Apple is the hardest
    Apple doesn’t support per-event subscriptions, only whole-calendar webcal:// feeds.
    I’ve just finished the architecture to auto-generate per-attendee, per-event ICS feeds so Apple users get real, automatic updates instead of static files that rot.

  • Pricing + onboarding are final
    Every sign-up gets a project, 1,000 invites, and 30 days to actually send something real.
    No fake “demo mode”. It’s the real system, with real delivery. Oh, and early-access users will get 50% off all packages for the first 6 months!

Where we're going next

The remaining blockers before launch:

  1. Finish Microsoft syncing (the last major client).

  2. Polish the dev console (webhooks, envelope previews, logs).

  3. Write the docs in a way that reflects how Synara actually works, not how ICS pretends it works.

  4. Ship a stable JS SDK with real examples and real tests.

After that, we open the doors.

Why this all matters

If you’ve ever shipped calendar invites at scale, you already know the problem:

  • ICS is 25 years old.

  • Each vendor interprets it differently.

  • Updates silently fail.

  • Some clients ignore cancellations.

  • Some override the wrong fields.

  • And “sync” means different things depending on which device is reading it.

Synara is basically:
“One API call → all attendees stay in sync across every client.”
The underlying spec (ACE) tracks versions, diffs, and authoritative state so updates behave consistently.

If you want early access

I’m letting in a few more people as we finish the last pieces.
Not for marketing - I just need more real-world input before launch.

Drop your email: https://synara.events

And if you deal with calendar delivery, I’d genuinely like to hear how you’re solving (or suffering through) it today.

Happy to answer questions.

12 views

Add a comment

Replies

Be the first to comment