Pay for twenty-four months and save 17% or moreOn every plan, pick the 24-month term when you order
Skip to main content

Modpack Server Hosting

Run RLCraft, ATM10, Pixelmon, Create, or any other modpack on hardware that can actually handle it. NVMe storage, dedicated vCPU cores, and enough RAM to keep tick rates stable.

A hopper, a dispenser, an observer and a piston in a row on smooth stone
A hopper, a dispenser under a redstone lamp, an observer and a piston, drawn from the game's own block textures. No block from any pack is in this picture: those blocks do not exist in the game's own files.

Why Modpacks Need Dedicated Resources

A vanilla Minecraft server can run on 2 GB of RAM without breaking a sweat. Modpacks are a completely different story. When you load 150, 300, or 400+ mods into a single server, every part of the hardware gets pushed harder. The JVM needs more heap memory, the CPU spends more time on block interactions and entity AI, and the disk has to read and write larger chunk files every time a player explores new terrain.

Shared hosting plans that advertise “unlimited” RAM almost always oversell their nodes. Your server ends up competing with dozens of others for the same physical CPU and the same disk throughput. That is fine for a small Paper server, but modpacks punish it. You get lag spikes during world generation, freezes when players open large inventories, and TPS drops that make the game unplayable once a few people start automating things.

Dedicated resources solve the problem at the hardware level. When your server has 8 or 12 GB of RAM that belongs entirely to your instance, there is no neighbor to steal cycles from you. When storage is NVMe-based, chunk generation and region file writes happen faster than the server can queue them. And when you have guaranteed vCPU cores, the tick loop stays at 20 TPS even when multiple players are exploring in different directions.

That is the approach we take at Astroworld. Every plan comes with dedicated vCPU cores, NVMe SSD storage as the standard, and a fixed amount of RAM that no other server on the node can touch. You also get full access to a Pterodactyl-based panel with a file manager, so uploading modpacks and adjusting server properties is straightforward.

Forge and Fabric Support

Most popular modpacks run on Forge, the mod loader that has been the standard since the early days of Minecraft modding. Forge handles the heavy lifting of loading hundreds of mods, resolving dependencies, and patching the base game code so that everything works together. RLCraft, All The Mods 10, Pixelmon, and Vault Hunters all use Forge.

Fabric is the newer alternative. It is lighter-weight and tends to load faster, but its mod ecosystem is smaller. Packs like Fabulously Optimized and some versions of Create use Fabric. If your pack ships with a Fabric server JAR, you can run it on any of our plans the same way you would run Forge.

Either way, the setup process is the same. Upload your server pack through the panel's file manager or via SFTP, set the correct startup JAR, and adjust the RAM allocation in the startup parameters. If you are new to modded servers, our modpack installation guide walks through every step.

Every Pack on This Page, Side by Side

Memory per pack and the smallest plan it still fits in, both read from the same list the cards above use.
ModpackMemoryLoaderSmallest plan that fits
RLCraft6 - 8 GBForgeStarter (8 GB)
All The Mods 108 - 12 GBNeoForgeStandard (12 GB)
Pixelmon4 - 6 GBForgeStarter (8 GB)
Create4 - 6 GBForge or FabricStarter (8 GB)
SevTech: Ages6 - 8 GBNot documented hereStarter (8 GB)
Vault Hunters8 GB+Not documented hereStarter (8 GB)

Questions About Modpack Servers

How far apart are these packs in memory?

Further than most people expect. Pixelmon is listed at 4 - 6 GB and All The Mods 10 at 8 - 12 GB, and the plan that covers the first one is Starter while the second needs Standard. Picking by pack rather than by habit is the whole reason the table is there.

Does giving a modpack more RAM make it run faster?

Only up to the point where it stops running out. Past that, memory does nothing for the tick rate: a pack that drops TPS because hundreds of machines are working every tick needs processing time, not more gigabytes.

My pack is not in this list. What now?

Look at what the pack itself recommends and match that against the memory column here. The numbers on this page are the ones we host these packs on; a pack of comparable size behaves comparably.

Can I move to a bigger plan once the pack grows?

Yes, and that is the usual path with a kitchen-sink pack. The list runs from Mini at 4 GB up to Dedicated at 96 GB, so there is room above whichever tier you start on.

Plans start at 8 GB RAM and scale up to 96 GB. Pick the one that matches your modpack and player count.