low cost VPS server: ARM or x86?

The exact decision

This page answers one purchasing question: whether switching the processor architecture makes a matched low cost VPS server cheaper when the provider, advertised cores, memory, storage, contract view and storefront tax setting stay the same. The netcup catalogs show matching x86 and ARM64 G12.5 tiers from 4 GB through 64 GB RAM, with the same published pre-VAT monthly amount at every matched tier. [A] [B]

The software check is narrower than an installation test. It records whether five pinned Docker Official Image tags publish both linux/amd64 and linux/arm64 variants in their official manifests. It does not prove that plugins, native extensions, private images, backup agents or license servers in your own stack work on ARM. [C] [D] [E] [F] [G] [H]

Published inputs

These are catalog inputs, not benchmark results. The catalogs label the x86 storage as SSD and the ARM64 storage as NVMe; matching the advertised quantity does not establish matching storage performance. The provider uses 1 TB = 1024 GB in its own storage calculator. [A] [B]

Calculation: architecture alone changes no base-price line

Keep currency and tax treatment separate from architecture. The comparison below uses the pre-VAT monthly amounts printed beside the German 19% VAT display, then multiplies each monthly amount by the selected 12-month view. It does not add backup, software licenses, operator time or migration work because no matching amount for those items was collected here. [A] [B]

Example at the smallest matched tier: monthly cost per advertised GB of RAM = €8.26 ÷ 4 = €2.065 per GB-month for both architectures. Storage unit conversion = 64 ÷ 1024 = 0.0625 TB for both advertised capacities. ARM64 saving for the selected term = €99.12 − €99.12 = €0.00. [A] [B]

Inference: architecture is not a price lever in this specific dated catalog match. That does not show equal speed, energy use or application capacity. A buyer who selects ARM here is exchanging software-compatibility risk for an architecture choice, not receiving a lower published base charge. Only a workload test on the purchased systems could support a performance or capacity comparison.

Compatibility check: inspect the pinned image manifest

Do not treat a generic product-page claim about Linux support as proof for your exact deployment. Resolve the actual image tag used by the compose file or release manifest, then check that tag rather than an unpinned product name. Docker documents multi-platform images as a manifest list that points to platform-specific variants; the registry chooses a matching variant when one exists. [C]

A listed ARM64 variant clears only the image-availability gate. Before purchase, repeat the check for every image, inspect separately downloaded binaries and agents, and identify any package built during deployment. If one required component has no ARM64 artifact, keep x86 or replace that component before ordering. This is a preflight rule, not a claim that the listed stack was installed successfully.

Quick answer

Is an ARM low cost VPS server cheaper than x86?

Not in this matched netcup snapshot. The five published G12.5 tier pairs have the same pre-VAT monthly amounts, so their calculated 12-month base totals are also the same. Choose ARM only if the exact software manifest passes and you have a reason to test that architecture; otherwise x86 avoids introducing an architecture change without a published base-price saving. [A] [B]

Downloadable comparison table

The CSV keeps the verification date, official URLs, plan inputs, shown calculations and pinned image tags together. Blank fields would mean unknown, not free; this table has no blank price input because both matched catalog pages exposed the required base amounts.

The file is static and opens in a spreadsheet. Recheck every linked source before using it for a later purchase.

Before ordering an ARM server

1. Copy every exact container tag and separately downloaded binary from the deployment configuration. Do not substitute a product family name for the deployed tag.
2. Open each official tag manifest and confirm that linux/arm64 is listed. Keep the source URL and check date beside the tag.
3. Check native extensions, backup agents, monitoring agents and licensed software separately. They can have a different support matrix from the main container.
4. Compare the final cart using the same location, network option, contract and tax setting. The catalog match on this page is not a customer-specific checkout quote.
5. If the manifest gate passes, run an authorized ARM installation and workload test before claiming performance or operational savings. No such test result is included here.

Evidence and number sources

All pages and API responses were checked September 23, 2026. That is the verification date, not a vendor offer-expiry date. Published prices and image manifests can change.

• A — x86 plans: netcup vServer (VPS) catalog. G12.5 plan names, x86 architecture, cores, RAM, storage, pre-VAT monthly amounts, German 19% VAT display and selected 12-month catalog view.
• B — ARM64 plans: netcup ARM server catalog. Matching G12.5 ARM64 plan names, resources, prices, German 19% VAT display and selected 12-month catalog view.
• C — manifest method: Docker multi-platform documentation. Platform-specific image variants and the linux/amd64/linux/arm64 platform notation.
• D — NGINX tag: Docker Hub official tag API. The pinned tag and listed image architectures.
• E — PostgreSQL tag: Docker Hub official tag API. The pinned tag and listed image architectures.
• F — WordPress tag: Docker Hub official tag API. The pinned tag and listed image architectures.
• G — Redis tag: Docker Hub official tag API. The pinned tag and listed image architectures.
• H — MySQL tag: Docker Hub official tag API. The pinned tag and listed image architectures.