Pick how many hops your traffic passes through and which mode they run. Your device connects to the first hop only; it is the one that sees both you and where you go.
01 · account
Your account is a key pair generated in this browser. It proves you're a distinct user and authorizes sessions — no wallet, no payment.
This key is your account. Save it to reuse this identity on another device. It holds no funds — losing it just means creating a new account, nothing is at stake yet.
02 · tunnel
Choose mode and hops, then generate a config.
normal = direct · sentinel = a node you run at hop 1 records your destinations and gives you a report, see below · extreme = inspected, see below · tor = max anonymity, slow, some sites block it
route
A recommended chain — fastest among routes that keep every hop on a different network. Operator separation is reported per chain, and only counts once a node's operator is attributed. Picking your own hops below is the normal path — it is not an advanced option.
network
Pick hops in order (first = entry, last = exit). Your entry node always sees both ends. Avoid two hops sharing a net or operator — that lets a second party see them too.
| pick | node | net | operator | latency | rep | flags |
|---|---|---|---|---|---|---|
| loading… | ||||||
A domain confirmed against the URLhaus threat feed stops resolving for clients that resolve through a seQroute node. It is not blocked elsewhere on the internet, and a client using DNS-over-HTTPS resolves somewhere this cannot reach.
Your account of where you met it is the most useful thing you can add — the automated checks only see the shape of the name. It is stored with the report.
Set up a node on a laptop or a Raspberry Pi with one command. It registers itself, starts relaying, and earns per minute it carries a confirmed chain.
01 · configure
Tell us where this box is reachable and what it should offer.
This is the id the command on the right installs — the field and the command always match. Press new id when you move on to a different box.
Pre-filled with a fresh unique id. It names this node to the coordinator and cannot be changed later without reinstalling — a node id belongs to the account that first enrols it, so reusing one across accounts is refused. Keep the generated value unless you are deliberately re-enrolling the same node under the same account.
extreme = full MITM inspection; needs a CA on the client and breaks pinned apps. Leave off unless you know you want it.
seQrity = only addresses your device looked up can be reached. Blocks connections to hardcoded IPs and makes your blocklist binding rather than advisory. learn records what your devices resolve without blocking anything — start there. Covers all protocols, and it breaks peer-to-peer apps by design.
enforce is not offered here on purpose. It applies to everyone exiting this node, including strangers who never asked for it, and whether that is safe depends on flags you can change on this page afterwards. Turn it on from the command line, where the installer checks and warns.
02 · install
Paste this into your laptop or Pi terminal. Idempotent — safe to re-run.
Installs — the same id shown in the node id field on the left.
configure on the left, then generate…
It installs WireGuard, Squid, unbound, the agent, generates keys, and registers with the coordinator. Your node appears below within ~30s.
your nodes
Status of nodes attributed to your operator wallet.
| node | endpoint | modes | latency | earned | status | advertise | bump | public bump | drain | remove |
|---|---|---|---|---|---|---|---|---|---|---|
| connect an operator wallet above… | ||||||||||