Show HN: Forced to build my own Harvest alternative tracking and invoicing
Over the years I've tried dozens of time tracking and invoicing apps, and Harvest was the only one I liked. Primarily due to its relatively intuitive UI/UX. I was happy to pay them a reasonable sum for the product they provide, but after the 10x price jack, I had no choice but to seek alternatives. I tried a bunch of them again, found nothing I liked. So, with 20+ years of software engineering experience under my belt, I decided to build my own. Here's the result: https://hourbun.com/ I first an
Read original source
Source record
Recorded metrics
points · 1 votes
2026-11-09 14:30:25.673Z
cumulative since publication
Research analysis
What changed
Source account: Over the years I've tried dozens of time tracking and invoicing apps, and Harvest was the only one I liked. Primarily due to its relatively intuitive UI/UX. I was happy to pay them a reasonable sum for the product they provide, but after the 10x price jack, I had no choice but to seek alternatives. I tried a bunch of them again, found nothing I liked. So, with 20+ years of software engineering experience under my belt, I decided to build my own. Here's the result: https://hourbun.com/ I first an
Version & cost evidence
Source votes: 1 votes (Nov 9, 2026 UTC; cumulative since publication)
Who is affected
Identify the existing workflow this change affects before recommending an upgrade. Launch attention does not establish improvement; an API, pricing or availability change may instead create migration work.
Missing comparison points
Missing checks: old versus new behavior, affected plans and regions, availability date, compatibility, rollback path and cost under the same workload.
Migration check
Save the release or policy notice, run the same task on the old and new option, and compare outputs and the full bill. For retirement notices, verify the deadline before scheduling migration.