DDoS-protected Paper server hosting on our Frankfurt network, ready the moment you pay. Every plan runs
behind Minecraft-aware DDoS filtering at the edge, with Aikar's JVM flags and Paper tuning applied before you
log in. It is the Paper-specific tier of our
Minecraft server hosting, from €5.00/mo with dedicated DDR5 ECC RAM and a Pterodactyl panel.
Four Paper plans, split by RAM. Each includes the same Frankfurt network, Minecraft-aware DDoS filtering and
Pterodactyl panel; only the memory and comfortable player count change. Prices are monthly; annual billing
lowers the effective rate. Suggested player counts are our recommendation, not a hard cap.
*Suggested players are our recommendation for a moderate plugin set, not a technical limit. Real capacity
depends on plugins, world size and view distance.
Paper is a fork of Spigot built for performance. It keeps full Bukkit and Spigot plugin compatibility, then
rewrites the hot paths: asynchronous chunk loading, per-world configuration and patches for long-standing
exploits. Under a full player load it holds a higher, steadier TPS than vanilla or plain Spigot on the same
hardware.
Vanilla runs the server on largely one thread and exposes almost no knobs beyond server.properties. Spigot
added configuration and a set of entity optimisations. Paper goes further. Chunk loading and saving move off
the main thread, so a player flying into ungenerated terrain no longer stalls the tick for everyone else.
Per-world config lets you cap mob density in a crowded spawn hub while leaving a survival world untouched.
Paper also carries patches for exploits that vanilla leaves open, which matters on any public server.
Because Paper implements the Bukkit API, plugins written for Spigot run unchanged in the large majority of
cases. That is why Paper is the default for most public networks, and the base that Purpur and Folia build
on. If you are weighing the two, our
Spigot hosting page covers the plain-Spigot route; most admins pick
Paper for the extra tick headroom. The upstream project documents every patch and config key in the official
PaperMC docs.
Paper-specific tuning we apply on every node
Every Paper instance boots with Aikar's JVM flags and a tuned paper-global.yml and paper-world-defaults.yml.
Aikar's flags configure the G1 garbage collector for short, predictable pauses, which is the single biggest
win for tick stability. On top of that we set a handful of Paper keys that matter under load and under
attack.
The table lists the settings we touch and why. Exact values differ by plan and version, so shipped defaults
are marked for confirmation, not guessed at.
Setting (file)
Our value
Why
anti-xray engine-mode (paper-world-defaults.yml)
{{CONFIRM_ACTUAL_DEFAULTS}}
Obfuscates buried blocks so x-ray clients see noise, without the CPU cost of hiding the whole world.
Keeps the loaded chunk count inside each plan's RAM budget.
You keep full control: every value is editable from the Pterodactyl file manager, so change any of them and
restart.
DDoS protection built for Minecraft
Every Paper plan sits behind 3.2 Tbps of always-on L3, L4 and L7 mitigation at our Frankfurt edge, with
detection under one second and no traffic rerouting. For game traffic we run deep packet inspection tuned for
the Minecraft protocol, so malformed and forged packets are dropped upstream before they reach your server.
There is no separate DDoS add-on to buy.
This is infrastructure-layer protection: it absorbs volume and drops junk packets at the network edge.
Application-layer defence, such as anti-bot plugins and proxy hardening, still belongs to your server
software; the full walkthrough is in our guide on
how to protect a Minecraft server from DDoS. Hosting
Paper elsewhere? Our
remote DDoS protection for Minecraft
routes your box through the same Frankfurt edge over a GRE or WireGuard tunnel instead of migrating the
world.
Panel and features
You run Paper from Pterodactyl, the same panel behind our whole Minecraft range. Swap the Paper build or
Minecraft version with one click, restore a bad update from a snapshot backup in a single click, and hand out
a free subdomain to players. Full SFTP access is on every plan.
One-click jar and version swap — move between Paper builds and Minecraft versions (Java 1.8.x to the
latest 1.21.x) without editing a config file.
Snapshot backups with single-click restore — a broken plugin update is one click from rolled back.
Free subdomain — a clean address for players, plus an optional native 25565 port so they connect
without typing one.
SFTP and subusers — drop in plugins over SFTP, and give staff granular permissions without sharing the root login.
Get started in 3 steps
Setup is instant, with no manual provisioning wait. Pick a plan and the server is live on the Frankfurt
network behind DDoS filtering within moments of payment. From there it is three steps to a running Paper
server.
Choose a plan by RAM and order it. Your Paper server is provisioned automatically behind the protected edge.
In Pterodactyl, select the Paper build and Minecraft version you want, then start the server. Aikar's flags
and our Paper tuning are already applied.
Upload plugins over SFTP, set your subdomain and share the address. Protection is already on.
Paper, tuned and protected, in minutes
Order a plan and your Paper server boots on the Frankfurt network behind 3.2 Tbps of always-on filtering,
with Aikar's flags already applied. From €5.00/mo.
Yes. Paper reads Spigot and vanilla worlds directly, so you drop the world folder in place, switch the
jar to Paper and start. Because Paper implements the Bukkit API, your Spigot plugins carry over too. Take
a snapshot backup first so you can roll back if a plugin misbehaves on the new build.
Will any plugins break on Paper?
Very few. Anything written against the Bukkit or Spigot API runs unchanged. Breakage is limited to
plugins that hook Spigot internals (NMS) for one specific server version; those need a build that matches
your Minecraft version. Update such plugins to their Paper-compatible release before you switch.
How many players per GB can Paper handle?
There is no fixed number; it depends on plugins, world size and view distance far more than on RAM alone.
As a recommendation we map RAM to players like this: up to ~10 on 4 GB, ~25 on 8 GB, ~60 on 16 GB and
~120+ on 32 GB, for a moderate plugin set. A heavy plugin stack lowers those figures. Treat them as
starting points, not caps.
Can I switch to Purpur or Folia later?
Yes for Purpur, with a caveat for Folia. Purpur is a Paper fork whose config is a superset of Paper's, so
you switch the jar in Pterodactyl and your world and most plugins keep working. Folia re-threads the
server for very large player counts and drops compatibility with most current plugins, so treat a move to
Folia as a rebuild, not a jar swap.
Launch a protected Paper server
Instant setup on the Frankfurt network, from €5.00/mo with a 14-day money-back guarantee.