i2tor.com

What It Is

i2tor is not a custom-built browser, nor is it a traditional enterprise cybersecurity platform. It is a Tor Browser launcher for Linux. It uses a separate Tor Browser profile, starts I2P, a local I2P HTTP proxy, and the Tor daemon bundled with Tor Browser, then uses a PAC file to route .i2p traffic through 127.0.0.1:4444 while keeping all other traffic on Tor Browser’s Tor route.

Core Capabilities and Security Boundaries

Its core design principles are “upstream-first” and “fail-closed.” The former avoids maintaining a browser fork, reducing the risk of delayed browser security updates. The latter requires I2P to be ready before the browser is launched, preventing .i2p requests from silently falling back to other routes when I2P is unavailable. Routing applies only to the browser profile managed by the launcher and does not modify the system proxy, which provides a fairly clear isolation boundary. Downloads are verified before extraction or execution, and extraction rejects unsafe archive paths.

Deployment, Integration, and Management

Deployment is clearly Linux-first, with AppImage, Arch AUR, Nix, and standard Linux binary options available. It can reuse or install Tor Browser, Java, and I2P, then waits for the local I2P HTTP proxy and Tor SOCKS proxy to become available before writing the PAC file and launching the browser. Its management capabilities are mainly limited to the local launch workflow and cleaning up processes on exit; the main documentation does not show centralized management, log auditing, alert integration, or SIEM integration features.

Pricing and Compliance

The main documentation does not mention commercial pricing, payment methods, or enterprise subscriptions. Given its distribution through GitHub Releases, AUR, and Nix, it is closer to a free and open-source tool. No compliance certifications or frameworks such as SOC 2, ISO 27001, MLPS, or GDPR are mentioned, so it should not be positioned as an enterprise security product for compliance-driven procurement.

Pros, Cons, and Best Fit

Its strengths are clear boundaries, a restrained design, no system proxy modification, and reduced misrouting risk through fail-closed behavior. Its limitations are a narrow use case and reliance on components such as Tor, I2P, Java, and local proxies, which creates a barrier for non-technical users. Windows and macOS do not appear to be current priorities. It is best suited to privacy researchers, technical Linux users, and users who need to access I2P within an isolated profile.

Access from China

The main documentation does not provide information on availability from mainland China, mirrors, payment, or local alternatives, so its accessibility from China can only be marked as unknown. For real-world use, you would still need to independently verify access to GitHub Releases, Tor/I2P connectivity, and downloads for related dependencies.