It's a calendar workspace that treats events as structured data rather than just blocks of time.
I built it because I was planning in Google Calendar, then manually reconstructing what actually happened in another tool during my weekly review.
Velprium adds properties such as status, tags, ratings, and notes to events, then uses them for diary and weekly review views.
It's built with Next.js, TypeScript, Supabase/Postgres, and the Google Calendar API. The trickiest parts so far have been recurring events and reliable two-way sync without polluting the original Google Calendar data.
I'm currently trying to figure out whether the clearest initial use case is "turn your calendar into a weekly review" or the broader idea of a time-based database.
It's a calendar workspace that treats events as structured data rather than just blocks of time.
I built it because I was planning in Google Calendar, then manually reconstructing what actually happened in another tool during my weekly review.
Velprium adds properties such as status, tags, ratings, and notes to events, then uses them for diary and weekly review views.
It's built with Next.js, TypeScript, Supabase/Postgres, and the Google Calendar API. The trickiest parts so far have been recurring events and reliable two-way sync without polluting the original Google Calendar data.
I'm currently trying to figure out whether the clearest initial use case is "turn your calendar into a weekly review" or the broader idea of a time-based database.