What the ARM64 build really is, when it makes sense, and how to move a factory off a Raspberry Pi or ARM box onto native x86-64 Ryzen cores.

Select from our wide range of optimized game servers. Each server is configured for maximum performance and comes with DDoS protection.







Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Bronze 4GB | 1–5 players, fresh vanilla mapEnough memory for a new map; translation still costs CPU, so consider the standard server. | 4 vCore Ryzen 9950X · 4 GB DDR5 6000MHz · 50 GB NVMe SSD Samsung 990 PRO | ₺240.00/mo |
| Silver 6GB | Saves moved off a Pi, mid-gameComfortable headroom for a save brought over from an ARM board with its mods. | 4 vCore Ryzen 9950X · 6 GB DDR5 6000MHz · 60 GB NVMe SSD Samsung 990 PRO | ₺345.00/mo |
| Gold 8GB | Late game or several Space Age planetsRecommended once multiple surfaces run; native x86 gives the same memory more speed. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | Longer mod listsCovers mod memory plus box64's translation overhead with room to spare. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | Overhaul packsHeavy mods under translation hit UPS first; weigh the standard server seriously. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | Very large modded savesMore vCores won't offset translation cost in a single-threaded simulation. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | Far beyond what one map needsExceeds what a single Factorio save uses; rarely sensible under emulation. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
What actually differs between the ARM64 template and a native Factorio server, and what stays exactly the same.
The Ryzen 9 9950X runs Factorio's official x86-64 binary directly; the standard listing skips translation entirely, and that is where single-thread UPS is decided.
The ARM64 template starts Factorio as box64 ./bin/x64/factorio, translating x86-64 instructions on the fly for ARM CPUs like those in single-board computers and ARM cloud servers.
BOX64_DYNAREC settings such as SAFEFLAGS, BIGBLOCK, CALLRET and FASTROUND trade translation speed against accuracy, which matters in a deterministic game like Factorio.
Because both templates run the same x86-64 Factorio build, a save created on a Pi under box64 opens on native hardware as-is, mods and all.
Single-board servers often save to SD cards or USB drives; NVMe storage noticeably shortens the autosave freeze that grows with every expansion of the factory.
Not sure which template fits? Our support team answers before and after purchase, around the clock, by ticket, Discord, WhatsApp, phone or live chat.
Factorio ARM64 server hosting at TheCrewHost is listed from ₺240.00 ($6.00) a month, and before you order, here is the honest picture. Wube publishes the Factorio headless server only for x86-64 Linux, so the ARM64 template runs that same binary through box64, a translation layer that lets ARM processors execute x86-64 code. Our game servers in İstanbul use AMD Ryzen 9 9950X CPUs, which are x86-64 themselves, so the standard Factorio server runs on them natively with no translation involved. For most people, especially anyone moving a factory off a Raspberry Pi or an ARM cloud instance, the standard plan is the better buy, and your saves carry over unchanged.
ARM64, also called AArch64, is the processor architecture found in Raspberry Pi 4 and 5 boards, many ARM cloud servers and Apple Silicon Macs. Factorio's official headless server, however, is only published for x86-64 Linux; the download page offers a single headless build, and it is x64. There is no native version for ARM Linux servers.
The ARM64 template bridges that gap with box64, an open-source translator. Rather than launching ./bin/x64/factorio directly, it launches box64 and hands it the Factorio binary, and box64's dynamic recompiler (dynarec) converts blocks of x86-64 code into ARM64 code while the game runs. Six BOX64_DYNAREC variables are exposed in the panel so the translation can be tuned.
Everything above that layer is ordinary Factorio: the same server-settings.json, map-gen-settings.json and map-settings.json, the same mods folder and mod-list.json, the same saves folder and the same default UDP port, 34197. To a player, an ARM64 server looks just like any other Factorio server.
On TheCrewHost, pick the standard Factorio server unless you have a specific reason not to. Our game servers are AMD Ryzen 9 9950X machines, and that CPU is x86-64, the very architecture Factorio's headless build targets. Running natively means there is no translation step at all, and Factorio is the kind of game where that step hurts: most of its simulation runs on one thread, so any overhead lands straight on UPS.
Accuracy is the other factor. Factorio multiplayer is deterministic, and every client has to compute the same result as the server on every tick. box64 is a mature project and the template offers settings that balance speed against correctness, yet a native binary removes that whole category of risk from the start.
Both listings cost the same and share the same 7 plans, so choosing ARM64 saves you nothing. If you still want this template, say to mirror a setup you also run on ARM hardware, message our support team before ordering and we will look at it together. Everyone else gets more out of the standard server.
Moving is mostly copying files, because the save format doesn't care which CPU produced it. On the old machine, type /server-save in the console, stop the server, and gather the save .zip from the saves folder, the whole mods folder including mod-list.json, and data/server-settings.json. If you promoted admins, take server-adminlist.json as well; it usually sits in the server's main directory.
On TheCrewHost, upload the save into the saves folder under the name set in the Save Name variable, replacing the generated one, and copy the mods folder across over SFTP. Instead of overwriting server-settings.json wholesale, carry your visibility, verification and pause preferences over by hand, and put name, slots, password, username and token into the panel variables, since those get written into the file on every start.
Finally, confirm the Factorio version is the same as, or newer than, the one the save came from, start the server and watch the console load the map. Players only need the new IP and port.
They decide how aggressively box64 translates code, and on ARM hardware they are the first place to look when Factorio misbehaves. The template ships with BOX64_DYNAREC_SAFEFLAGS, BIGBLOCK, FORWARD, CALLRET, FASTROUND and ALIGNED_ATOMICS. Broadly speaking, bigger translated blocks, call and return shortcuts and relaxed flag handling make translation faster, while safer flag handling and precise floating-point rounding keep results closer to what real x86-64 hardware would produce.
For Factorio that balance is not an academic detail. In a deterministic lockstep game, the server and every client have to agree on each calculation; if translated maths drifted even slightly, players would see desyncs.
On our x86-64 hardware, the standard server needs none of this tuning, which is one more reason we steer most customers there. If you do run the ARM64 template and see crashes or desync reports, change one variable at a time, write down the result, and keep a backup of the save before each test.
Factorio's memory needs are the same whichever template you pick, with a little extra on the ARM64 side for box64's own translation cache. A fresh vanilla or Space Age map for a few players fits in 4 GB. Several Space Age planets or a few dozen mods call for around 8 GB, and large overhaul packs are where 12–16 GB earns its price.
The CPU is what really separates the two. Per-core speed sets how big a factory can grow before UPS falls below 60, and translation eats into exactly that budget. A factory that was already straining a small ARM board will feel the move to native Ryzen 9 9950X cores; the same factory running under translation keeps carrying the overhead.
The extra vCores on bigger plans add little to a single Factorio map in either case. Choose the plan for memory, and let your choice of template decide how much of the CPU's speed actually reaches the game.
Without an ARM-specific reason, order the standard Factorio server instead, which runs natively at the same price; if you want the ARM64 template, talk to support first.
Bronze 4GB is enough for a new map; for a modded save moved off a Pi or several Space Age planets, look at Gold 8GB and above.
Once payment is confirmed, the Factorio headless build downloads and default settings files are created; console, file manager and backups live at gamepanel.hostingmerkezi.net.
Run /server-save on the old server, then upload the save zip, the mods folder and server-adminlist.json over SFTP, naming the save after the Save Name variable.
Enter server name, slots, password, factorio.com username and token; only change the BOX64_DYNAREC values if you see a problem, and then one at a time.
Watch the map load in the console, make yourself admin with /promote, and send players the new IP and port for Connect to address.
Questions about the ARM64 template, box64 and moving a factory off ARM hardware.
Our İstanbul datacenter runs on Ryzen 9 hardware, delivering low latency to players in Türkiye and good connectivity to Europe, the Middle East and the Caucasus.
Turkey
Everything your project needs — from game servers to VPS, dedicated servers, web hosting and Discord bot hosting.
Connect with our community of gamers and developers
Get instant support, share experiences, and stay updated with the latest news