How it works · Tour · Quick start · Docs
A focus app for Linux that is hard to get around.
Distracting sites slow to a crawl at the network layer, routines start sessions on their own, and every early quit costs you a building.
| 🐢 Throttle, don't kill | Distracting sites buffer and load slowly; docs, mail and work sites run at full speed. |
| 🛡️ Root daemon | deepworkd enforces with nftables, tc/netem, its own DNS and SNI checks. Closing the app changes nothing. |
| ⏰ Routines | Focus slots start on their own. A few skips a week, no more. |
| 🏙️ A city that remembers | Finished sessions raise buildings. Surrendering, tampering or bypassing cracks or levels them. |
| 🚪 A way out, never a lockout | Surrender takes 10 minutes, sessions cap at 6 hours, and TTY root always works. |
What it holds up against
| You try | DeepWork |
|---|---|
| Close the app or kill the daemon | Rules stay in place; the daemon restarts |
| Reboot or suspend | Session resumes; time only counts while awake |
dig @8.8.8.8, DoH, QUIC |
Redirected, dropped, or forced back to TCP |
sudo nft flush ruleset |
Repaired within a second, and it costs you |
sudo / pkexec mid-session |
Denied until the session ends |
| Loosen the config | Waits 24 hours; tightening is instant |
Full threat model: docs/ARCHITECTURE.md.
 |
 |
| In session. Each one raises a building. | Surrender. Ten minutes to change your mind. |
 |
 |
| 260 hours in. A metropolis. | What giving in costs. Cracks and rubble. |
 |
 |
| Stats. Every session, kept or quit. | Site lists. Loosening them waits a day. |
curl -fsSL https://deepwork.sagyamthapa.com.np/get.sh | sh
deepwork start 50mThe script picks the right package for your distribution from the
latest release and starts
the daemon. Rather do it by hand? Download the .deb, .rpm or Arch package
from there, or build from source (Development).
| Requires | |
|---|---|
| OS | Linux with systemd: Debian 12+, Ubuntu 22.04+, Fedora, openSUSE, Arch (x86_64, aarch64) |
| Kernel | nftables, tc/netem |
| DNS | systemd-resolved (works with DNS-over-TLS) or plain /etc/resolv.conf |
- Architecture: how enforcement works, threat model, safety rails
- The game: coins, needs, blueprints, what giving in costs
- The app: the window and the 3D city
- Development: building without root, mock UI, CLI, releases
- Roadmap: what's next
- Design language: fonts, colours and components shared with the site, light and dark
- Contributing · Security · Code of conduct
MIT · Created in T3 Code