A dedicated Swiss platform for services that need room to operate. Metal Atlas brings a dual Xeon E5 foundation, DDR4 ECC memory and several network variants into one configurable server range.
Dual Xeon E5-2680 v4 processors, 64 GB of DDR4 ECC memory and a 1 TB SATA3 SSD form this dedicated configuration. Its network specification is a 1 Gbps port with unmetered traffic.
A dedicated E5-2680 v4 configuration with a 10 Gbps port and a 100 TB traffic allowance. The dual-processor hardware includes 64 GB of DDR4 ECC memory and a 1 TB SATA3 SSD.
Choose the unmetered-traffic variant of the 10 Gbps Atlas configuration. It pairs dual Xeon E5-2680 v4 processors with 64 GB of DDR4 ECC memory and a 1 TB SATA3 SSD.
A 20 Gbps port distinguishes this Atlas configuration for network-intensive projects. Dedicated dual Xeon E5-2680 v4 hardware, 64 GB of DDR4 ECC memory and a 1 TB SATA3 SSD accompany unmetered traffic.
Compare the listed specifications and base prices. Final availability, delivery and applicable tax are confirmed on your quote. Illustrations are conceptual.
Understand what makes this service family useful.
Start from the listed E5-2680 v4 platform and compare the memory, disks and operating-system choices needed for your application environment.
DDR4 ECC is listed in the base configuration. Review the RAM upgrade choices when combining databases, caches and multiple application services.
Atlas contains different port-speed and traffic combinations. Select the variant that fits the movement of data as well as the compute workload.
Add supported drives, review IPv4 allocation and select optional licences. The final summary keeps hardware and software selections visible together.
Plan a physical environment for databases, workers and web services with enough memory for their combined activity.
Evaluate the listed hypervisor images and hardware requirements for your own virtual environments and operational model.
Compare the faster network variants when the project moves substantial content to its authorised users.
An application platform often holds more than one process: a database, a cache, background workers and the public service. Estimate their combined memory and CPU needs, then plan storage for active data and growth. Atlas keeps a physical foundation while offering different ways to size the rest of the environment.
The Atlas variants share a recognisable compute foundation but list different network characteristics. Compare both the maximum port speed and the included traffic model. If a workload has a fixed traffic budget, review the optional bandwidth choice rather than assuming a faster port adds allowance.
A Swiss offshore server can host public applications while keeping management access restricted. Choose the operating system or hypervisor deliberately, expose only required services and protect administrative credentials. The listed IP allocation gives you addresses to plan with, not a complete security design.
The Atlas plans list physical hardware and five IPs in a /29 allocation. Confirm administrator rights, secure IPMI or equivalent access, IPv6 and the protection scope before delivery. Private VLANs, Layer 2 or Layer 3 networking and custom routing need a reviewed topology and quote. Storage-controller support, NVMe limits and network commitments also require confirmation for the selected machine.
Available choices depend on the selected configuration. See included selections and option prices in the configurator.
Specific answers for this service family.
Compare port speed and traffic alongside price and options. Select the network configuration that fits your usage, then verify the complete hardware summary.
The operating-system selector includes hypervisor choices where listed. Verify hardware, licensing and operational requirements before using one for your own virtualisation platform.
It identifies the memory type listed for the base server. It does not replace backups, software monitoring or a tested recovery process.
Yes. The configurator lists additional-drive choices. Confirm your intended storage layout and filesystem plan; the options describe drives, not an automatic application architecture.
Check each licence's account or domain allowance and system requirements. The server resources and the limits of a selected software licence are separate.
Confirm a secured IPMI or equivalent recovery console and the delivery of root or administrator credentials. Remote-management availability and access controls must be agreed for the actual server.
Prepare the topology, node count and routing requirements for review. VLANs, private links and Layer 2 or Layer 3 services are not automatic inclusions merely because a hypervisor image is listed.
Atlas lists five IPs in a /29 allocation, with optional additional blocks. Confirm IPv6 availability and usable addressing before planning firewall or routing rules.
No. Confirm disk compatibility, NVMe limits, maintenance windows, protection scope and any dedicated network commitment. Catalogue options describe proposed resources, not an upgrade or SLA procedure.
Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload.
Read the guideChoose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue.
Read the guideA Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment.
Read the guideChoose your resources. Keep control of your identity.