Semsync
Paste two links once, and your Canvas deadlines, NUSMods classes and exams stay in your calendar for the rest of the semester.
Nov 2026 · Live at semsync.live · about ten people using it
Why I built it
My deadlines lived on Canvas and my timetable on NUSMods, but the place I actually look is my calendar. I wrote about why I built it, and about the first feedback, in a note. This page is about how it works.
How it works
You sign in with Google and paste your Canvas calendar link, plus your NUSMods share link if you want your classes too. From then on, Semsync keeps a calendar called "NUS semester" up to date: deadlines titled with their module code, classes only in the weeks they actually run, your exams, a "Week N" label at the top of each week and a colour for each module. A semester comes to about 250 events. Google Calendar gets them directly, and Outlook, Apple Calendar and Notion Calendar can subscribe to a feed with the same events.
About once an hour, for each person
- Canvas feed + NUSMods
- Build the semester's events
- Compare with the last sync
- Send only the changes to Google
A scheduled job in the database runs every 20 minutes and picks up anyone who hasn't been synced in the last hour. For each of them, Semsync downloads the Canvas feed and works out the semester's classes from the NUSMods API, leaving out recess week, public holidays and NUS Well-Being Days, then compares the result with what it sent last time.
Decisions
Only touching its own calendar
Semsync only asks Google for permission to manage calendars it created, so everything goes into its own "NUS semester" calendar and it can't see anything else in yours. Google treats that permission as non-sensitive, which also means there's no "unverified app" warning and no 100-user cap. The note has the story of how I got there.
Doing nothing when nothing changed
Every event gets an ID worked out from where it came from, so the same deadline always maps to the same calendar event, and Semsync keeps a hash of each event it sent. That way a sync only sends what's new, moved or gone. Most hours nothing has changed at all, so after downloading the Canvas feed, Semsync compares a fingerprint of everything that goes into your calendar with last time's and stops there if they match. It also never deletes past events, since Canvas drops items from its feed about 30 days after they happen.
Treating the Canvas link like a password
Anyone with your Canvas calendar link can read your deadlines, so Semsync encrypts it before storing it, along with your Google sign-in. Subscription links are only ever stored as hashes.
Letting an AI read it, carefully
Semsync also has an MCP server, so you can ask an assistant like Claude what's due this week. It's read-only, and it never returns links, rooms or descriptions, because an assistant might follow instructions hidden in them.
What it runs on
It's written in TypeScript with Hono, and runs on Vercel with Postgres on Supabase, both in Singapore. I tried Cloudflare D1 and then Turso first, and moved to Supabase on the third day because Turso had no Singapore region. There are about 200 tests, which run in GitHub Actions against an in-memory Postgres.