Lokinet Service Node VPS on Offshore Infrastructure

A Lokinet service node forwards anonymous traffic for the broader network and can host SNApps simultaneously. We deploy service nodes with the official Lokinet build on Debian stable, exposing only the protocol ports required by the daemon. SNApps run as separate processes bound to lokinet interfaces, never to clearnet IPs, so a compromise of a SNApp cannot leak the operator's clearnet identity through default routes.

Operators who run both must size the VPS for both. We offer plans from 2 vCPU 4 GB RAM up to 8 vCPU 32 GB RAM. SNApps that proxy large amounts of web traffic benefit from the higher tier, while pure service nodes work fine on the entry plan.

Lokinet itself is anonymous by design. The operator running the service node is only anonymous if the hosting is. AnubizHost provides anonymous signup, crypto only billing, and no KYC. The service node identity advertised to the Lokinet network is independent of the AnubizHost account and rotates on operator command. Linking the two requires breaching both the hosting provider records and the Lokinet protocol metadata, which our records do not retain.

We do not aggregate operator data for marketing. We do not require renewed identity verification at any tier upgrade. Operators run nodes for years on the same anonymous account with no operational interruption.

Some Lokinet service nodes also act as exits, terminating traffic to clearnet on behalf of anonymous users. Exit operation generates abuse mail similar to Tor exits, and our offshore mediation workflow handles those complaints without exposing operator identity. Reduced exit policies that block the loudest abuse ports are supported and recommended for new exit operators.

Romania and Iceland remain our recommended jurisdictions for Lokinet exit operators in 2026. Both have realistic court procedures, narrow data retention rules, and no compulsory operator identification for overlay network traffic.