Working name: datasip (swap with: grep -rl datasip . | xargs sed -i '' 's/datasip/NEWNAME/g') Shortlisted alternatives (check availability first): capwatch, nettally, hoggr, bytebite, nibble.
Prior art to position against (all live-only, no history): bandwhich, iftop, nethogs, bmon, bwm-ng. Names to AVOID (taken/confusing): trickle (Linux bandwidth shaper), datamon, netwatch, bandwhich.
"I'm on a 5G home router with a data cap. I wanted to know which app was burning my data and when it spiked - not just the live number every other tool shows. So I built datasip: it remembers, so you can ask 'how much did Chrome use in the last 30 minutes?'"
- Show HN: datasip - terminal data monitor that remembers which app spiked and when
- Show HN: I built a per-app data monitor for people on capped connections
- Show HN: datasip - ask your terminal "how much did Chrome use in the last 8h?"
I live behind a 5G router with a monthly data cap. Tools like bandwhich/iftop show live per-process bandwidth, but nothing kept history - so I could never answer "what ate 2GB last night?"
datasip logs per-app usage into tiny per-minute buckets, so you can query any window (datasip app chrome --since 30m), see a ranked leaderboard, and it flags spikes (an app blowing past its own baseline) - even via a background agent while the dashboard is closed.
macOS only for now, pure netstat/nettop under the hood, no root, no telemetry, MIT. Would love feedback on the spike heuristic and what to build next.
Tagline: Know which app is eating your data - live and over time. First comment: Built this because I'm on a capped 5G connection and every monitor only shows now. datasip remembers, detects spikes, and tracks you against your data cap. Free, terminal-native, MIT.
Shipped datasip 🥤 - a tiny macOS terminal tool that tells you which app is eating your data, live AND over any window ("how much did Chrome use in the last 30m?"), and flags spikes automatically. Free + MIT 👇 [GIF]
r/commandline, r/macapps, r/selfhosted (metered-connection angle)
- Pick + availability-check final name (GitHub org, Homebrew, npm)
- Record README demo GIF (asciinema -> agg, or screen capture)
- Port to Go for a single brew install binary (recommended for distribution)
- Homebrew tap repo
- Tag v0.1.0, write a short CHANGELOG