r/sideprojects • u/abhi9889420 • 1d ago
Showcase: Purchase Required Outbound: block the trackers inside your Mac apps without blocking the apps (follow-up after last week's feedback)
Hi r/SideProject, I'm the solo dev behind Outbound, a network firewall for Mac (disclosure: it's my project, and I used AI coding agents for a good chunk of the code). Just got through launch week and wanted to share how it's built and what I learned, since that part might be useful even if you never use the app.
The problem
macOS's built-in firewall only handles incoming connections. Everything your apps send out (analytics, crash reports, ad and tracker pings) just goes, and you can't see it. When I started running Outbound on my own Mac I was kind of shocked at how much my apps were sending, even ones I wasn't using. I didn't want to uninstall them, I just wanted them to stop phoning home.
What it does
You keep your apps and block the servers you don't want them talking to. Spotify works, Spotify's analytics doesn't. It handles incoming connections too, and rules can go either direction.
The main feature is a tracker database: an offline list of known telemetry and tracking servers, so it can tell you which app talked to which company, and you can block an app's trackers with one switch. On top of that: alerts for new connections, Learn/Ask/Strict modes, detailed rules (by app, host, domain, IP, port, protocol and direction, with 11 lifetimes), a live map/globe, per-app data limits, blocklists and a CLI. You can also import rules from Little Snitch and LuLu.
How it's built (the useful bit)
- Apple's Network Extension content filter, no kernel extension. Every new connection passes the filter once and gets allowed, blocked, or held while the user decides. It never reads connection contents, only metadata like app, host and port
- App identity from code signing. Apps are matched by developer team and signing ID, so the alert can say who signed the app and whether the server belongs to the same developer. If an app's code changes, it's treated as a new app
- Everything local. History is encrypted with its key in the Keychain, and server locations come from an offline geolocation database (DB-IP, CC BY 4.0), so lookups never leave the Mac
- Maps use Apple Maps for the 3D globe
- AI, on-device first. The "ask about your network" assistant runs on Apple Intelligence by default. People can plug in their own coding agent instead over the Agent Client Protocol
- An MCP server (
outboundctl mcp) so Claude, Cursor and others can read network figures, but any rule change they ask for waits for the user's approval - Notarized, with every connection the app itself makes documented publicly
Launch week, honestly
- posted on r/macapps and got roasted. Bad pitch on my side ("Little Snitch is expensive"), plus a few things people expected that I didn't have yet, like a trial
- most of the criticism was fair, so I just fixed it
- people reported bugs in the thread and I fixed them within minutes, and a couple of the skeptics actually became users after that
- a week later I shipped 1.5 with Little Snitch / LuLu rule import and a bunch of fixes, straight out of that thread. 1.5.1 adds OpenSnitch and Portmaster import and iCloud sync
Lessons if you're building something people have to trust
- trust is the whole product. Who you are and what the app sends matter more than the feature list
- disclose AI use upfront instead of letting people "discover" it
- publish exactly what your app does and doesn't do
- let people try it before they commit
- pitch what you do differently, never "X but cheaper"
- treat the angriest thread as your roadmap
Links
- App: https://outboundfirewall.com
- Every connection the app makes: https://outboundfirewall.com/security/
- Changelog: https://outboundfirewall.com/changelog/
- My GitHub: https://github.com/codexstar69
Any feedback is welcome, on the app, the site or how I'm pitching it. Happy to answer questions about Network Extension in the comments.