MultiOBX

What you do online is your business.

Your ISP sees the addresses you reach for. Whoever runs the Wi-Fi sees the same. MultiOBX puts a server of ours between you and the network: traffic leaves the device encrypted, and what goes out to the network is the server's address.

In exchange you move your trust from the ISP to us. Below: what we know about you, what we do not, and how to arrange things so that you need not trust us at all.

There is no account. Instead of an e-mail and a password — a 24-character key.

We do not store the key. What sits in the database is an HMAC-SHA256 of it, and the key cannot be recovered from that record — not by you, not by us. You pay the price: lose the key and the paid days go with it; if a server moves or a hole turns up, we cannot tell you, because we have no address.

Tor is inside the app. No separate browser needed.

Where the traffic goes

Three traffic routes Three routes. Plain VPN («Обычный VPN» in the app): device, our server, internet. VPN, then Tor («VPN, затем Tor»): device, our server, three Tor relays, internet. Tor only («Через Tor»): device, three Tor relays, internet, with our server left out. DEVICE OUR SERVER TOR RELAYS INTERNET PLAIN VPN ENCRYPTED REGULAR INTERNET VPN, THEN TOR TOR ONLY NOT USED
This is how traffic goes while the app is on. Green line: the data is encrypted, and no one along the way can read it — not your ISP, not the Wi-Fi owner. The app encrypts it right on your phone or computer. Dotted grey line: the data has already been decrypted (on our server or on the last Tor relay) and goes on to the site the ordinary way, like everyone else's. The route is chosen in the app: Settings → "Путь трафика" (traffic route).

Who sees what

On the first route your ISP sees that you connected to our server, and nothing else. The site at the far end sees the server's address. On the second route the ISP sees the same thing, while our server does not know where you go next: it hands the traffic to Tor. On the third we are not in the chain at all.

What Tor costs

Three relays instead of one server is noticeably slower, and Tor carries TCP only: calls, games and video chat do not go through it. The app holds that traffic back rather than letting it slip out directly. The firewall does not apply on this route: its rules rest on a tunnel, and there is none here.

Getting started

Get a key

The "Create a key" button issues 24 characters and shows them once. No form to fill in, no e-mail to confirm.

Pay for time

Days go onto the key — by voucher or by numbered order. There is no subscription: when the days run out, the tunnel stops coming up.

Install the app

The key is entered once. Up to 5 devices hang off it; each gets its own address inside the tunnel and its own WireGuard key pair, and the private half never leaves the device.

What it is built from

What the server knows about you

Stored in the database

  • A digest of the key. Not the key itself.
  • The public keys of your devices and their addresses inside the tunnel.
  • The date your paid time ends, down to the hour.
  • Order numbers, if you placed any.

Stored nowhere

  • Name, e-mail, phone. There is nowhere to enter them.
  • A password. It does not exist.
  • Browsing history. The servers keep no connection logs.
  • Your computer's name. A device gets a name from a word list.

Through the tunnel you are still you. Sign in to your mail and the site knows you by your login; no address changes that.

If you do not take our word for it

Pick "VPN, затем Tor". We will see that you went into Tor, but not where; the exit relay will see the destination, but not you. Or pick "Через Tor" — then no server of ours is in the path at all, and there is nothing left to trust us about.

What that does not undo

Your ISP still sees the timing and the volume of the connection to us. That pattern sometimes gives away what you are doing. The word "anonymous" will not appear here.

The key digest

HMAC-SHA256 of the key, with the secret in a separate file on the server. At sign-in the digest is computed again and compared with the stored one. A stolen database signs nobody in; a lost key cannot be recovered, by us either.

Where this does not work

Hyper-V and WSL
Hyper-V virtual machines and WSL have their own network stack, and Windows rules do not reach it. Traffic from there can go around the tunnel.
The first seconds after boot
Until the service is up there are no rules. Persistent rules that apply from system boot are something we have not built yet.
Android and iOS
Both systems let a share of their own service requests bypass any tunnel: connectivity checks, time, a few services. That is a platform limit, and nobody gets around it.
Tor mode
TCP only, and three random relays on the way. Speed drops; calls and games do not work.

The full account: what is closed and what is not

What it costs

Free

The «Через Tor» route costs nothing

No server of ours is busy with it, so there is nothing to pay for. In exchange: slow, TCP only, no leak protection. What paid time includes.

Paid days open our servers and sit on the key, not on a person. Nothing is charged automatically: when the days run out the tunnel stops coming up. The one place we can warn you in advance is the Telegram bot, if you signed in to it with your key — we have no other address for you.

Until you sign in with a key, the link opens the sign-in page first.

A key is issued without a form and without an e-mail.

Press the button and see what comes out. Whether to pay or stay on the free route, decide afterwards.