A focused tool from a small studio.

Why gity

In late 2025, working on a Rust project that lived in a monorepo with about 180,000 tracked files, every git status took six seconds. fsmonitor existed; the setup was fiddly enough that I kept putting it off. Eventually the conclusion: the setup is the actual problem.

gity is what came out of that. One small Rust binary. One command to install, one to register, and your Git becomes fast — fsmonitor, prefetch, maintenance, multi-worktree cache, all from the same daemon, with sensible defaults.

Principles

• One binary. Same bits via cargo, brew, npm, pip, .deb, .pkg, MSI, snap, choco.
• One command to set up. gity register <path>. unregister restores prior state.
• No configuration files. Defaults are right. Tunable through the CLI when not.
• Cheap when idle. ~12 MB resident, <0.1% CPU at rest.
• Honest about what it doesn't do. gity health tells you what's failing and why.

License & funding

gity is open source under the MIT license. No telemetry, no SaaS, no enterprise tier. The daemon talks to your Git, your filesystem, and nothing else.

Neul Labs ships a small portfolio of similarly focused tools. We don't take VC; the studio is funded by consulting and the occasional sponsorship from teams that use these tools at scale. If your team relies on gity and wants to sponsor — gity@neullabs.com.

Contact

Bug reports, feature requests, and war stories about your own giant monorepo: open an issue on GitHub. Direct email: me@dipankar.name.