# Cloud
Source: https://docs.serververs.com/cloud/index
Documentation for Serververse Cloud services including VPS and infrastructure management.
Serververse Cloud provides scalable infrastructure for developers, startups, and production workloads.
Cloud services are designed to give you full control over compute resources while maintaining simplicity and performance.
## Available Cloud Products
> **[Virtual Private Servers (VPS)](/cloud/vps/index)**
>
> Deploy and manage virtual servers with full root access, public IPs, and flexible operating systems.
## What You Can Build
* Application servers and APIs
* Databases and caching layers
* Game backends and automation tools
* Internal services and staging environments
* Custom software stacks
## Getting Help
If you’re unsure which cloud service fits your workload, reach out through support or community channels.
# Email Hosting
Source: https://docs.serververs.com/email/index
Guides to set up, connect, and manage your Serververse email hosting.
Manage emails with ease
> **[Email Setup](/email/email-setup)**
>
> Email Setup for SMTP Server, Personal or for Work with IMAP, SMTP & POP protocols
> **[Email Migration](/email/email-migration)**
>
> Migrate Your Emails from any Host like Gmail, Yahoo, Outlook with ease
# Serververse™ Docs
Source: https://docs.serververs.com/introduction
Explore docs for Web Hosting, Minecraft Servers, Cloud (VPS), and Enterprise Solutions – all powered by Serververse.
# Welcome to Serververse Docs
Everything you need to set up, manage, and scale your services — from web to game servers and cloud infrastructure.
> Self-serve. High-performance. Built for founders, developers, and growing teams.
## Choose Your Product
> [!NOTE]
>
> Don’t know where to begin? Start by selecting your product category below.
## Web
Launch and manage websites with Serververse’s fast, secure web hosting stack. Includes domain management, email hosting, SSL, and website tools.
> **[Web Hosting](/web/index)**
>
> Learn how to purchase hosting, connect your domain, set up email, and manage your website.
> **[Email](/email/index)**
>
> Learn how to setup email, use mailbox, and manage your emails
## Cloud
Deploy and manage virtual servers, S3 & more that is designed for developers and power users.
> **[Cloud](/cloud/index)**
>
> Built SaaS, & More with Cloud
## Gaming
From buying to launching, customize and secure your Game server in minutes.
> **[Start Your Minecraft Server](/minecraft/start)**
>
> Buy, deploy, and manage your Minecraft server using the Game Panel.
## Labs
Experimental features, advanced configurations, and edge use-cases.
> **[IP Transit](/labs/ip-transit/begin)**
>
> Set up secure tunnels, private routing, and proxy-based architectures.
> **[Edge](https://serververs.com/edge)**
>
> Deliver content and route traffic globally with low latency edge infrastructure.
> **[AI Compute](https://serververs.com/ai-compute)**
>
> Run AI workloads, inference, and GPU-based compute at scale.
## Enterprise & Partner
Custom infrastructure and partnerships for businesses, SaaS platforms, and service providers.
> **[Partner With Serververse](https://serververs.com/partner)**
>
> Become a reseller, infrastructure partner, or offer white-labeled services.
## Need Help?
> **[Join Our Discord](https://discord.gg/pXmG5CuveT)**
>
> Talk to the Serververse team and community in real time.
> **[Create a Ticket](https://store.serververs.com/tickets/create)**
>
> Talk to the Team and issue resolved within 48 hours.
# IP Transit
Source: https://docs.serververs.com/labs/ip-transit/begin
Attach routable public IPs to any Linux server through the Serververse™ Network Transit.
Serververse™ Network Transit is a production-grade IP transit system designed for **developers, homelab operators, and infrastructure engineers**. It lets you attach a routable public IP to any Linux-based server — even behind NAT — through an automated provisioning workflow.
Traffic is routed through the **Serververse edge network** over a secure WireGuard tunnel, giving your server direct public exposure without touching your local ISP or managing complex routing rules yourself.
> [!NOTE]
>
> Network Transit is currently in **beta**. Breaking changes may occur between minor versions.
***
## How It Works
**1. Get your install command**
Log in to the [Serververse Dashboard](https://labs.serververs.com) and navigate to **Network Transit**. Your personalised install command — including your provisioning token — is generated for you.
**2. Run it on your server**
Paste the command on your Linux server. The installer handles tunnel configuration and provisioning automatically.
**3. You're live**
Serververse provisions your tunnel on the edge network and your server receives a routable public IP.
```text theme={null}
Internet
↓
Serververse Edge Network
↓
WireGuard Transit Tunnel
↓
Your Server (with Public IP)
```
***
## What You Get
* Public IP on any server, including those behind NAT
* Token-based provisioning — no manual key management
* WireGuard tunneling, configured per your use case
* Dashboard to view your transit IPs and retrieve your install command
* Lightweight, dependency-minimal execution
* Compatible with VPS, bare metal, containers, and homelabs
***
## Use Cases
* Exposing **homelab services** with a dedicated public IP
* Hosting **game servers** (e.g. Minecraft) without ISP restrictions
* **Failover and redundancy routing** across regions
* Custom **cloud and hybrid infrastructure** networking
* NAT bypass with a **static public IP assignment**
* Advanced routing and lab experiments
***
## Choose your setup
> **[Cloud providers & HomeLab](/labs/ip-transit/tunneling)**
>
> Single routed IP for VMs on Microsoft Azure, AWS, Oracle Cloud and similar providers or to attach on your WSL, VMWare, VirtualBox or Linux Machine.
> **[Self-hosted Hypervisors](/labs/ip-transit/tunneling-hypervisor)**
>
> Route a public subnet to VMs on Proxmox VE & other hypervisors.
> **[Customer API](/labs/ip-transit/transit-api)**
>
> Manage your account and tunnels from your own scripts. Premium feature.
> **[LXC Containers](/labs/ip-transit/tunneling-lxc)**
>
> Run Serververse Transit inside an unprivileged Proxmox LXC container or route a subnet to multiple containers.
***
## Operational Notes
> [!WARNING]
>
> Always ensure **out-of-band access (IPMI, VNC, or console)** is available before running the installer. Incorrect routing may temporarily disrupt your SSH session.
* Intended for users familiar with **Linux networking concepts**
* Underlying transport mechanisms may evolve across versions
* By using this service you agree to the applicable [Terms of Service](https://serververs.com/tos) and [Privacy Policy](https://serververs.com/privacy)
# How to Start Your Minecraft Server
Source: https://docs.serververs.com/minecraft/start
Official guide to launch and manage Minecraft servers with Serververse
Launch your Minecraft server on **Serververse** in just a few steps.
## 🛒 Step 1: Purchase Your Minecraft Server
1. Visit the [Minecraft Hosting Store](https://serververs.com/minecraft)
2. Choose a plan based on your needs:
* Vanilla, Spigot, Paper, Forge, Fabric
3. Complete checkout. Your server will be provisioned instantly.
> 🛍 All purchases and renewals are managed at [store.serververs.com](https://store.serververs.com)
## 🔑 Step 2: Access Your Dashboard
1. Go to [store.serververs.com](https://store.serververs.com)
2. Open the `Dashboard` and select your Minecraft server
3. Click on **"Login to My Server"**
This will redirect you to our Panel Selector.
## 🎮 Step 3: Choose Your Game Panel
1. Visit [serververs.com/panel](https://serververs.com/panel)
2. Select **"Game Panel"** (for Minecraft, Terraria, etc.)
3. You'll be redirected to the correct server management panel
> 🔐 Use the **same email** as your Store login\
> 🛠 If you're logging in for the first time or forgot your password, click **"Forgot Password"** to reset it
## 🚀 Step 4: Start Your Server
1. Once logged in, find your Minecraft server in the list
2. Click **Start**
3. Wait a few seconds — your server will turn **Running**
> 🟢 The panel shows live usage stats, logs, startup parameters, and more.
## 🌐 Step 5: Join Your Server
1. Copy the IP address shown in your server panel
2. Open Minecraft → Multiplayer → Add Server
3. Paste the IP (e.g. `yourname.serververs.games:25565`) and join
> 📌 Use `ip:port` format if a non-default port is assigned
> [!NOTE]
>
> Need a custom domain like `yourname.com` or a free subdomain like `yourname.serververs.games`?
>
> Get a subdomain through your panel, or buy a domain via [domain.serververs.com](https://domain.serververs.com) and point it to your server.
>
> Need help? Reach out to [Support](https://store.serververs.com/tickets/create).
## ⚙️ Customize Your Minecraft Server
* Upload your world or mods via the **File Manager**
* Install plugins (Spigot/Paper) into `/plugins`
* Modify server settings (MOTD, max players, game rules, etc.)
* Set up automated tasks with **Schedules**
> 🧠 Full control via Web Console, Config Editor, and Startup Parameters
## 🧠 FAQ & Troubleshooting
### Can't login to panel?
* Visit [serververs.com/panel](https://serververs.com/panel) → Select Game Panel
* Use your **store email**
* Click **Forgot Password** if login fails
### Server won't start?
* Check the **Console Logs**
* Make sure your chosen version (e.g., Paper/Forge) is compatible
* Try reinstalling from the panel
Need more help? [Submit a support ticket](https://store.serververs.com/tickets/create)
> [!NOTE]
>
> Want DDoS protection and proxy IPs for your Minecraft server?
>
> Explore [Serververse Shield](https://serververs.com/shield) — our network-level protection system.
## 🤝 Need Help?
💬 [Join our Discord](https://discord.gg/pXmG5CuveT)\
📩 [Open a Support Ticket](https://store.serververs.com/tickets/create)
# Quickstart Guide
Source: https://docs.serververs.com/quickstart
Welcome to Serververse for this guide helps you get started in 3 simple steps.
> Whether you're launching a website, game server, or virtual machine so follow this flow to go live fast.
## Step 1: Choose & Purchase a Service
1. Visit the [Serververse Store](https://store.serververs.com)
2. Browse our offerings:
* **Web Hosting** – WordPress, WooCommerce, or CyberPanel-based shared hosting.
* **Minecraft Hosting** – Paper, Vanilla, Modded, and more.
* **Cloud VPS** – Root access with blazing-fast SSD or NVMe.
* **Enterprise/Custom** – Tailored infrastructure for scale.
3. Select your plan and complete the checkout.\
Your service will be provisioned within seconds.
## Step 2: Access Your Panel
Once your service is active:
1. Head to [serververs.com/panel](https://serververs.com/panel)
2. You'll be redirected to the correct control panel (Web, Game, or VPS)
3. Log in using the **same email** as your store account\
→ If password not set or forgotten, just use **Forgot Password**
> [!WARNING]
>
> Your panel is different from the store dashboard, Each service has its own portal: Web Panel, Game Panel, or Cloud (Proxmox).
## Step 3: Launch & Manage
After login, you'll find your server listed. You can:
* Start, stop, or restart your server
* Access logs and real-time resource stats
* Upload files via File Manager or FTP
* Add DDoS protection or subdomains
* Install apps, mods, plugins, or OS images
## Need Help?
* Join our [Discord](https://discord.gg/pXmG5CuveT)
* Or open a [support ticket](https://store.serververs.com/tickets/create)
We'll get you up and running fast.
# Shield
Source: https://docs.serververs.com/shield
# 01 · OVH VAC + Edge Firewall
The first layer is positioned at the **OVH network edge**.
OVH's Anti-DDoS infrastructure and Edge Network Firewall provide the first network-level filtering boundary before traffic reaches the Serververse infrastructure.
This layer is primarily responsible for handling unwanted traffic as early in the path as possible.
### What happens here?
```text theme={null}
Incoming Traffic
│
▼
┌─────────────────────────┐
│ OVH Network Edge │
│ │
│ Anti-DDoS / VAC │
│ Edge Network Firewall │
└────────────┬────────────┘
│
┌─────┴─────┐
│ │
Filtered Allowed
Traffic Traffic
│ │
▼ ▼
DROP Next Layer
```
The OVH layer can provide:
* Network-level DDoS mitigation
* Edge firewall policies
* Stateless traffic filtering
* Early traffic rejection
* Protection before traffic reaches the origin network
### Why the first layer matters
The earlier unwanted traffic can be discarded, the less of that traffic needs to be processed by the layers behind it.
This makes the upstream edge an important part of the overall mitigation chain.
***
# 02 · Cloudflare Magic Transit
Traffic that passes the first layer enters the second security boundary through **Cloudflare Magic Transit**.
Magic Transit provides network-layer protection for routed IP prefixes using Cloudflare's global network.
Traffic can be inspected and filtered across Cloudflare's network before clean traffic is returned toward the Serververse infrastructure.
```mermaid theme={null}
flowchart LR
A["OVH Edge"] --> B["Cloudflare Network"]
B --> C["DDoS Mitigation"]
C --> D["Advanced TCP Protection"]
D --> E["Network Firewall"]
E --> F["Clean Traffic"]
```
Cloudflare's network provides an additional globally distributed mitigation layer between the public Internet and the protected infrastructure.
### This layer can provide
* DDoS mitigation
* Network firewall policies
* TCP protection
* Traffic filtering
* Globally distributed traffic processing
* BGP-based traffic routing through the Cloudflare network
### Why add another layer?
A single upstream provider does not need to be the only filtering boundary.
With Magic Transit in the path, traffic receives another opportunity to be identified and filtered before it reaches the Serververse network.
***
# 03 · Serververse In-House Filtering
After upstream mitigation, traffic enters the **Serververse network**.
This is the final filtering layer immediately before the protected infrastructure.
Unlike upstream mitigation systems, this layer is controlled by Serververse and can apply policies specific to the protected network and workload.
```mermaid theme={null}
flowchart TD
A["Cloudflare
Clean Traffic"]
A --> B["Serververse Filtering"]
B --> C["ACL / Prefix Rules"]
B --> D["Port / Protocol Rules"]
B --> E["Rate Limiting"]
B --> F["Traffic Telemetry"]
B --> G["Custom Mitigation Policies"]
C --> H["Protected Origin"]
D --> H
E --> H
F --> H
G --> H
```
### Serververse filtering can include
* Custom ACLs
* IP and prefix filtering
* Port-based filtering
* Protocol-based policies
* Rate limiting
* Connection controls
* Traffic telemetry
* Custom mitigation rules
* Infrastructure-specific policies
This gives Serververse direct control over the final network boundary before traffic reaches the workload.
***
# What Happens During an Attack?
Shield is designed around **progressive filtering**.
When an attack occurs, traffic moves through the same layered architecture, with each layer providing an additional opportunity to discard unwanted traffic.
```mermaid theme={null}
flowchart TD
A["Attack Traffic
reaches the Internet"]
A --> B["01 · OVH VAC + Edge Firewall"]
B -->|Malicious traffic| X1["DROP"]
B -->|Allowed traffic| C["02 · Cloudflare Magic Transit"]
C -->|Mitigated traffic| X2["DROP"]
C -->|Allowed traffic| D["03 · Serververse In-House Filtering"]
D -->|Blocked by policy| X3["DROP"]
D -->|Verified / permitted traffic| E["Protected Origin"]
style X1 stroke-width:2px
style X2 stroke-width:2px
style X3 stroke-width:2px
```
The important concept is simple:
> **Traffic must pass multiple filtering boundaries before it reaches the origin.**
***
# Attack Traffic vs Clean Traffic
The architecture can be visualized as a progressive filtering pipeline:
```text theme={null}
INTERNET
│
│
┌─────────────▼─────────────┐
│ 01 · OVH EDGE │
│ │
│ VAC + Edge Firewall │
└─────────────┬─────────────┘
│
Filtered Traffic
│
┌─────────────▼─────────────┐
│ 02 · CLOUDFLARE │
│ │
│ Magic Transit │
└─────────────┬─────────────┘
│
Clean Traffic
│
┌─────────────▼─────────────┐
│ 03 · SERVERVERSE │
│ │
│ In-House Filtering │
└─────────────┬─────────────┘
│
Verified Traffic
│
┌───────▼───────┐
│ ORIGIN │
│ │
│ Game / VPS / │
│ Web / API │
└───────────────┘
```
Each stage reduces the amount of unwanted traffic that continues toward the protected workload.
***
# Defense in Depth
The main principle behind Shield is **defense in depth**.
Rather than depending on a single mitigation system, Shield places multiple security boundaries between the Internet and your infrastructure.
| Layer | Infrastructure | Primary Role |
| - | - | - |
| **01** | OVH VAC + Edge Firewall | Upstream network filtering and DDoS mitigation |
| **02** | Cloudflare Magic Transit | Globally distributed DDoS mitigation and network filtering |
| **03** | Serververse Filtering | Infrastructure-specific policies and final filtering |
| **04** | Protected Origin | Your actual workload |
Each layer operates at a different point in the traffic path.
***
# Why Three Layers?
## 1. Multiple security boundaries
If unwanted traffic passes one filtering layer, it still has to pass the next layer before reaching the origin.
## 2. Earlier traffic rejection
Traffic can be discarded upstream instead of consuming resources at the protected workload.
## 3. Global mitigation
Cloudflare provides a globally distributed network layer between the public Internet and Serververse infrastructure.
## 4. Serververse-controlled policies
The final filtering layer allows Serververse to apply policies specific to the protected infrastructure.
## 5. Better visibility
Traffic reaching the Serververse network can be observed through our own network telemetry and monitoring systems.
***
# Clean Traffic Delivery
The objective of Shield is not to block legitimate users.
The objective is to **remove unwanted traffic while allowing legitimate traffic to continue toward the protected service**.
```mermaid theme={null}
flowchart LR
A["Internet"] --> B["OVH Edge"]
B --> C["Cloudflare Magic Transit"]
C --> D["Serververse Filtering"]
D --> E["Protected Service"]
B -. "Unwanted traffic" .-> X["Dropped"]
C -. "Unwanted traffic" .-> X
D -. "Policy violation" .-> X
```
Legitimate traffic continues through the chain:
```text theme={null}
Internet
↓
OVH
↓
Cloudflare
↓
Serververse
↓
Protected Service
```
***
# Traffic Is Not Automatically Trusted
Passing an upstream mitigation provider does not automatically make traffic trusted.
Shield follows a layered approach:
```text theme={null}
┌──────────────────────┐
│ INTERNET │
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ OVH EDGE LAYER │
└──────────┬───────────┘
│
First Filter
│
▼
┌──────────────────────┐
│ CLOUDFLARE MAGIC │
│ TRANSIT │
└──────────┬───────────┘
│
Second Filter
│
▼
┌──────────────────────┐
│ SERVERVERSE NETWORK │
│ FILTERING │
└──────────┬───────────┘
│
Final Filter
│
▼
┌──────────────────────┐
│ PROTECTED ORIGIN │
└──────────────────────┘
```
This is the core idea behind Serververse Shield:
> **Three filtering layers. One protected origin.**
***
# What Shield Protects
Shield can be deployed in front of infrastructure such as:
* Minecraft and game servers
* VPS infrastructure
* Web applications
* APIs
* Dedicated servers
* Network services
* Public IP infrastructure
The exact mitigation capabilities and routing behaviour depend on the protected service and network configuration.
***
# Built for Network-Level Attacks
Shield is designed around network-level protection rather than relying only on application-level proxies.
This allows the architecture to protect services that require direct IP connectivity and protocols beyond traditional HTTP traffic.
Examples include:
```text theme={null}
L3 · Network traffic
L4 · TCP / UDP traffic
↓
Network filtering
↓
Protected infrastructure
```
For application-specific attacks, additional application-layer controls may be required depending on the workload.
***
# The Shield Pipeline
The entire architecture can be summarized in one flow:
```text theme={null}
┌─────────────────────────────────────────────────────────────┐
│ INTERNET │
└────────────────────────────┬────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ 01 · OVH NETWORK EDGE │
│ │
│ VAC + Edge Network Firewall │
│ │
│ First network filtering layer │
└────────────────────────────┬────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ 02 · CLOUDFLARE │
│ │
│ Magic Transit │
│ │
│ Global DDoS mitigation + network filtering │
└────────────────────────────┬────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ 03 · SERVERVERSE │
│ │
│ In-House Filtering │
│ │
│ ACLs · Policies · Rate Limits · Telemetry │
└────────────────────────────┬────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PROTECTED ORIGIN │
│ │
│ Game · VPS · Web · API · Network Service │
└─────────────────────────────────────────────────────────────┘
```
## One Origin. Three Filtering Layers.
Serververse Shield combines upstream network protection, globally distributed mitigation and Serververse-controlled filtering into a single layered architecture.
**Internet → OVH → Cloudflare → Serververse → Origin**
That is how Shield keeps unwanted traffic away from the infrastructure that matters.
# Web Services
Source: https://docs.serververs.com/web/index
Guides to set up, connect, and manage your Serververse web hosting.
Manage domains, hosting, and emails : all in one place.
> **[Getting Started](/web/start)**
>
> Step-by-step guide to purchase, set up, and launch your web hosting.
> **[Email](/email/index)**
>
> Use & Manage Emails with ease.