Clouduxe rents servers and filters the traffic that reaches them. Everything you
buy, run, and pay for sits in one place: the panel at
dash.clouduxe.com.
Cloud VPS is a virtual server. You get a machine of your own with root or
Administrator access, and the panel gives you power controls, a browser console,
reinstalls, and SSH keys for it. It suits anything you want to administer
yourself, such as a game server or an application server.
Dedicated servers are whole machines rather than a share of one. They are
managed with the same panel controls as a VPS, described in
Your servers.
DDoS-Protected Proxy is sold under DDoS protection. It is protection
bought as a product in its own right, for when what you need is filtered traffic
rather than a machine to administer. A standalone protection subscription has no
machine behind it, so the panel hides the machine controls for it.
Which region a server runs in is part of the plan you pick, not a setting you
change afterwards. See Choosing a plan.
Traffic is filtered in two layers before your service ever answers it.
The first layer is upstream, at the network edge. It removes flood traffic on the
way in, before it reaches the machine your service runs on.
The second layer is Clouduxe Prism, running at the server itself. It judges the
packets that get through against the rules you set for that server: which ports
are open, which protocol each one speaks, packet-rate ceilings, and any source
addresses you have blocked or allowed. A stack of behavioral, timing, and
protocol checks runs automatically on every allowed port, and a few of them can
be switched off per rule if a legitimate client trips one.
You control the second layer from the Firewall tab on the server, and you
read what both layers removed on the Attacks tab, where it is enabled for
your server. The Attacks tab folds edge drops and Prism drops into one total
rather than splitting them by layer.
Two layers stand between the internet and your service. The network edge removes floods on the way in; Clouduxe Prism, which you set on the Firewall tab, judges what is left against your rules and its automatic checks. What either layer removed is counted together on the Attacks tab. Illustration.
The panel is the whole customer surface. From it you order and pay for a service,
power it on and off, open a console, reinstall it, manage SSH keys, write
firewall rules, read attack history, settle invoices, and open support tickets.
The path from sign-up to a running server. Steps 1 to 3 are covered in Getting started and steps 4 to 8 in Buying a server. Sign-up does not sign you in, and checkout will not finish without a saved billing address, so those two are worth knowing before you start. Illustration.
