Serververse Network Transit
serververs.com · Egress and tunnels · 1 record · JSON
Serververse Network Transit Egress and tunnels
paidemailno cardDvolume-quota
| 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 |
| Per-object cap | not applicable |
| Retention | not applicable |
| 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 |
| Identity | email A dashboard login at labs.serververs.com issues the install command; the signup form and payment step were not read. |
| Limits |
|
| 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." |
| 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. Four broker calls were spent chasing a price and none was found, so the row stays price-unverified rather than guessed. 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 rung | documented The mechanism, the token flow and the beta status are first-party. Price and allowance are both unverified, and a dashboard login is what would settle them. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
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 (7)
{
"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_tib_month": null,
"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 or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable