Early March 2026·March 5, 2026
Foundation, auth, and the first site model
The first release established the data model, security boundaries, auth flow, and owner site model needed before feedback could become a real surface.
Highlights
- 01Core Supabase schema and RLS
- 02Server-side auth guards and onboarding
- 03Public-board-first product scope
Full notes
01
Core data model
3 updatesThe initial schema created the entities needed for feedback collection, planning, release notes, and notifications.
- Users, sites, memberships, boards, posts, votes, comments, and tags were added.
- Roadmap, changelog, subscriptions, and notifications were included early.
- Storage rules covered site-owned assets such as uploaded logos.
02
Authentication
3 updatesProtected owner routes were built around server-side user verification and a default site on signup.
- Supabase SSR clients power server and browser auth flows.
- Server guards redirect unauthenticated users before dashboard access.
- Onboarding creates the owner's first site and default feedback structure.
03
Product scope
3 updatesThe product direction was narrowed around public boards first, with the widget as the second product surface.
- Public feedback stayed the core loop.
- Owner-led workflows were prioritized over heavy team management.
- Removed surfaces were kept out of the customer-facing product scope.