Run your servers, keep them up.

The panel, the protection, and the servers themselves. 121 pages, written against what the product actually does.

Browse by topic. 13 sections, from your first sign-in to hardening a server.

5 pages

Getting started

What Clouduxe is, how to get in, and how the panel is laid out.

5 pages

Buying a server

Choosing a plan, ordering, paying, and waiting for it to build.

15 pages

Your servers

Power, console, reinstalls, SSH keys, networking and plan changes.

11 more pages
13 pages

DDoS protection

How Clouduxe Prism filters traffic, and every setting you can tune.

9 more pages
9 pages

Billing

Invoices, payments, wallet credit, tax and renewals.

5 more pages
10 pages

Your account

Profile, security, notifications and giving someone else access.

6 more pages
3 pages

Support

Getting help, and checking whether the problem is on our side.

28 pages

Game servers

Setting up, tuning and running game servers on Clouduxe.

24 more pages
10 pages

Linux

Running and securing a Linux server, from first login to day-to-day administration.

6 more pages
4 pages

Windows

Running a Windows server, Remote Desktop, and keeping it locked down.

5 pages

Networking

Diagnosing latency, packet loss and routing, and reading the results properly.

4 pages

Security

Hardening a server, and what to do if one is compromised.

10 pages

Media Storage

fxvault Media: hosting your FiveM server's screenshots, photos, video and voice notes.

6 more pages

Two layers stand in front of every server. Floods are absorbed upstream. What is left meets Prism on the host, the layer you configure.

How protection works
  1. Network edge

    Volumetric floods absorbed upstream

    Removed here

    Amplification and spoofed floods

  2. Clouduxe Prism

    Per-packet filtering on the host

    Removed here

    Bad protocol, bad behaviour, rate abuse

  3. Your server

    Only traffic that passed both layers

    Nothing removed

    This is what reaches your application

Traffic reaches your server only after passing both layers. The edge handles raw volume. Prism is the layer you configure, and the one that understands your game’s protocol.

Need a server, or a hand with one?

Pick a plan to deploy a server, or open a ticket in the panel. Support runs 24/7/365.