Opportunities › Self-hosted coding activity tracking backend › Proposed app
Tallyhome
Self-hosted coding time tracking that works with your existing editor plugins
- Score
- 45
- confidence 53
- Evidence
- 4
- items on the page
- Rivals
- 1
- named in sources
- First version
- 25 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2013
- Mature market · AI estimate
ScreensConcept
Desktop app: Developers review coding time, project breakdowns, and analytics across long work sessions at their desks, with keyboard setup and detailed breakdowns. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Today
Server online5h 42m
About this appAI proposal
Tallyhome is a backend you run on your own server. Point the editor plugins you already use at it, and it records time per project, language and editor, without sending anything to a third-party cloud.
It is built for developers and engineering teams who want coding statistics but keep source-adjacent data in-house. Install with one container, then read your stats in a phone-friendly web app.
Unlike a bare API, it adds managed team views, simple backups, and hosted-or-self-run options, so a team lead can set it up in an afternoon.
- Tagline
- Your coding hours, kept on your own server.
- Voice
- PlainCalmPrecise
- Why this name
- A tally is a simple count you keep yourself, and home says the data stays where you live. Together: your hours, counted at home.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Works with existing plugins
Accepts the WakaTime-style client protocol, so editors keep their current plugin. Change one API URL and key.
No member yet
Your server, your data
Run it in Docker on your own hardware or cloud. Data stays in your database and you can export it any time.
No member yet
Project and language breakdown
See time by project, language, editor and branch over day, week or month.
No member yet
Team view with privacy controls
Share totals with a team while each person decides whether file names and branches are visible.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#12372ADeep Pine · primary#F6F3EAPaper · surface#1B1F1DInk · text#E3A02FAmber · accent#6E9A6BMoss · data
Typography
Aa
Tallyhome
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Your coding hours, kept on your own server.
PricingAI proposal
The material gives no competitor prices and no monetization. These tiers are a starting point to test, with a free single-user tier since self-hosted alternatives already exist.
Self-run
Free
- One user
- Docker install
- Plugin-compatible API
- Export to CSV and JSON
Team license
$49 a month
- Up to 25 users
- Team views and privacy controls
- Scheduled backups
- Weekly email digests
- Email support
Managed
$99 a month
- We host it for you in your region
- Up to 25 users
- Updates and backups handled
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Reaches customers through search, developer communities and documentation. Self-hosted installs are private to each team, so use does not show the product to outsiders.
- Do they become customers?
- Developers who find it are the buyers, but a free self-run tier may not convert. Test whether team leads pay for team views, backups or hosting.
- First customers
- Engineering leads at small software teams of 5 to 25 developers who already self-host internal tools and care where their data lives.
- Where to reach them
- Self-hosting communities: Post a setup guide and demo in forums and subreddits for self-hosters and homelab users.
- Developer blogs and search: Write guides on moving off cloud time trackers and on plugin configuration for each editor.
- Open-source issue threads: Answer questions where users ask for team features in existing self-hosted trackers.
- First milestone
- Five teams pay for the team license or managed plan within 60 days of launching the guide.
Why people already pay for this
- VerifiedGitHub repository gained 4448 stars in 2698 days
- Public claimA minimalist, self-hosted WakaTime-compatible backend addresses the market need for coding statistics tracking with data sovereignty and control
- AI inferenceThe repository has 4448 stars and 306 forks, indicating substantial developer interest in self-hosted coding statistics solutions
- VerifiedWakaTime's pricing page lists 4 paid plans, from $9 to $14 a month, plus a free plan
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Time-series storagePostgres rollup tablesHeartbeats arrive often; indexed Postgres tables with rollups should be enough at team scale.
- This app · Self-host packagingDocker image and Compose fileBuyers expect to run it themselves with a single command.
RisksAI inference
- PlatformCompatibility depends on a third-party plugin protocol that can change without notice, and the maintainers of existing plugins may not support custom servers well.
- CommercialFree open-source self-hosted backends already exist with thousands of stars. Willingness to pay for a team layer or hosting is untested.
- Intellectual propertyClaims of compatibility must avoid using the incumbent's name or branding; the protocol and terms of use need legal review.
- TechnicalHeartbeat volume from many users can strain a basic database, and self-hosters need simple upgrades and migrations.
- DataTeams storing file names and branches hold sensitive data, so access control, backups and deletion must be correct from day one.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.