Tower BrowserDocumentationDownload

TOWER BROWSER 1.0.10

Set up a controlled path for one browser.

Tower Browser is a portable Windows x64 stable release that connects an isolated Mullvad Browser profile to a selected Mysterium WireGuard provider.

01 · REQUIREMENTS

Before you start

Windows x64

The current package targets 64-bit Windows and includes a self-contained .NET 8 desktop runtime.

A user-writable folder

Extract the complete portable archive. Do not mix files from different releases.

Internet access

Identity registration, wallet top-ups, provider discovery, and provider connections use Mysterium services.

MYST balance

Provider traffic is usage-based. Your selected identity needs funds before paid traffic can flow.

02 · INSTALL AND VERIFY

Download the complete portable package.

  1. 1
    Download release 1.0.10

    Use the project’s GitHub Releases page and download the Windows x64 portable ZIP together with its published SHA-256 file.

  2. 2
    Verify the archive

    Compare the downloaded archive checksum with the published value before extraction.

  3. 3
    Extract everything

    Keep the controller, Mullvad Browser tree, Myst backend, locked policy, and bundle manifest together.

  4. 4
    Open TowerBrowser.exe

    The release is unsigned, so Windows SmartScreen may display a warning. Confirm the source and checksum before continuing.

Open releases

03 · IDENTITY AND WALLET

Prepare a Mysterium identity.

Tower starts its owned Myst backend and exposes identity controls inside the native window. Accept the current consumer terms, then create a passphrase-protected identity or import an existing encrypted identity.

Passphrases are not persisted.

Tower asks for the passphrase when a sensitive operation needs it, sends it only to the loopback Myst backend for that operation, and clears the password control afterward.

Funding the wallet

Version 1.0.10 exposes only payment methods supported by both the live Myst response and a registered client adapter. The current adapters cover CoinGate, Stripe-hosted card checkout, and PayPal-hosted checkout. Availability still depends on Mysterium’s services.

04 · CHOOSE A PROVIDER

Inspect the route before connecting.

Open the Connection page and refresh the WireGuard provider list. Search by provider identity, country, city, or ISP, then review the network type and live price shown by the application.

LOCATIONCountry and city
NETWORK TYPEResidential or other
ISPProvider network
PRICECurrent MYST rate
Residential IP availability is dynamic.

Mysterium includes residential providers, but Tower does not guarantee a particular residential IP, location, provider, price, performance level, or session duration.

05 · CONNECT AND LAUNCH

Wait for every readiness check.

Connect to the selected provider. Tower enables browser launch only after the backend reports a connected state and the same composite readiness gate verifies the owned loopback proxy, browser executable, locked policy, and browser process state.

✓

Provider connectedBackend connection state has settled successfully.

✓

Proxy owner verifiedThe expected owned Myst process controls 127.0.0.1:4449.

✓

Locked policy presentThe isolated browser has no direct proxy fallback.

✓

Browser readyThe configured executable and isolated profile are available.

REFERENCE · TRAFFIC PATH

What Tower changes—and what it leaves alone.

01Mullvad BrowserIsolated profile
→
02Loopback proxy127.0.0.1:4449
→
03Mysterium providerSelected exit route
→
04InternetProvider exit IP

Tower does not modify the Windows system proxy, DNS servers, firewall, or route table. Other Windows applications keep their existing network path.

REFERENCE · PROTECTIONS

Browser-scoped safeguards

  • The browser receives a locked HTTP/HTTPS proxy with no direct fallback.
  • DNS prefetch, speculative connections, DNS-over-HTTPS, and WebRTC are locked off.
  • Mullvad Browser anti-fingerprinting defaults remain enabled.
  • The portable manifest checks release version, path containment, byte length, and SHA-256 for critical components.
  • Unexpected proxy owners and non-loopback proxy settings are rejected.
  • Closing the owned backend leaves the isolated browser targeting the unavailable loopback proxy instead of switching to direct traffic.

REFERENCE · RELEASE LIMITATIONS

Know the current validation boundary.

Version 1.0.10 is a stable release, but its package remains unsigned. Code signing, clean-machine standard-user testing, reboot validation, firewall-product testing, and fresh native packet-capture validation remain outstanding. Provider discovery, registration, payments, and connectivity also depend on external Mysterium services.

No live Stripe, PayPal, or CoinGate order was created for 1.0.10. Production checkout, payment completion, provider behavior, and MYST wallet credit remain unvalidated. Always review the release notes and checksum before using a package.