Bruvely

since 2026

I built Bruvely in roughly a month in 2026: an internal time allocation app for Redbrick and its portfolio companies. Employees log monthly hours per company; managers and PeopleOps use the submitted data for budget allocation.

Creative and Marketing were each logging hours into something different and retyping the totals into the same Google Sheet at month end. I gave myself a month to replace that ritual with a tool I would actually want to use.

Solo on product, design, build, and database. My friend Maciej helped with @rdbrck.com SSO and the schema.

Postgres on Supabase with row-level security enforcing the privacy rule, react-hook-form and Zod on entry, Recharts on review, Vitest and Playwright so I could refactor without breaking the schema.

**Dashboard**Employee home. Pick a company, log the hours, move on.

**Time entry**One screen, one month, one save.

**Monthly review**Manager view. Submitted months only. Current month stays with the employee.

**Holiday calendars**Per company, per country, per year.

**Users**Admin view. Promote roles, assign teams, archive people who leave.

In August I built a Mac app for Bruvely. It lives in the menu bar and does the one thing people do many times a day: start a timer, stop it, and the hours land in the same month sheet. Swift, signs in with the same Google account as the web app, idle detection asks whether to subtract the break, Sparkle for updates.

**Sign in, log by hand**Same Google account as the web app. Manual entry for the hours a timer never saw.

**Timer**One click to start, one to stop and log. The running timer shows in the menu bar itself.

Internal testing now, web and Mac.

Bruvely~/bruvely