decentralized · multi-hop · community-run

A VPN routed through nodes nobody owns together.

seQroute chains your connection across nodes run by separate operators — at home, on a spare VM, or on their own server. Your entry node is a trusted position: like any VPN, it sees your address and your destinations. No node past it learns both. You pick the route. The coordinator never touches your traffic.

Stock WireGuard — no app to install · You choose your hops · Pay per minute

a route across independent operators — watch a packet travel
Youyour device
Nodeentry
Nodeexit
Internetdestination
each hop is a different network · the coordinator hands out routes, never carries them
how it works

Decentralized traffic. Coordinated discovery. Honestly so.

Pure peer-to-peer discovery is unsolved at scale, so we're straight about the split: the data path is decentralized and private; a thin coordinator just tracks who's online and settles credits — and never touches a byte you send.

the data path — decentralized

Where privacy lives

  • Your device connects to the entry node only; the rest of the chain is invisible to it.
  • Chain selection prefers hops on different networks — a /16 check — and relaxes it when the pool is too small.
  • Operator diversity is not enforced yet: a chain can repeat one operator.
  • You pick your hops — and see which share a network or operator.
the control plane — coordinated

What the coordinator does

  • Keeps a live list of which nodes are online, fast, and reputable.
  • Suggests a fast, diverse route — you accept it or build your own.
  • Bills per minute, only once every hop confirms the chain is up.
  • Settlement migrating on-chain over time.
run a node

Anyone can run a hop. Earn for the bandwidth.

Set up a node in one command — on hardware you already have. It registers to your wallet, starts relaying, and earns for every minute it carries a confirmed chain. Weak hardware automatically offers only the modes it can run.

Raspberry Pi at home

A cabled Pi 4/5 is ideal — low power, always on, plug into your router.

A QEMU / virtual machine

Spin up a VM on a box you already run — bridged networking, done.

Your own VPS

Any cheap cloud box works — more bandwidth, more relayed minutes.

ONE COMMAND
curl -fsSL https://seqroute.com/install-node.sh \
  | sudo bash -s -- \
    --coordinator https://seqroute.com \
    --endpoint YOUR_IP:51820 \
    --operator YOUR_WALLET
Installs WireGuard, the resolver, and the agent; generates keys; and appears on your profile — live, with earnings — within thirty seconds.
modes

One toggle changes what the exit does.

Every mode is multi-hop underneath. The mode decides how the final node treats your traffic on the way out — tap a mode to see it.

you entry exit www NAT

Direct exit

Plain encrypted relay to a clean exit IP. Fastest. Sites you reach see the address of the exit node, not yours.

the cleaner internet initiative

Report a scam site. Earn. Protect everyone.

Each chain's exit node resolves the DNS that reaches it — so a confirmed report is refused there, at DNS, for any device that resolves through your node. Find a malicious site, submit it, and once it's confirmed it's refused at every exit for clients resolving through the node. You earn credits for every confirmed report. A client using DNS-over-HTTPS (Firefox's default in some regions) resolves elsewhere and is not covered; nor are Tor sessions, a hardcoded address, or DNS your device sends outside the tunnel.

you submit validate confirm blocked + credits earned

Earn for confirmed reports

Each scam or malware domain that gets confirmed pays out credits to the reporter — usable for your own routes, or held as your contribution score.

Validated, not auto-trusted

Independent validators plus an AI signal score each submission. Honest validators are kept honest by honeypots; disagreement goes to human review — never an automatic block.

Protects the whole network

A confirmed domain feeds every node's resolver blocklist. One person's catch protects everyone — refused at DNS for devices that resolve through the node. It's hygiene, not a hard boundary: a client resolving over DoH goes around it.

sentinel · optional · not running yet

See what your device talks to — not yet.

  • Not running yet. No analysis node reports on this network today, so Sentinel currently detects nothing.
  • Planned: flag repeating call-home patterns and rarely-contacted destinations for you to review — never a verdict that you are compromised.
  • Would see destinations on HTTPS and HTTP only. QUIC, other UDP and other ports are invisible to it, not examined and found clean.
  • Metadata only — no decryption, no deep packet inspection. Never your content.
  • Only as good as its feeds: known indicators and patterns, not novel malware.
  • Confirmed bad domains feed the network blocklist for everyone.

Join the network.

Connect a route in minutes, or run a node and earn for the bandwidth you relay.