Why I built privacy controls directly into the browser itself

Hey Product Hunt! I'm Archit, a CS student from India and the solo builder behind Sandbox Browser. I wanted to share the honest story of why this exists.

For a while I kept running into the same problem. Whenever I needed a controlled browsing environment for testing or research, I'd end up with a VPN app in one window, a proxy extension in another, a separate DNS tool somewhere else — and none of it feeling reliable or truly isolated. The browser had no idea what was happening at the network layer beneath it.

So I started asking: what if all of that lived inside the browser itself? Not as extensions bolted on from outside — as real, first-class architecture inside Chromium.

That question turned into Sandbox Browser. Over time it grew to include:

→ Embedded SOCKS5 proxy

→ Windows AppContainer sandboxing

→ Psiphon auto-launch and proxy chaining for censorship circumvention

→ VPN-style toolbar toggle

→ Split tunneling

→ DNS-over-HTTPS

→ Custom HTML/CSS parsers

→ TLS fingerprint randomization

All built solo. All in C/C++ on top of Chromium. No team, no funding, no shortcuts.

I'd genuinely love to hear from this community:

1. If you do security research or browser automation testing, what's your current setup for controlled browsing?

2. Is there a feature here that solves a real pain point for you?

3. What would make this genuinely useful for your workflow?

I read and respond to everything. Happy to go deep on any technical questions. Happy launch day!