Minecraft Hosting Infrastructure Upgrade: NVMe Storage, DDoS Protection & Smarter CPU Power
We've upgraded every Minecraft server on Oryzen: enterprise NVMe storage, OVHcloud Anti-DDoS with a Layer 7 Game Firewall, a new CPU burst system, and better defaults on every plan — at no extra cost.
| Singapore | Frankfurt, Germany | Mumbai, India |
|---|---|---|
| Intel Core i7-7700K | Intel Xeon E-2288G | Intel Xeon E-2386G |
| Intel Xeon E-2388G | Ryzen 5 5600X | Ryzen 5 3600X |
| AMD EPYC 4244P | AMD EPYC 9124 | Ryzen 7 5800X |
| Ryzen 7 5700G | Ryzen 9 9950X3D | AMD EPYC 4244P |
| Ryzen 9 7950X3D | — | AMD EPYC 4344P |
| — | — | Ryzen 9 5950X |
| — | — | AMD EPYC 7C13 |
Pricing is identical across all three regions — pick whichever is closest to your player base, since network distance affects perceived lag more than which exact CPU you land on.
Picking Your CPU and Checking Stock
On the billing page, a dropdown shows which CPUs are currently available at each location, along with live stock for that node. The Intel i7-7700K stays in the lineup because its lower core count suits small servers well — but it won't appear as an option for large allocations. A 24 GB plan expecting real player load, for example, won't be offered the i7-7700K on that node even if RAM is technically free, since that CPU isn't built to carry that kind of load. If the CPU you want is out of stock on a node, you can join a queue for it right from your panel. Once a matching node opens up, your server transfers over automatically — no manual request needed.
Smarter CPU Power, With a Fair-Use Safeguard
We've moved away from strict, low, fixed CPU limits. A hard ceiling works fine most of the time — but it falls apart exactly when you need extra power most: world generation, modpack loading, or a sudden wave of players joining at once. Under the new system, your server can automatically draw on extra CPU power whenever it genuinely needs it, instead of hitting a wall right when things get busy. Think of it as spare capacity held in reserve for the moments that actually matter — a big new area loading in, or a rush of players logging in together. That extra power is meant for real spikes, not for running something non-stop at full load all day. So there's a simple fair-use safeguard running quietly in the background, there to protect the node you're sharing with other servers — not to interfere with normal gameplay. If a server keeps pushing an extremely heavy task non-stop for a long stretch (like pre-generating enormous amounts of terrain with a tool such as Chunky), instead of using the extra power for short spikes, the system notices and brings that server back to its normal, steady speed for 24 hours. It returns to normal automatically after that — no action needed from you. If this happens to you by mistake — a plugin or world-generation tool ran longer than intended — open a ticket and tell us what happened. We're glad to take a look and help sort it out. In short: extra CPU power when you genuinely need it, with a simple fairness check running in the background to keep the node stable for everyone sharing it.
Better Defaults on Every Plan
Standard across the entire lineup, from Copper to Beacon, with no add-ons required:
| Included | Details |
|---|---|
| 2 Backups | Manual/scheduled backups, available now. Custom per-slot scheduling (e.g. Backup 1 at 12 AM, Backup 2 at 12 PM) is coming soon to the panel. |
| 5 Additional Ports | For proxy setups, sub-server ports, or plugin-based services. |
| 3 MySQL Databases | Enough for most plugin-heavy setups. Need more? Open a ticket and tell us why — we'll add them. |
Server Splitting
A split lets you divide your plan's resources to run fully independent, separately manageable child servers directly inside your Pterodactyl panel. It's fully flexible: when you create a split, you choose exactly how much RAM, CPU, disk, and how many ports go to it, drawn from your parent server's pool. You can edit these allocations later. Splits use your existing plan resources rather than adding new ones — they suit lighter, plugin-driven sub-servers better than a second full-scale world.
- Gold Plan: 1 Server Split
- Lapis Plan and above: up to 2 Server Splits
Full Pricing
All prices in INR. Pricing hasn't changed with this upgrade — existing customers get the new storage, security, and CPU system automatically, at the price they're already paying.
| Plan | RAM / Storage | 1 Month | 3 Months | 6 Months | 1 Year | 2 Years |
|---|---|---|---|---|---|---|
| Copper | 2 GB RAM / 25 GB NVMe | ₹399.36 | ₹1,137.76 | ₹1,797.12 | ₹3,394.56 | ₹6,389.76 |
| Iron | 3 GB RAM / 35 GB NVMe | ₹478.40 | ₹1,635.92 | ₹3,099.20 | ₹5,855.20 | ₹11,021.92 |
| Gold | 4 GB RAM / 45 GB NVMe / 1 Split | ₹667.68 | ₹1,903.20 | ₹3,605.47 | ₹6,810.34 | ₹12,819.46 |
| Lapis | 6 GB RAM / 65 GB NVMe / 2 Splits | ₹936.00 | ₹2,666.98 | ₹5,054.40 | ₹9,545.95 | ₹17,969.95 |
| Redstone | 8 GB RAM / 85 GB NVMe / 2 Splits | ₹1,179.36 | ₹3,360.86 | ₹6,367.30 | ₹12,028.22 | ₹22,642.46 |
| Quartz | 10 GB RAM / 100 GB NVMe / 2 Splits | ₹1,422.72 | ₹4,054.75 | ₹7,681.44 | ₹14,510.50 | ₹27,314.98 |
| Emerald | 12 GB RAM / 120 GB NVMe / 2 Splits | ₹1,662.34 | ₹4,737.41 | ₹8,975.62 | ₹16,954.08 | ₹31,915.10 |
| Diamond | 16 GB RAM / 160 GB NVMe / 2 Splits | ₹2,171.52 | ₹6,188.83 | ₹11,724.96 | ₹22,148.26 | ₹41,691.94 |
| Obsidian | 20 GB RAM / 200 GB NVMe / 2 Splits | ₹2,658.24 | ₹7,575.36 | ₹14,353.25 | ₹27,111.55 | ₹51,035.71 |
| Netherite | 24 GB RAM / 240 GB NVMe / 2 Splits | ₹3,111.26 | ₹8,867.04 | ₹16,799.33 | ₹31,732.90 | ₹59,734.27 |
| Bedrock | 28 GB RAM / 280 GB NVMe / 2 Splits | ₹3,541.82 | ₹10,093.82 | ₹19,123.10 | ₹36,124.61 | ₹67,999.78 |
| Beacon | 32 GB RAM / 320 GB NVMe / 2 Splits | ₹4,051.01 | ₹11,545.25 | ₹21,872.45 | ₹41,317.54 | ₹77,776.61 |
Quick Answers
Will my server lag? The two most common causes of lag — slow storage during chunk loading/saving, and not enough CPU during busy moments — are exactly what this upgrade targets. NVMe removes the storage bottleneck, and the new CPU system gives you real extra power instead of hitting a hard wall during world generation or a player rush.
Why did you switch back to NVMe after moving to SATA? The move to SATA didn't deliver what we expected. Admins still had to pre-generate terrain the same way as on NVMe, so it wasn't actually less work — and on large, heavily explored worlds, SATA's limits started causing real lag. NVMe fixes that properly, so we've moved back, at no extra cost to you.
Java or Bedrock? Both. You choose the egg for your server — Java or Bedrock — at deployment, and can run either on any plan.
What happens if I hit the fair-use safeguard? It only kicks in if a server runs something extremely heavy, non-stop, for a long stretch — not from normal gameplay or short spikes. If it triggers, your server goes back to its normal, steady speed for 24 hours, then returns to normal on its own. If it happened by mistake, open a ticket and let us know — we're glad to help.
What's Next
We're continuing to convert the remaining nodes to U.3 NVMe, and rolling out per-slot backup scheduling to the panel over the coming weeks. If there's something specific you'd like to see next — a region, a feature, a plan size — let us know through any of the channels below.
Support
Questions about sizing your plan, picking a region, or anything in this update:
- WhatsApp — bottom-left widget on the site, for a direct chat.
- Live chat — bottom-right widget, for a quick reply without leaving the page.
- Discord — join our server for community support and updates.
- Support ticket — open a ticket for account-specific or billing requests.
Ready to deploy or upgrade an existing server: View Minecraft Hosting Plans
Thank you for choosing Oryzen Hosting.