SecureVM is now Evorxa.comWhat this means for you

ddos protection · measured, not claimed

Floods stop at the edge. Your box never hears them.

Three layers in front of every server. Scalebit absorbs volumetric layer 3/4 floods on the network, GGProtect's layer 7 WAF blocks HTTP floods, bots and injection attempts, and Shield, our own firewall, applies your rules before anything reaches your server. Every figure on this page is read from our own edge.

Deploy behind ShieldSee plans
  • UDP
  • SYN
  • DNS
  • Real visitor
  • HTTP
  • Bots
  • SQLi
ScalebitAnti-DDoS · Layer 3/4Floods dropped
GGProtectWAF · Layer 7Attacks blocked
Your serverShield firewallpassed
Gbps absorbed
4,791.25
Requests blocked
37,296,550
last 30 days, at the edge

How Shield works

Absorbed on the network

Volumetric floods meet multi-Tbps of scrub capacity on the ScaleBit network, before anything reaches an uplink you share. There is nothing to switch on and nothing to size.

Filtered per request

Whatever survives scrubbing is judged at the edge. Drop a country, a network, an address range, a protocol or a port, and it stops there rather than on your box.

On from the first hour

Shield ships with every plan. No separate SKU, no add-on to remember, and no traffic surcharge on the day somebody points a botnet at you.

the console

This is the screen you get.

Not a mockup of a product we are planning. Three tabs on every instance, from the first hour, on every plan.

console.evorxa.com/instances/…

DDoS protection

Mitigation across every protected address and endpoint.

Traffic during mitigation

DroppedServed

Requests blocked

37,296,550

Attacks mitigated

312

Peak absorbed

374

Gbps

Average peak

15.36

Gbps

Median to clear

1m 37s

Attack vectors
VectorAttacksShare
UDP Flood25834.3%
SYN Flood12416.5%
ACK Flood10513.9%
FIN Flood587.7%
RST Flood567.4%
Handshake445.8%
ICMP Flood374.9%
DNS Amp243.2%
NTP Amp233.1%
DNS Flood101.3%
SYN ACK Flood70.9%
DNS Amplification40.5%

The tiles and the vector table are live platform figures. The traffic curves are an example: shape belongs to one instance during one attack, and there is nothing to average across customers.

the path a request takes

Everything arrives at the edge. Only what should reach you leaves it.

Floods and legitimate requests hit the same address. Scalebit drops the volumetric layer 3/4 floods, GGProtect filters layer 7 attacks, and Shield applies your firewall rules, so your uplink only carries the traffic you wanted.

dropped
passed
dropped
Evorxa edge
Your server

inbound → Evorxa edge → Your server

stage by stage

Three stops, and only one of them is yours.

The same journey without the geography: everything lands on the edge, the edge decides, and one clean stream continues to your server.

  1. 01

    inbound

    Volumetric floods meet multi-Tbps of scrub capacity on the ScaleBit network, before anything reaches an uplink you share. There is nothing to switch on and nothing to size.

  2. 02

    Evorxa edge

    Whatever survives scrubbing is judged at the edge. Drop a country, a network, an address range, a protocol or a port, and it stops there rather than on your box.

  3. 03

    Your server

    Rules apply to the address, so every service behind it inherits them at once. Drop a range for SSH and it is dropped for everything else too.

01 · ddos protection

Absorbed before it reached an uplink.

Floods are scrubbed on the network, and whatever survives that is filtered per request at the edge. These are the platform's own figures.

4,791.25Gbps

312 attacks scrubbed against protected addresses. Your server keeps serving; it never hears the flood.

The headline adds up every recorded attack's own peak rate. It is a sum of crests, not an integral of traffic over time.

One address, every service behind it.

Protection belongs to the address, not to a protocol. Anything listening on a protected IP inherits it.

Websites and APIs

Request floods are filtered before they reach your origin. Rules read the path, the method and the source, so a bad country or a scraping ASN stops at the edge while real visitors carry on.

TCP and UDP services

Game servers, databases, VPN endpoints, anything on a port. Mitigation is not limited to HTTP, so a UDP amplification flood is handled the same way an HTTP one is.

The whole box

Rules apply to the address, so every service behind it inherits them at once. Drop a range for SSH and it is dropped for everything else too.

Visible while it happens

Every attack is recorded with its vector, its peak and how long it ran, in your console as it is mitigated rather than in a monthly report.

Already carrying production traffic.

  • AutoComputer Trading
  • Cointo
  • Cranl
  • Eduvera
  • Envkit
  • Stockship

03 · plans

Shield ships with every plan. No separate SKU, no traffic surcharge on the day someone points a botnet at you. Pick a size; the edge is already in front of it.

Pricing

Clear plans. Choose what you need.

Compare resources and choose a plan for your game server, business apps or next project. Switch billing cycles to see prepaid discounts.

Plan family
Billing cycle
Currency
Plan view

Budget VMs plans
PlanPrice / moDeploy
Nano1 core2 GB30 GB500 Mbps
MicroMost popular2 cores4 GB40 GB500 Mbps
Mini3 cores6 GB50 GB500 Mbps
Standard VMs plans
PlanPrice / moDeploy
TinyMost popular4 cores8 GB100 GB1 Gbps
Large4 cores10 GB150 GB1 Gbps
XLarge6 cores16 GB200 GB2 Gbps
2XLarge8 cores20 GB300 GB2 Gbps
3XLarge10 cores32 GB400 GB2 Gbps

Recommended for game servers. Dedicated high-frequency Ryzen cores for FiveM, Minecraft and other game servers.

High-Frequency VMs plans
PlanPrice / moDeploy
Silver4 cores16 GB200 GB2.5 Gbps
GoldMost popular6 cores24 GB300 GB2.5 Gbps
Platinum8 cores32 GB400 GB2.5 Gbps
Diamond10 cores48 GB600 GB2.5 Gbps
Emerald12 cores64 GB800 GB2.5 Gbps
  • Cancel anytime, prorated refund.
  • Shield DDoS protection included
  • Full root access
  • AI agent usage billed separately

Tailored to your team

Easy to use for one server or a whole fleet: same dashboard, same API.

Deploy queue

Eygelshoven, NL
fivem-cityWindows Server 2022 · High-Frequency · PlatinumBuilding
api-workerUbuntu 24.04 · Standard · TinyDeployed
mc-survivalDebian 12 · High-Frequency · GoldDeployed
web-prod-2Ubuntu 24.04 · Standard · LargeDeployed
Representative sample of a deploy queue

Fits into your existing workflows

Provision from the dashboard or manage servers from your scripts through the API. Choose your OS and resources, and use the AI agent for help with setup and operations.

  • Dashboard
  • REST API
  • AI agent
  • Telegram

One panel for every server you run

Shared cores for websites and everyday workloads, or dedicated high-frequency cores for more demanding tasks. Manage both from one dashboard.

  • Shared cores
  • Dedicated cores
  1. 1Start with one serverPick a plan and an OS in the dashboard. It boots in under a minute.
  2. 2Automate the routineScript it with the API, or ask the AI agent to install and configure software.
  3. 3Grow into a fleetAdd servers as you need them and manage them all from the same panel.

Why teams choose Evorxa

Less time fixing servers. More time building.

What usually goes wrong, and what you get here instead.

Elsewhere

  • A traffic flood takes your server offline
  • Pages and games lag at peak time
  • You wait hours for a support reply
  • The renewal price is much higher than the first bill
  • A bandwidth cap stops you mid-month
  • A surprise invoice at the end of the month

With Evorxa

  • Shield drops floods on the network, before they reach you
  • NVMe disks and dedicated Ryzen cores on High-Frequency plans
  • The AI agent checks your server and fixes it with you, right away
  • The price you see is the price you pay at renewal
  • Unmetered bandwidth on Standard plans
  • Prepaid billing. You always know what you pay

questions

Before you point a record at us.

  • Is DDoS protection an add-on?

    No. Shield ships with every plan, on from the first hour. There is no separate SKU to buy, no add-on to remember to enable, and no traffic surcharge on the day somebody points a botnet at you.

  • How large an attack can you actually absorb?

    Volumetric floods meet multi-Tbps of scrub capacity on the ScaleBit network, before anything reaches an uplink you share. Every figure on this page is read from that edge rather than a datasheet, including the largest attack we have absorbed so far.

  • Does this only cover websites?

    No. Protection belongs to the address, not to a protocol, so anything listening on a protected IP inherits it: game servers, databases, VPN endpoints, anything on a port. A UDP amplification flood is handled the same way an HTTP one is.

  • What do I have to configure?

    Nothing to switch on and nothing to size. Scrubbing, edge filtering and the rule editor are active from the moment the instance exists. You only touch the firewall if you want to narrow who can reach it.

  • How quickly do firewall rules take effect?

    Seconds. Drop a country, a network, an address range, a protocol or a port and it stops at the edge rather than on your box. Rules apply to the address, so every service behind it inherits them at once.

  • Am I billed for attack traffic?

    No. Traffic that never reaches your server is not your traffic. An attack day costs the same as a quiet one, which is the whole reason mitigation belongs on the network rather than on the box you are paying for.
  • Scrubbing on from the first hour
  • No traffic surcharge on an attack day
  • Rules push in seconds
  • Filtered per request at the edge
  • Every figure read from our own edge

Put your next server behind the same edge.

Scrubbing, edge filtering and the rule editor are on from the first hour, on every tier.

Deploy behind ShieldHow Shield works