Consumer SaaS · Calendar

Annum

The whole year, on one page. Both your calendars, merged.

No repos public yet. The build is underway.

Status
Building
MVP live: OAuth, household pairing, year grid, edit/delete, dark mode
55%
Features listed below
7
Tools in the stack
11

No. 01 / The problem

What pain does this solve?

Couples coordinate their lives across two separate Google calendars and a constantly-out-of-sync paper wall calendar. Existing shared-calendar apps either flatten everyone into one feed (you can't tell whose event is whose at a glance) or force a month view that hides the bigger rhythm of the year. Anniversaries, school breaks, travel, and recurring family commitments all live on different surfaces. The big-ass paper calendars solve the visual problem but can't sync from anywhere.

No. 02 / The solution

How the tool works

Annum merges both partners' Google calendars into one full-year grid — every week of the year on a single page, color-coded so you can see at a glance whose event is whose. Households are first-class: invite your partner once, both calendars overlay automatically. Click any day to add an event, click any event to edit, recolor, or delete. LLM-driven smart coloring with a curated 8-color palette fallback. The whole stack is Cloudflare-only — Pages, Workers, D1, KV, Workers AI — so the cost ceiling stays effectively zero and the data path stays tight.

  • Full year on one page — 52 weeks at a glance, no month-by-month flipping
  • Direct Google OAuth with multi-account merge
  • Household pairing — invite your partner once, see both calendars overlaid
  • Click-to-add events on any day, all-day or timed
  • Edit and delete events directly from the popover
  • Color rules with LLM-inferred colors and a deterministic palette fallback
  • Light + dark mode, persisted with system-preference fallback

No. 03 / Technical approach

Architecture decisions

Built as a TypeScript monorepo with Vite + React 18 + Tailwind v4 on the frontend (Cloudflare Pages) and a Hono API on Cloudflare Workers. State uses TanStack Query for server cache and Zustand for local UI. Auth is direct Google OAuth, mediated by the Worker, with refresh tokens AES-GCM encrypted at rest using a Worker secret. The shared-data tier is Cloudflare D1 (SQLite) for relational storage and KV for hot-path caches. Color inference runs on Workers AI with bail rules that fall back to a deterministic palette hash on any latency, contrast, or schema failure. The household table is the tenant boundary, not user identity — the schema is shaped for a future SaaS pivot without rework.

  • React
  • TypeScript
  • Vite
  • Tailwind CSS
  • Hono
  • Cloudflare Workers
  • Cloudflare D1
  • Cloudflare KV
  • Workers AI
  • TanStack Query
  • Zustand

No. 04 / Current status

Where things stand

MVP live: OAuth, household pairing, year grid, edit/delete, dark mode55%

No. 05 / Building something similar?

Recognize this problem in your own business?

This project started as a real frustration Ryan observed working inside companies. If you're dealing with a similar problem, let's talk. The solution might already be in progress, or we build it together.

Or text or call (248) 882-9055