Serververse Network Transit

docs.serververs.com/labs/ip-transit/beginRouted public IPv4 over WireGuardegress/serververse-network-transitJSON compare report an error provider JSON

Free allowance: No free tier named. The product is sold through a store: "Checkout stays in sync with the store - the price you see on /nt is the price you pay at store.serververs.com." That store page carries no price.
Verdict: paidno free allowance; listed for its price
Cost: no price statedsee Price below
Identity: emailno card, no phone
Binding limit: volume-quotaunpublished
Evidence: documented3 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23

Free tier	No free tier named. The product is sold through a store: "Checkout stays in sync with the store - the price you see on /nt is the price you pay at store.serververs.com." That store page carries no price. unit none; metered on none
Price	unverified: no price on /nt, /network, the docs, or the store product page
Limits	volume-quota (binding) unpublished source
Binding	volume-quota With no published allowance, the first thing that fails at 1 TiB/month is the vendor's own judgement rather than a counter. The beta status is the bigger risk: "Network Transit is currently in beta. Breaking changes may occur between minor versions."
Identity	email A dashboard login at labs.serververs.com issues the install command; the signup form and payment step were not read.
Egress	No allowance is published on the docs, the /nt page, the /network page or the store product page.; ingress: tcp+udp free allowance: none published
Interface	cli, rest Install command plus dashboard; "Manage your account and tunnels from your own scripts. Premium feature."
Tooling	one-line installer; customer API as a premium feature
Composes with	Designed exactly for a user's shape: a Linux box anywhere gets a routed public IP without moving into a datacentre.
Reliability	Beta service with breaking changes between minor versions; no uptime figure published.
Notes	serververse.io does not answer; the live brand is serververs.com, with docs.serververs.com and store.serververs.com. The install-command design is the notable part: it removes the config-file step entirely, which is why wg_path is registration-api rather than native-conf.
Evidence note	documented The mechanism, the token flow and the beta status are first-party.
Parsed numbers	has-free-tier 0

Evidence 3

date	source	what it proved
2026-10-23	docs.serververs.com/labs/ip-transit/begin	token-based install command, WireGuard transport, routable public IP on a machine behind NAT, beta status
2026-10-23	serververs.com/nt	two buy paths, IP lease and transit, both sold through the store; no price shown
2026-10-23	store.serververs.com/products/network-transit	the product page exists and carries marketing copy but no price

More fields 6

wg path	registration-api
wg detail	Provisioning is a token, not a file: "Your personalised install command - including your provisioning token - is generated for you" and "Serververse provisions your tunnel on the edge network and your server receives a routable public IP." The transport is named: "Traffic is routed through the Serververse edge network over a secure WireGuard tunnel". A customer API exists as a premium feature.
ingress	tcp+udp
volume stated	No allowance is published on the docs, the /nt page, the /network page or the store product page.
bytes transit	yes
transit note	The vendor's edge network announces and routes the address.

Unknown values 2

per object cap stated: the field does not apply to this kind of offer
retention stated: the field does not apply to this kind of offer