# SwissOctet complete public reference > Generated from the same public catalogue, service copy, policies and original guides used by the website. --- # SwissOctet reference > Public facts and a workload-based reading guide for SwissOctet. Canonical human page: https://swissoctet.com/reference/ ## Catalogue facts | Fact | Current public value | | --- | --- | | Hosting destination | Switzerland / CH only | | Service families | 18 | | Configurations | 55 | | Currency | USD | | Editorial guides | 32 | | Crypto assets | BTC, ETH, USDT, USDC, SOL, LTC | | Asset/network routes | 7 | | Distinct blockchain networks | Bitcoin, Ethereum, TRON, Solana, Litecoin | ## Current journey and claim boundaries Publication status: live-mode resource build. This generator does not publish files, change indexing controls or establish service readiness. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. Create an account before selecting a payment asset and network. Registration uses a username and password. A browser quote is not a server-issued invoice or payment confirmation. The current interface does not ask for an email address, passport, identity card or proof of address. The intended order journey is designed without documentary KYC; live operational arrangements require confirmation. Saved services and the cart use browser storage. The project brief is downloaded locally rather than sent. Clearing browser data does not cancel real orders or remove blockchain records. Swiss location and no-document onboarding do not establish absolute anonymity, zero logging, guaranteed non-disclosure, legal immunity, independently audited controls or an availability SLA. Server access, logs, retention and official-request handling must be documented for the live service. Public blockchains can expose transaction information. Payment verification and the delivery of infrastructure are separate events. Listed configurations, specifications and base prices describe the public catalogue. Final availability, provisioning, applicable taxes, licences, management and contractual terms are confirmed before a real order. Educational examples describe a decision method, not features included with every service. ## Choose by workload | Infrastructure type | Typical fit | Check before choosing | Relevant families | | --- | --- | --- | --- | | Linux VPS | Applications, private tools and test environments needing a Linux guest. | Memory, CPU allocation, storage, transfer and administration responsibilities. | Vector VPS | | Windows RDP | A remote Windows workspace for compatible applications and administration. | Operating system, licences, access restrictions, resource needs and recovery. | DeskLink RDP | | NVMe VPS | Applications where measured storage I/O is part of the constraint. | Actual I/O pattern, capacity and application latency; NVMe alone is not a benchmark. | Pulse NVMe | | Security testing environments | Authorised security assessment and learning using the listed Kali or Parrot environment. | Explicit permission for the target, operating-system tools, resources and the usage framework. | Sentinel Kali, Sentinel Parrot | | Storage configurations | Growing archives and datasets whose primary need is listed capacity. | Storage components, transfer allowance and an independent recovery strategy. | Vault Storage | | Dedicated servers | Projects needing the listed physical machine and its resource layout. | Processor, memory, drives, minimum term, management and independent recovery. | Metal Origin, Metal Atlas, Metal Zenith, Metal Hyper, Metal EPYC | | GPU servers | Supported accelerated computing, rendering and machine-learning workflows. | Exact device, per-device memory, software compatibility and the whole data pipeline. | Tensor GPU | | High-bandwidth servers | Data-moving workloads that can use the selected 40, 100 or 200 Gbps port profile. | The complete route, storage and CPU limits, transfer terms and responsible network use. | Transit 40, Transit 100, Transit 200 | | Web hosting | Websites whose stack and account requirements fit the enabled hosting features. | Runtime, domains, storage, permitted processes and restoration scope. | Canvas Web | | Onion hosting | Projects intended to be accessed through an onion-service arrangement. | Selected stack, onion addresses, capacity, application privacy and backup options. | Veil Onion | | VPN | A device connection using the protocol and configuration listed by the service. | Device allowance and protocol; a VPN is not a web-hosting server or an anonymity guarantee. | Shield VPN | ## Useful definitions ### VPS A virtual-machine environment. Its virtual resources and operating system are distinct from a purchase of the whole physical host. ### Dedicated server A physical machine assigned to the project; software management and redundancy are separate arrangements. ### NVMe A storage protocol designed for non-volatile media and parallel I/O. The label does not establish application-specific throughput or latency. ### GPU An accelerator used by compatible software. Workload fit depends on the device, memory and complete software and data pipeline. ### Port speed A connection rate, commonly expressed in Mbps or Gbps. It differs from a transfer allowance over a billing period. ### Transfer allowance An included data volume over time. Unmetered labels still operate within a port profile and usage conditions. ### Offshore Hosting outside a customer’s home country. SwissOctet’s listed destination is Switzerland; the term does not establish immunity or absolute confidentiality. ### No-document KYC The absence of identity-document collection in the described journey, not proof of absolute anonymity or an absence of operational records. ## Asset and network pairs | Asset | Network | | --- | --- | | BTC | Bitcoin | | ETH | Ethereum | | USDT | TRON (TRC20) | | USDT | Ethereum (ERC20) | | USDC | Ethereum (ERC20) | | SOL | Solana | | LTC | Litecoin | Review the complete checkout instructions: asset, network, exact amount, receiving address and expiry. Keep the client reference and exported record privately. A receiving address alone does not specify a payment, and a browser record does not prove receipt of funds. ## How to read prices and options Starting prices use the shortest available billing term for each plan, then the lowest effective monthly base among those configurations. They never assume an undisclosed longer commitment. The stated starting configuration supplies the corresponding specifications. Base prices and billing-period totals below come directly from the public catalogue. Effective monthly figures retain the catalogue’s displayed cent value; they are not recalculated from an already-rounded price. Nominal monthly rates before billing-period pricing are labelled separately. Add-ons are separate selections. The configurator applies the selected duration factor to monthly rates and presents the calculated configuration total. Only options allowed by the chosen plan are listed for that plan. A choice requiring an operator quote is not a free service. An included or zero-cost choice is identified only from its published price and does not imply that all software, management, backups or protections are included. ## Starting configurations and initial charges | Family | Configurations | Starting configuration | Effective monthly base | Shortest available term | Base charge for that term | Text specification | | --- | --- | --- | --- | --- | --- | --- | | Vector VPS | 6 | Vector VPS 01 | USD 11.84 | 1 month | USD 11.84 | https://swissoctet.com/services/vector/index.txt | | DeskLink RDP | 4 | DeskLink RDP 01 | USD 22.95 | 1 month | USD 22.95 | https://swissoctet.com/services/desklink/index.txt | | Pulse NVMe | 5 | Pulse NVMe 01 | USD 13.77 | 1 month | USD 13.77 | https://swissoctet.com/services/pulse/index.txt | | Vault Storage | 1 | Vault Storage 01 | USD 62.42 | 1 month | USD 62.42 | https://swissoctet.com/services/vault/index.txt | | Sentinel Kali | 4 | Sentinel Kali 04 | USD 12.85 | 1 month | USD 12.85 | https://swissoctet.com/services/sentinel-kali/index.txt | | Sentinel Parrot | 4 | Sentinel Parrot 04 | USD 12.85 | 1 month | USD 12.85 | https://swissoctet.com/services/sentinel-parrot/index.txt | | Tensor GPU | 3 | Tensor GPU 01 | USD 323.82 | 1 month | USD 323.82 | https://swissoctet.com/services/tensor/index.txt | | Canvas Web | 4 | Canvas Web 01 | USD 12.85 | 1 month | USD 12.85 | https://swissoctet.com/services/canvas/index.txt | | Veil Onion | 3 | Veil Onion 01 | USD 27.54 | 1 month | USD 27.54 | https://swissoctet.com/services/veil/index.txt | | Metal Origin | 3 | Metal Origin 01 | USD 146.88 | 3 months | USD 440.64 | https://swissoctet.com/services/metal-origin/index.txt | | Metal Atlas | 4 | Metal Atlas 01 | USD 284.81 | 1 month | USD 284.81 | https://swissoctet.com/services/metal-atlas/index.txt | | Metal Zenith | 3 | Metal Zenith 01 | USD 351.13 | 1 month | USD 351.13 | https://swissoctet.com/services/metal-zenith/index.txt | | Metal Hyper | 2 | Metal Hyper 01 | USD 642.59 | 1 month | USD 642.59 | https://swissoctet.com/services/metal-hyper/index.txt | | Metal EPYC | 4 | Metal EPYC 01 | USD 371.79 | 1 month | USD 371.79 | https://swissoctet.com/services/metal-epyc/index.txt | | Transit 40 | 2 | Transit 40 01 | USD 1926.86 | 1 month | USD 1926.86 | https://swissoctet.com/services/transit-40/index.txt | | Transit 100 | 1 | Transit 100 01 | USD 7343.00 | 1 month | USD 7343.00 | https://swissoctet.com/services/transit-100/index.txt | | Transit 200 | 1 | Transit 200 01 | USD 13768.93 | 1 month | USD 13768.93 | https://swissoctet.com/services/transit-200/index.txt | | Shield VPN | 1 | Shield VPN 01 | USD 4.59 | 1 month | USD 4.59 | https://swissoctet.com/services/shield/index.txt | ## Public resources - [Catalogue text](https://swissoctet.com/catalogue/index.txt): Base specifications, billing periods and plan-specific options. - [Complete corpus](https://swissoctet.com/llms-full.txt): Full public service and editorial material. - [Insights library](https://swissoctet.com/insights/): Original guides with checklists, FAQ and primary references. --- # Private Swiss offshore infrastructure — VPS, dedicated servers, and cloud \| SwissOctet Canonical URL: https://swissoctet.com/ Private Swiss offshore infrastructure — VPS, dedicated servers, and cloud ## Your privacy. Swiss precision. Privacy comes first. Swiss offshore hosting. No KYC. Less personal information to hand over. [Find your infrastructure](https://swissoctet.com/catalogue/) [Discover SwissOctet](https://swissoctet.com/about/) Swiss VPS from $11.84 / month · Base configuration Swiss-only hosting No identity documents Crypto-native Familiar technology. An independent Swiss foundation. Linux Debian Ubuntu Windows KVM NVMe OpenVPN Node.js LiteSpeed cPanel Technologies available across selected configurations. Compatibility and licences vary by plan. START WITH YOUR PROJECT ## What will you build? A useful starting point, based on what you want to run. Open the plans to check the exact resources and options. ### Apps & APIs An independent Linux environment for your application stack. [Vector VPS From $11.84 / month](https://swissoctet.com/services/vector/) 1-month base term · Add-ons separate [Explore NVMe compute](https://swissoctet.com/services/pulse/) ### Websites & publishing Web hosting for sites, domains and a familiar control panel. [Canvas Web From $12.85 / month](https://swissoctet.com/services/canvas/) 1-month base term · Add-ons separate [Explore onion hosting](https://swissoctet.com/services/veil/) ### Windows workspace A remote desktop with a choice of Windows configurations. [DeskLink RDP From $22.95 / month](https://swissoctet.com/services/desklink/) 1-month base term · Add-ons separate ### Archives & datasets A storage-focused environment for larger collections of data. [Vault Storage From $62.42 / month](https://swissoctet.com/services/vault/) 1-month base term · Add-ons separate ### GPU workloads Compare dedicated GPU resources with your software requirements. [Tensor GPU From $323.82 / month](https://swissoctet.com/services/tensor/) 1-month base term · Add-ons separate ### Your own hardware A physical machine for workloads that need dedicated resources. [Metal Origin From $146.88 / month](https://swissoctet.com/services/metal-origin/) 3-month minimum · $440.64 base total [Explore EPYC configurations](https://swissoctet.com/services/metal-epyc/) ### High-volume transfer Dedicated bandwidth plans for projects with substantial network needs. [Transit 40 From $1,926.86 / month](https://swissoctet.com/services/transit-40/) 1-month base term · Add-ons separate [Explore 100 Gbps plans](https://swissoctet.com/services/transit-100/) ### Security & private access Authorized security workspaces or a Swiss OpenVPN connection. [Sentinel Kali From $12.85 / month](https://swissoctet.com/services/sentinel-kali/) 1-month base term · Add-ons separate [Explore OpenVPN](https://swissoctet.com/services/shield/) Every configuration is listed for Switzerland. Capacity and compatibility depend on the selected plan. [Compare the full catalogue](https://swissoctet.com/catalogue/) A DIFFERENT FOUNDATION ## Infrastructure with nothing to hide. A complete technical catalogue. A discreet customer journey. A clear Swiss location. BUILT TO DO MORE ### Small start. Serious headroom. From a first Linux VPS to dedicated hardware, GPU acceleration and 200 Gbps networking. Find the right platform, then make it yours. [Meet the infrastructure](https://swissoctet.com/catalogue/) LESS TO DISCLOSE ### Confidentiality at the core. No passport scan. No proof of address. No advertising profile. Explore and prepare your infrastructure without uploading identity documents. [Our privacy commitments](https://swissoctet.com/privacy/) A DELIBERATE LOCATION ### Offshore. In Switzerland. One Swiss destination across every service family. A stable point of reference for your architecture. YOUR STACK, YOUR WAY ### Made for your workload. OS images, resource upgrades, backups, applications and network options. Specific choices for each service. CRYPTO, CLEARLY ### Every network matters. BTC, ETH, USDT, USDC, SOL and LTC. Seven explicit payment routes and a complete order review. [Understand crypto networks](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/) THE RIGHT TOOL FOR THE JOB ## Find your next core. 18 service families. 55 configurations. One Swiss location. CLOUD COMPUTE CH / 6 PLANS ### Vector VPS A Linux foundation for applications, private services and everyday server work. Choose the resources and operating system your project needs, with every configuration located in Switzerland. VCPU 2 x Xeon E5-2680 v4 RAM 1GB DDR4 Storage 30GB SSD Bandwidth 100 Mbp/s 2TB STARTING AT $11.84 / month 1-month base term · Add-ons separate [Explore plans](https://swissoctet.com/services/vector/) Swiss location No identity document onboarding Crypto checkout [Explore all configurations](https://swissoctet.com/catalogue/) THE PRINCIPLES BEHIND THE CORE ## Confidence in every layer. Discretion in the journey. Control over your environment. A clear path to support. The foundations of a Swiss infrastructure experience built around you. 01 / LESS TO ENTRUST ### Confidentiality. Your project deserves privacy. Explore, compare and configure without identity documents, an advertising profile or an account. Your saved choices stay in this browser. A discreet starting point. No passwords, private keys or recovery phrases are needed to prepare your project. [Read our privacy approach](https://swissoctet.com/privacy/) 02 / KEEP YOUR CONTROL ### Security. Swiss offshore infrastructure is a place to build your security. Combine encrypted connections, restricted access and protected backups with a workload you control. End-to-end starts with your keys. For true end-to-end encryption, use a compatible application that encrypts on your device and keeps decryption keys outside the host. [Explore the security guide](https://swissoctet.com/insights/linux-vps-hardening-baseline/) 03 / PEOPLE BEHIND THE PLATFORM ### Technical guidance. Build a clear technical plan with practical guides, service specifications and configuration tools. Find the resources that help you make the next decision. Prepare your question today. Create a private project brief on your device and keep the details together. The brief is downloaded locally. [Prepare a support brief](https://swissoctet.com/contact/) Clear promises build trust. Hosting location, encryption and privacy are separate layers. Read the [privacy scope](https://swissoctet.com/privacy/) for information on the website and its services. YOUR WALLET. YOUR WAY. 06 ASSETS / 07 PAYMENT ROUTES ## More ways to power your next core. Swiss infrastructure. A crypto-native payment journey. Choose your currency, match the network and keep every detail clear. [Understand payment networks](https://swissoctet.com/insights/choose-crypto-asset-network/) Bitcoin logo 01 ### Bitcoin BTC Bitcoin Ethereum logo 02 ### Ethereum ETH Ethereum Tether logo 03 ### Tether USDT TRON (TRC20) Ethereum (ERC20) USD Coin logo 04 ### USD Coin USDC Ethereum (ERC20) Solana logo 05 ### Solana SOL Solana Litecoin logo 06 ### Litecoin LTC Litecoin One asset. The right network. USDT supports TRON (TRC20) and Ethereum (ERC20). USDC uses Ethereum (ERC20). Review the complete payment instructions and expiry. SWISS BY DESIGN ## Your infrastructure. A clear sense of place. Discover the connection between location, capacity and control. \+ SWITZERLAND / CH ### A Swiss anchor. A global ambition. From virtual machines to high-throughput dedicated ports, every SwissOctet configuration shares the same country. Choose your network profile around the actual needs of your project. 18 service families 55 configurations 200 Gbps largest listed port Illustrative country map. Port capacity depends on your selected plan and is not an end-to-end speed guarantee. [Explore the Swiss network](https://swissoctet.com/network/) FROM IDEA TO INFRASTRUCTURE ## A better way to build. Make informed choices at every step. ### Find your fit. Search by hardware, compare service families and keep a private shortlist on your browser. [Explore the catalogue](https://swissoctet.com/catalogue/) ### Go beyond the base plan. Choose the period, operating system and add-ons available for the configuration you actually need. [Configure your resources](https://swissoctet.com/services/vector/) ### Know your next move. Practical guidance on storage, backups, bandwidth and payment networks. Clear answers before you order. [Read the guides](https://swissoctet.com/insights/) SWISSOCTET INSIGHTS ## Build with a clearer picture. Useful knowledge for decisions that shape your infrastructure. Compute Compute 4 MIN READ ### [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/) Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. Read the guide Dedicated Dedicated 4 MIN READ ### [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/) Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. Read the guide Storage Storage 4 MIN READ ### [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/) Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. Read the guide [Explore all insights](https://swissoctet.com/insights/) QUESTIONS, ANSWERED ## Details make the difference. Understand the platform before choosing your next service. ### Which locations are offered? SwissOctet exclusively presents the Swiss configurations from its catalogue. The location is indicated along with the characteristics of each offering. ### VPS or dedicated server: how to choose? A VPS provides resources in a virtual environment. A dedicated server puts a physical machine at the service of your project. Start with your memory, storage and traffic needs, then compare configurations rather than the name of the range. ### Do you have to provide an ID document? Explore the catalogue and prepare a configuration without entering a legal name, passport details or proof of address. ### Why does the payment network matter? Review the complete checkout instructions: asset, network, exact amount, receiving address and expiry. Keep the client reference and exported record privately. A receiving address alone does not specify a payment, and a browser record does not prove receipt of funds. ### When will a payment be considered confirmed? The billing service must verify the transaction and link it to your order. The site will display a confirmation only when that service returns a confirmed payment status. Creating an invoice or stating that a transfer has been sent does not prove receipt of funds. ### What does the privacy-first approach include? The site includes no audience analytics tool, no marketing cookie and no personalised advertising. You can browse the offerings without creating an account. YOUR NEXT MOVE ## Put your next idea on Swiss ground. Choose your resources. Keep control of your identity. [Explore infrastructure](https://swissoctet.com/catalogue/) --- # About SwissOctet: Swiss Location, Privacy and Control Canonical URL: https://swissoctet.com/about/ ABOUT SWISSOCTET / AN INDEPENDENT POINT OF VIEW ## Swiss by choice. Independent by design. A clear Swiss destination. A discreet path in. Infrastructure shaped around your project. [Explore infrastructure](https://swissoctet.com/catalogue/) + PRECISION IN THE DETAILS. CONTROL AT THE CORE. A clear Swiss destination. Every configuration in the catalogue is presented with a Swiss location. Service families Swiss configurations Hosting country Asset / network routes 01 / OUR POINT OF VIEW A FOUNDATION, NOT JUST A NAME. SwissOctet brings location, useful specifications and a discreet customer journey into one focused experience. Start with your workload. See your choices clearly. Build a configuration on your own terms. All of the configurations presented here are Swiss. Their resources and configurable options remain visible, including where a particular choice needs a quote. There is no reason to hide the details that decide whether a machine will suit your project. CH ONE DELIBERATE DESTINATION 01 / LOCATION ### One country. A clear foundation. Every configuration shares a Swiss destination. Compare the resources that fit your project, with the location in plain sight. [Explore the Swiss network](https://swissoctet.com/network/) LESS TO HAND OVER 02 / PRIVACY ### Ask for less. Explain the rest. Explore without uploading identity documents. Keep your shortlist in this browser and understand the scope of our privacy commitments. [Our privacy approach](https://swissoctet.com/privacy/) region CH resources your choice environment your stack next move your project\_ SPECIFICATIONS BEFORE SLOGANS 03 / CONTROL ### See the details. Make it yours. Choose your system, resources and useful extras. Compare CPU, memory, storage and network profiles before preparing your configuration. [Find your configuration](https://swissoctet.com/catalogue/) 02 / A SENSE OF PLACE ## A Swiss anchor. Room to build. A personal service, a production application, a remote desktop and a high-throughput distribution platform do not need the same machine. Our catalogue spans virtual environments, dedicated systems, storage, GPU configurations, web hosting and privacy services so you can start from the workload rather than a marketing tier. + Switzerland / CH The only hosting country in the catalogue. [Discover the connection](https://swissoctet.com/network/) SWITZERLAND / CH · ILLUSTRATIVE LOCATION MAP 03 / A COMPLETE SPECTRUM 55 CONFIGURATIONS. YOUR STARTING POINT. ## Different projects. The same Swiss core. Virtual environments, dedicated hardware, networking, hosting and privacy services. Find your direction, then explore the exact specifications. 01 ### [Cloud compute](https://swissoctet.com/catalogue/compute/) 4 service families 02 ### [Dedicated & GPU](https://swissoctet.com/catalogue/dedicated/) 6 service families 03 ### [High bandwidth](https://swissoctet.com/catalogue/network/) 3 service families 04 ### [Web & onion hosting](https://swissoctet.com/catalogue/hosting/) 2 service families 05 ### [Security & privacy](https://swissoctet.com/catalogue/privacy/) 3 service families 04 / A CONSIDERED APPROACH ## Privacy is a practice. Clarity is part of it. [Read our commitments](https://swissoctet.com/privacy/) Explore the catalogue and prepare your choices without providing a passport or proof of address. Avoid unnecessary personal information in a configuration or technical brief. Privacy also depends on how the information required for account access and service operation is handled. Offshore describes a hosting location outside a customer's home country. At SwissOctet that location is Switzerland. It does not erase the public trail of a blockchain transaction, the security responsibilities of running a server or the rules that protect other customers. Our approach is to make those boundaries understandable. THE CURRENT JOURNEY Live ordering, payment verification and provisioning require connected operational systems. The current interface lets you prepare a configuration and review the intended crypto journey. Availability, contractual terms, payment acceptance and the delivery of access must be confirmed by the live service before you rely on them. 01 / THE NEXT STEP ### Discover your fit. Explore the catalogue, compare specifications and keep a shortlist in this browser. [Explore the catalogue](https://swissoctet.com/catalogue/) 02 / THE NEXT STEP ### Shape your environment. Choose your plan, period and the extras available for your particular service. [Meet the configurations](https://swissoctet.com/services/vector/) 03 / THE NEXT STEP ### Prepare your next move. A good infrastructure experience continues through configuration, access, updates and recovery. We provide practical guides to help you compare the catalogue and prepare those next steps. When you assess a service, consider how you will maintain it and recover it as carefully as how you will launch it. [Read the practical guides](https://swissoctet.com/insights/) SWISSOCTET / YOUR NEXT CHAPTER ## Your idea. Your own core. Start with a Swiss foundation and make the details yours. [Build your configuration](https://swissoctet.com/catalogue/) [Prepare a project brief](https://swissoctet.com/contact/) SWISS-ONLY HOSTING · 6 ASSETS · 7 PAYMENT ROUTES --- # The SwissOctet Network: Location and Capacity Explained Canonical URL: https://swissoctet.com/network/ THE SWISS CONNECTION ## Your infrastructure has a home. Your ambition has no borders. Swiss hosting, from the first virtual machine to demanding high-throughput workloads. Choose the network profile that matches the way your project moves data. SwissOctet brings Swiss location, visible transfer allowances and configurable resources into one catalogue, so you can plan around the actual specification of your service. [Explore high-bandwidth servers](https://swissoctet.com/catalogue/network/) \+ ONE COUNTRY ## Swiss location. Visible specifications. Check connection rates and transfer allowances on each plan. The catalogue spans virtual compute, dedicated hardware and high-throughput Transit configurations. Switzerland / CH 1–200 Gbps dedicated profiles Plan-specific traffic allowances ## One country. A complete infrastructure spectrum. Every configuration in the SwissOctet catalogue is presented with a Swiss location. There is no country selector to move your order elsewhere. Start with a lightweight Linux environment, build a dedicated application platform or compare the Transit ranges when moving large volumes of data becomes the main requirement. Location is one part of the decision. The route to your users, the software at each end and the performance of storage all affect the experience. A Swiss server gives you a clear hosting destination; your application architecture determines how well that destination serves your audience. ### Virtual infrastructure VPS profiles combine a stated port rate with a transfer allowance. Check the chosen plan and optional port upgrades together. [Compare VPS](https://swissoctet.com/catalogue/compute/) ### Dedicated capacity Dedicated ranges include profiles with 1 or 10 Gbps ports. Transfer terms differ, including stated quotas and unmetered configurations. [Explore dedicated](https://swissoctet.com/catalogue/dedicated/) ### High-throughput workloads Transit 40, Transit 100 and Transit 200 present 40, 100 and 200 Gbps port profiles respectively, with unmetered transfer listed in their specifications. [Explore Transit](https://swissoctet.com/catalogue/network/) ## A port rate and a transfer allowance tell different stories. Port speed describes the rate of a connection. A monthly transfer allowance describes the amount of data included over time. A fast port with a fixed allowance can suit short bursts, while a sustained distribution workload needs enough capacity across the whole billing period. Compare both figures before choosing. An unmetered label means the listed plan does not present a fixed monthly transfer quota. It does not mean an unlimited instantaneous speed, a guaranteed rate to every destination or permission to disrupt shared infrastructure. The physical port, application performance and usage policy still apply. - Read the bandwidth or traffic line on the specific configuration. - Check whether a port upgrade changes the transfer allowance or only the connection rate. - Estimate normal demand and bursts separately. - Include replication, backup traffic and software distribution in your estimate. ## Build around the whole route, not a headline number. A large network port cannot accelerate a slow remote client or a disk that cannot read quickly enough. Encryption, application workers, concurrent connections and the receiving system can each become the limiting component. Plan a balanced machine before paying for more network capacity. Measure from locations that represent your audience and keep the test conditions clear. Record the destination, timing, protocol and concurrency alongside the result. Use small, authorised tests first; repeated saturation tests belong in a coordinated maintenance window, not on somebody else's service. ## Protect the service at every layer. Some catalogue configurations list Layer 3–4 DDoS protection, and selected products offer related options. Read the chosen configuration rather than assuming that every service includes the same protection. A network protection label is not a promise to absorb every attack or secure an application automatically. Keep the operating system maintained, restrict administration access and limit exposed services. Application authentication, rate limits, request validation and a recovery plan remain part of running a reliable project. ## A private environment. A responsible network. SwissOctet is designed for lawful projects whose owners value confidentiality. The same principle protects other customers: your service must not create attacks, fraudulent destinations or avoidable instability for their infrastructure. Abuse reports should include the affected address, relevant timestamps, a concise description and evidence with personal information reduced to what is necessary. Never submit credentials, private keys or complete customer datasets. Operational response procedures and contractual remedies will be defined with the live service terms. - Do not originate denial-of-service attacks, unauthorised intrusion or network disruption. - Do not host phishing, malware distribution, fraud or unsolicited bulk messaging. - Do not host or distribute sexual abuse material involving children or content that harms people unlawfully. - Only test systems you own or have explicit permission to assess. - Respect applicable law, software licences and the rights of the people whose data you handle. ## Bring the useful numbers. Leave the secrets out. Preparing a network request is easier when you know your current monthly transfer, the peak rate, the regions you serve and the type of workload. Tell us whether you distribute files, serve interactive requests or replicate data; these patterns require different balances of CPU, storage and network capacity. Add any specific address requirement and your preferred operating system. Availability, route information, support arrangements and any service commitment must be confirmed for the actual order. This catalogue does not advertise an independently measured uptime, a peering list or an unverified latency guarantee. ### Prepare a network brief Keep your expected usage, preferred range and operational constraints together in one clear request. [Prepare my request](https://swissoctet.com/contact/) YOUR NEXT MOVE ## Put your next idea on Swiss ground. Choose your resources. Keep control of your identity. [Explore infrastructure](https://swissoctet.com/catalogue/) --- # Privacy at SwissOctet: Data Collection and No KYC Canonical URL: https://swissoctet.com/privacy/ Privacy ## Confidentiality comes first. Your project deserves a discreet home. Less information to entrust, clear control over your choices and a security model you can understand. ### No identity documents. Explore the catalogue and prepare a configuration without entering a legal name, passport details or proof of address. ### No advertising profile. This presentation includes no advertising trackers or audience analytics. Its fonts and application assets are served from the same origin. ### Your choices stay local. Saved services and the cart stay in this browser. The project brief downloads to your device without sending a message. Read how browsing, saved configurations, technical briefs and account information are handled. 01 / SWISSOCTET ## Browse without an advertising profile. The site includes no audience analytics tool, no marketing cookie and no personalised advertising. You can browse the offerings without creating an account. 02 / SWISSOCTET ## Your selections stay in your browser. Favourites, the basket and saved Insights guides use your browser’s local storage to remember your choices. Saved guides contain article identifiers, stay on this browser and are not synchronised to an account. Clear saved selections with the site's Clear browser data control or your browser settings. Saving a configuration does not create an order or collect a payment. 03 / SWISSOCTET ## A useful exchange, without superfluous data. Use the project brief to record only the service you are considering and the technical help you need. The file is downloaded to your device and is not sent through this form. Never include passwords, private keys, recovery phrases or identity documents. 04 / SWISSOCTET ## No document checks in your way. Browse, compare and configure services without uploading identity documents, creating an account or providing an email address. The account form uses a username and passphrase. Registration availability is shown on that form, and an account exists only after confirmation from the account service. 05 / SWISSOCTET ## A private workspace for your orders. Create an account before selecting a payment asset and network. Registration uses a username and password. A browser quote is not a server-issued invoice or payment confirmation. 06 / SWISSOCTET ## Privacy needs a clear operating policy. Confidentiality depends on how a service is operated. Check the data collected, technical records, administrative access, retention periods and service providers for the selected offering. Hosting location and website features do not establish a zero-log implementation, an independent security audit or absolute anonymity. 07 / SWISSOCTET ## Encryption has a boundary. Keep yours clear. An HTTPS connection protects information in transit between your browser and the website; the local HTTP development address does not provide that protection. For hosted workloads, secure administrative connections and encryption at rest are separate choices. True end-to-end encryption requires a compatible application that encrypts on your device and keeps decryption keys outside the host. Swiss location, an encrypted server disk or HTTPS alone does not establish end-to-end encryption for every service. 08 / SWISSOCTET ## A secure environment starts with controlled access. Use unique credentials, restrict administration access, maintain current software and keep independent encrypted backups with a tested recovery path. Store private keys and recovery material outside the public web directory. Confirm the operator's responsibilities for the selected offering; these deployment practices do not establish an independent infrastructure security audit. 09 / SWISSOCTET ## Expert help should respect your boundaries. Prepare a technical brief with the service, symptoms and assistance you need. The form downloads your brief to your device without sending a message. Keep sensitive details out of the file and confirm the support channel and scope for your service. Never include wallet credentials, private keys, recovery phrases or identity documents. 10 / SWISSOCTET ## Customer information deserves discretion. SwissOctet is designed around limited collection and confidential handling of the information a service actually needs. Requests for information must be assessed under applicable law and the published operating policy. Swiss hosting and no-document onboarding do not guarantee immunity from legal obligations or that no information can ever be disclosed. 11 / SWISSOCTET ## Take back control in one move. Clear your browser selections whenever you wish. Clearing local data does not cancel an order or delete a server account. Account-data access, correction and deletion follow the applicable retention rules and verified request process. 12 / SWISSOCTET ## Understand what a payment reveals. Public blockchains record transfers, and wallet or exchange providers can have their own records and identity checks. Fixed-address quotes and configuration details stay in this browser and can be exported. They are not authenticated account records. Crypto payments alone do not guarantee anonymity. **Language** Choose your language Clear local data **Browsing** Display the site and its local resources No account required **Favourites** Retrieve the offerings selected on this browser Deletion from your favourites or your browser settings **Basket** Keep your configuration before a request Deletion from the basket or your browser settings **Saved guides** Remember Insights articles selected on this browser Unsave a guide, clear browser data or use browser settings [Explore the infrastructure](https://swissoctet.com/catalogue/) --- # SwissOctet Help: Hosting, Privacy and Crypto Questions Canonical URL: https://swissoctet.com/help/ SWISSOCTET HELP ## Clarity before your next move. Practical answers about Swiss infrastructure, privacy, configuration and payment routes. ## Choose ### Which locations are offered? SwissOctet exclusively presents the Swiss configurations from its catalogue. The location is indicated along with the characteristics of each offering. ### VPS or dedicated server: how to choose? A VPS provides resources in a virtual environment. A dedicated server puts a physical machine at the service of your project. Start with your memory, storage and traffic needs, then compare configurations rather than the name of the range. ### What should you look at for a storage-heavy project? Check the usable capacity, the disk type and the included traffic. Distinguish primary storage from backups: keeping a second copy on the same environment does not replace an independent backup. ### When is a GPU configuration useful? When your software actually uses graphical computing: rendering, image processing or certain computing workloads. Check your application's compatibility, the GPU memory and the resources of the rest of the machine. ### What if none of the base plans fits my project? Start with the closest configuration and review its resource and network options. Prepare a technical brief for any requirement outside those choices. Hardware fit, software compatibility, supply, lead time and the final charge require confirmation before provisioning. ### Which services provide server administration control? VPS and bare-metal configurations are intended for administering your operating-system environment through Linux root access or Windows administrator access. Web hosting provides a hosting control panel rather than machine-level root access. Confirm the access method for the selected plan before delivery. ## Privacy ### Do you have to provide an ID document? Explore the catalogue and prepare a configuration without entering a legal name, passport details or proof of address. ### Does offshore mean absolute anonymity? No. Here, offshore describes the Swiss location of the hosting for customers based elsewhere. Confidentiality also depends on software, access, payments and your own practices. No location is enough to promise invisibility. ### Does the site use advertising tracking tools? The presentation site includes neither analytics nor marketing cookies. Favourites and the basket remain stored locally in your browser and can be cleared. ### What information should you share for a technical request? State the service concerned, the symptom, the time and the steps that reproduce it. Mask personal data in screenshots and logs. Never send a password, a recovery code or a private key. ### When can I create a customer account? Create an account before selecting a payment asset and network. Registration uses a username and password. A browser quote is not a server-issued invoice or payment confirmation. ### What does the privacy-first approach include? The site includes no audience analytics tool, no marketing cookie and no personalised advertising. You can browse the offerings without creating an account. ### Can you guarantee that information will never be disclosed? No unconditional guarantee has been established. Customer confidentiality is a design priority, while requests for information must be assessed under applicable law and the real service policy. Swiss location and no-document onboarding do not make blockchain activity private or remove applicable obligations. ### Is every hosted service automatically end-to-end encrypted? End-to-end encryption is an application design: information is encrypted before reaching the host and the decryption keys remain with the intended endpoints. HTTPS protects a connection, while disk encryption protects a different boundary. Use a compatible application and keep its decryption keys outside the hosting environment if you need the host to handle ciphertext without access to plaintext. This model is not automatically included in every catalogue offering. ## Process ### Does adding an offering to the basket start an order? No. The basket prepares your selection on this browser. Opening the client area or signing in does not place an order, reserve a machine or activate a service. Your selection is kept when you enter the account step so you can return to checkout. ### Do I need an account before checkout? Create an account before selecting a payment asset and network. Registration uses a username and password. A browser quote is not a server-issued invoice or payment confirmation. ### What can I manage in the client area? Services appear after the server confirms provisioning. An unconfirmed payment does not create an active service. ### How should you read the catalogue prices? The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. ### Within what timeframe will the service be available? Delivery depends on the configuration and confirmed availability. Agree the timeframe with the operator before scheduling a migration or relying on a service date. ### Can I pay from this site? The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. ### Why does the payment network matter? Review the complete checkout instructions: asset, network, exact amount, receiving address and expiry. Keep the client reference and exported record privately. A receiving address alone does not specify a payment, and a browser record does not prove receipt of funds. ### When will a payment be considered confirmed? The billing service must verify the transaction and link it to your order. The site will display a confirmation only when that service returns a confirmed payment status. Creating an invoice or stating that a transfer has been sent does not prove receipt of funds. ### Where can I check renewal and refund conditions? Confirm the operator’s identity, availability, delivery timeframe, applicable tax, renewal, cancellation and refund terms before sending funds. The fixed-address checkout provides a browser quote with complete transfer instructions; it does not issue a server invoice or confirm an accepted order. Payment verification and service delivery remain separate backend operations. ## Deployment ### How should I prepare my backups? Plan an independent copy of your data and test its restoration. Set the frequency according to what you can afford to lose and the time you have to get back online. Backup options must be confirmed for the chosen offering. ### What should I do after a server is made available? Check access, update the system, enable a suitable firewall and secure administration. Then install your application, configure your backups and check operation from another environment. ### What are security environments for? They let you prepare audits and tests on systems you own or for which you have authorisation. Their availability does not constitute authorisation to test third-party services. ### Does a payment confirmation immediately activate a server? No. Payment and making the service available are two separate steps. Your order status and access information must be communicated by the operator once the infrastructure is available. ### How can I strengthen the privacy of my hosted project? Use encrypted application and administrative connections, restrict access, update software and maintain independent encrypted backups with a tested recovery path. Separate secrets from public files and decide where decryption keys are kept. Confirm the operator's access and responsibilities for your offering before deployment. ### How should I prepare a technical support request? Record the service, symptoms and technical help you need in the project brief. The form downloads the file to your device without sending a ticket or message. Keep credentials and sensitive customer data out of the brief, and confirm the support channel, languages and operating scope for your service. ### Why can a DNS change appear at different times? DNS answers can remain cached according to their TTL. Check the authoritative record first, then allow existing caches to expire. For a migration, lower the TTL ahead of time and retain the previous destination during the transition. Domain registration and authoritative DNS are separate from the hosting configuration. ### Can someone manage the server for me? Selected families list management services in their configurator. Compare the scope of the option with the work you need: updates, application deployment, incident handling and backups are different responsibilities. Custom installation requests need an operator quote; a zero-price request entry does not promise free administration. ### Can I add IPv4 addresses? Several server families include additional IPv4 choices, while dedicated configurations may list an address block. Check both the base specifications and the selected option: an extra address is different from an included address. Routing, permitted use and availability need confirmation for the selected service. ### How do I regain access if SSH or RDP stops working? A remote console provides a different route from SSH or RDP. Some configurations list VNC as an option; physical servers may require an IPMI or KVM access arrangement. Confirm the recovery method and credentials with the operator before changing firewall or network settings. A console option does not replace a backup. ### Can I reinstall the operating system? Choose only an image compatible with the selected configuration. Confirm whether the service uses a customer control panel, remote console or assisted installation. Reinstallation can erase the operating-system disk and application data: keep an independent copy and confirm any assistance charge before proceeding. ### Does an onion hosting plan also provide a Tor relay? An onion website and a public Tor relay serve different purposes. Veil plans describe hosted onion services; they do not automatically authorise a relay or exit node. Check the use policy, traffic allocation and operator approval for any relay project before ordering. ### What should I check before hosting a sensitive project? Review the use policy and describe unusual network or content requirements in your technical brief. Swiss location does not authorise attacks, unsolicited bulk messaging, phishing or unlawful activity. Security testing requires the target owner's permission. Confirm project fit and the applicable service rules before deployment. [Deployment guide](https://swissoctet.com/guide/) [Facts & resources](https://swissoctet.com/reference/) --- # Prepare a SwissOctet Infrastructure Brief \| SwissOctet Canonical URL: https://swissoctet.com/contact/ PROJECT ASSISTANCE ## Let’s shape your next project. Prepare a clear technical brief, without sharing more information than necessary. PROJECT ASSISTANCE ### A useful conversation. Only the useful details. Tell us what you want to run, how much resource it needs and where you need flexibility. Avoid personal data and credentials. Use the form to save your technical brief. Direct message delivery is unavailable; your brief stays on your device. [Find an answer in the help centre](https://swissoctet.com/help/) #### Start with the essentials. CPU and memory requirements Storage and backup strategy Monthly traffic and port speed Software and deployment constraints --- # SwissOctet Affiliates: 20% First Month, 10% Recurring Canonical URL: https://swissoctet.com/affiliates/ THE SWISSOCTET AFFILIATE PROGRAMME / YOUR NETWORK. A SWISS CONNECTION. ## Good connections. Lasting rewards. Earn 20% on the first paid month, then 10% on eligible paid months that follow. Introduce your audience to Swiss infrastructure and an additional 10% discount on eligible services. Review the programme rates, choose relevant configurations and prepare your partner brief. Registration, referral attribution and payouts are currently unavailable. Prepare a partner brief Estimate your rewards AFFILIATE PROGRAMME Referral terms, earnings estimates and partner resources. SC / CONNECTION CORE CH · REFERRALS YOUR COMMUNITY SWISS INFRASTRUCTURE 20% First paid month 10% Later payments & renewals 10% Off for referred clients $27.99 Approved balance to withdraw THE PARTNER ADVANTAGE ## More than a referral link. A useful recommendation can become an ongoing relationship. Review the programme terms and resources below. 01 ### A strong first month Receive 20% of the eligible service amount paid for the first month of a qualifying referral. 02 ### A return that continues Earn 10% on subsequent eligible paid months and renewals while the referred service remains active. 03 ### A reason to choose your link Your referred customer receives an extra 10% off eligible SwissOctet services, applied to the current base price. 04 ### A clear view of your activity Referral reporting separates link activity, qualifying purchases and commission entries. Access and attribution require an activated partner account. 05 ### Materials ready to share Download original SwissOctet banners for your publication. Pair the artwork with an approved referral link when one has been assigned to your account. 06 ### No referral earning ceiling There is no programme cap on rewards from qualifying referrals. Results depend on real purchases and continued paid service. FROM INTRODUCTION TO REWARD ## Four steps. One clear connection. 01 ### Prepare your partner brief Record your public channel, audience and preferred code. Downloading a brief does not create an account, assign a referral link or activate attribution. 02 ### Make the introduction Use your assigned link and available marketing materials to introduce the SwissOctet configurations that fit your audience. 03 ### Build your balance Programme rates are 20% for the first eligible paid month and 10% for later eligible paid months. Each commission depends on a verified qualifying purchase and the programme rules. 04 ### Choose your reward The crypto-withdrawal threshold is USD 27.99 in available commission. Service credit is the alternative programme reward; access requires a verified balance and an activated payout or billing service. RUN THE NUMBERS ## See what your network could build. Choose a real SwissOctet base plan. Adjust the number of referrals to explore the commission model. 01 / YOUR SCENARIO USD Active paying referrals clients Service family Configuration The 10% customer discount is included before commission is calculated. Uses the selected plan's shortest billing term. [Explore this service](https://swissoctet.com/services/vector/) MODEL / Vector VPS 01 ILLUSTRATIVE EARNINGS First paid month $10.65 5 referrals × 20% of the discounted monthly base Each later paid month $5.35 10% recurring commission 12-month scenario $69.50 All referrals remain active for 12 paid months Referred customer's base $10.66 / month equivalent $10.66 for the shortest 1-month term, after the 10% referral discount. Base plan only. First-invoice commission model $10.65 One paid month. Withdrawal requests start at $27.99 of approved balance. An estimate, not a balance or an income guarantee. Prices stay constant in this model. No extras, tax, refunds, cancellations or network fees are included. Actual rewards require attributed, eligible payments and confirmed programme records. YOUR SHARE OF THE VALUE ## Understand every part. 01 / PROGRAMME DETAILS ### One introduction can keep working month after month. The programme follows the service you refer: 20% commission on its first eligible paid month, then 10% on each subsequent eligible paid month or renewal. There is no referral earning cap and no fixed end date for recurring rewards while the qualifying service continues to be paid. Your customer receives an additional 10% referral discount on the current eligible base service price. Commission is calculated on the resulting eligible service amount actually paid. The estimate on this page excludes optional add-ons, taxes and network fees; it does not promise a particular income. A longer invoice does not turn every month into a first month. For an initial multi-month purchase, its eligible service amount is shared across the covered months: 20% applies to month one and 10% applies to each later month. Subsequent renewal invoices use the 10% recurring rate. Month one 20% of the net eligible base service amount allocated to the first paid month. Following months 10% of the net eligible base service amount allocated to each later paid month. Customer advantage An additional 10% referral discount on eligible base services, with the final charge shown before payment. 02 / PROGRAMME DETAILS ### Know what your recommendations are doing. A useful partner workspace brings assigned referral links, brand materials and commission records together. Registration and referral attribution are currently unavailable. Download the artwork and prepare a brief with the SwissOctet configurations that fit your audience. Commission records must separate entries awaiting validation from rewards available to use or withdraw. Refunds and cancellations can affect eligibility. Check attribution windows, validation and adjustment rules before promoting a link. The calculator estimates programme amounts; it does not record customer activity or create payable earnings. Referral activity Activity reporting applies to assigned referral links and verified qualifying purchases. Attribution is currently unavailable. Commission ledger Commission records distinguish the first month, recurring paid months and eligibility adjustments. An estimate is not an available balance. Brand resources Download SwissOctet artwork and choose a service relevant to your audience. Referral links require a confirmed partner account. 03 / PROGRAMME DETAILS ### Take your balance in crypto. Or put it back to work. Programme payout terms set a minimum available balance of USD 27.99 and list Bitcoin (BTC), Monero (XMR) and Litecoin (LTC). Payout requests are currently unavailable. A withdrawal requires an approved balance and verified destination, asset and network. Service credit is the programme alternative to a crypto withdrawal. Applying credit requires a verified available balance and an authoritative service charge. Neither the calculator nor a downloaded brief creates a credit balance or records a withdrawal. - Minimum available balance for a crypto withdrawal: USD 27.99. - Programme payout assets: BTC, XMR and LTC. - Alternative use: spend earned balance on SwissOctet services. - The final payout quote must state the asset, destination, conversion and any applicable fees. 04 / PROGRAMME DETAILS ### Turn useful expertise into better introductions. A deployment guide, an informed configuration comparison or a community recommendation can be the start of a lasting referral. Developers, technical publishers, studios and specialist communities can introduce SwissOctet where its Swiss location and service specifications fit the project. Show what a configuration includes, explain the relevant options and disclose your referral relationship. Keep customer lists, passwords and wallet recovery phrases out of your application. Your own public promotion channel and an outline of the audience are enough to prepare a useful brief. Creators and educators Connect a practical tutorial or comparison to a configuration your readers can understand. Developers and studios Give clients a clear infrastructure choice and explain your role in the recommendation. Specialist communities Share relevant hosting choices where recommendations are welcome and useful. BUILT FOR YOUR CHANNEL ## A Swiss signature. Ready to share. Original SwissOctet banners for your website or publication. Download the artwork and add a referral link only after it has been approved and assigned to you. +SwissOctet Independent infrastructure. A Swiss connection. SWITZERLAND / CH · SWISSOCTET.COM Social / editorial · 1200 × 628 SVG +SwissOctet Swiss infrastructure. Your private core. Website banner · 728 × 90 SVG A GOOD CONNECTION STARTS HERE ## Bring your audience. Build the next connection. The programme has no joining fee. Use this brief to describe your channel and preferred code. Registration, referral attribution and withdrawals are currently unavailable. Payout assets BTC XMR LTC or SwissOctet credit Affiliate payout assets are separate from customer checkout currencies. Monero is listed for affiliate payouts. BEFORE YOUR FIRST REFERRAL ## The details that matter. ### Is joining free, and how is an account activated? The programme has no registration fee. Registration and automatic activation are currently unavailable. Prepare and download a partner brief; the file does not create an account or working referral link. ### How much can an eligible referral earn? The rate is 20% for the first eligible paid month and 10% for subsequent eligible paid months or renewals. There is no referral earning ceiling. Your actual balance depends on qualifying paid service, eligibility checks and any refund or cancellation adjustments. ### What happens when the first invoice covers several months? The eligible service amount is allocated across the covered months. On the initial invoice, the first month earns 20% and later months earn 10%. A renewal invoice uses the 10% recurring rate. The calculator models this monthly allocation; it does not apply 20% to the whole first multi-month invoice. ### What does my referred customer receive? A qualifying referral receives an additional 10% discount on the current eligible base service price. This is the referral programme advantage; the final order must show the applicable price before payment. The page estimate excludes optional add-ons, taxes and network fees. ### Which referral and marketing tools does the programme cover? The programme covers assigned referral links, activity reporting, commission records and SwissOctet marketing artwork. Registration and attribution are currently unavailable. Downloadable banners and the calculator can be used without creating tracked referrals or payable earnings. ### When can I withdraw, and which crypto assets are supported? The programme specifies a minimum available balance of USD 27.99 and Bitcoin (BTC), Monero (XMR) or Litecoin (LTC) payouts. Withdrawal requests are currently unavailable. An authorised withdrawal must identify its asset, destination, conversion and applicable fees. ### Can I use my earnings for SwissOctet hosting? The programme includes service credit as an alternative to a crypto withdrawal. Credit requires a verified available balance and authoritative service charge before it can be used. ### What should I know before promoting a referral link? Describe services accurately, disclose your referral relationship and choose configurations that fit the audience. Verify attribution duration, validation timing, self-referral eligibility and refund handling for your assigned link. The calculator provides an estimate, not an income guarantee. KNOW THE INFRASTRUCTURE YOU RECOMMEND ## Your reputation. Our Swiss core. Explore the resources, billing periods and available choices before introducing a service to your audience. [Explore the Swiss catalogue](https://swissoctet.com/catalogue/) --- # SwissOctet Terms: Catalogue Scope and Responsible Use Canonical URL: https://swissoctet.com/terms/ Usage framework ## Clear rules before starting. Confidentiality has value when accompanied by a readable framework. Here are the site's principles and the points to be finalised for the service opening. Review the configuration, delivery conditions and payment terms before committing to an order. A saved selection or receiving address alone does not authorise a transfer. 01 / SWISSOCTET ## The role of this site SwissOctet presents a catalogue and lets you compare, select and prepare a configuration. A saved selection does not reserve a service, form a contract or confirm availability. 02 / SWISSOCTET ## Before confirming an order Confirm the operator’s identity, availability, delivery timeframe, applicable tax, renewal, cancellation and refund terms before sending funds. The fixed-address checkout provides a browser quote with complete transfer instructions; it does not issue a server invoice or confirm an accepted order. Payment verification and service delivery remain separate backend operations. 03 / SWISSOCTET ## Invoices, addresses and confirmations Review the complete checkout instructions: asset, network, exact amount, receiving address and expiry. Keep the client reference and exported record privately. A receiving address alone does not specify a payment, and a browser record does not prove receipt of funds. 04 / SWISSOCTET ## Use that respects others Use services only for authorised activity. Attacks, phishing, fraud, spam and activity that harms people or network stability are incompatible with this requirement. Review the service's acceptable-use rules, incident procedure and contact channel before deployment. 05 / SWISSOCTET ## Administration of your environment The user must secure their access, maintain their software, comply with applicable licences and manage the data they host. The exact division of tasks with the operator will depend on the chosen offering and will be described in its conditions. 06 / SWISSOCTET ## Backups and continuity A backup strategy must be planned before going into production. Included or optional backups, recovery limits and continuity commitments remain to be confirmed for each service. 07 / SWISSOCTET ## Confidentiality and official requests Review the service-specific policy for the information collected, its retention and the handling of access requests. The absence of documentary KYC does not remove applicable legal obligations. 08 / SWISSOCTET ## Changes to the document Changes to service conditions must be dated and communicated clearly before they apply. Review the terms associated with your order when the service or its conditions change. [Explore the infrastructure](https://swissoctet.com/catalogue/) --- # SwissOctet Insights: Practical Infrastructure Guides Canonical URL: https://swissoctet.com/insights/ SWISSOCTET / INSIGHTS & FIELD GUIDES ## Clarity for what comes next. Go deeper than the spec sheet. Practical knowledge for private infrastructure, sharper decisions and systems you can actually operate. Explore the library Find your starting point ENGINEERING PRINCIPLES. PRACTICAL DECISIONS. PRIMARY SOURCES. KNOWLEDGE / CONNECTED COMPUTE Understand the workload. PRIVACY Know the boundaries. OPERATIONS Build for day two. AN INTERCONNECTED WAY TO THINK 32 In-depth field guides 08 Connected disciplines 04 Learning paths 20 Terms, made clear THE STARTING POINT ## A better question. A better configuration. FEATURED GUIDE / CLOUD & VPS ### [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/) Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. Read the field guide 4 min read THE KNOWLEDGE LIBRARY ## Find your next clear answer. From a first VPS to a recovery drill. Explore the decisions that shape your infrastructure. Reading level 32 guides · All disciplines EXPLORE AT YOUR OWN DEPTH FIELD NOTE / 01 Cloud & VPS Foundation ### [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/) Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. 4 min read [Read the guide](https://swissoctet.com/insights/choose-a-vps-by-workload/) FIELD NOTE / 02 Dedicated & GPU Foundation ### [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/) Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. 4 min read [Read the guide](https://swissoctet.com/insights/vps-or-dedicated-server/) FIELD NOTE / 03 Storage & recovery Foundation ### [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/) Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. 4 min read [Read the guide](https://swissoctet.com/insights/nvme-storage-when-it-matters/) FIELD NOTE / 04 Crypto payments Foundation ### [Crypto checkout and the limits of payment privacy](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/) Understand the asset, network and confirmation journey, and protect the information that connects your project to a payment. 4 min read [Read the guide](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/) FIELD NOTE / 05 Day-two operations Applied ### [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/) Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. 4 min read [Read the guide](https://swissoctet.com/insights/build-a-backup-you-can-restore/) FIELD NOTE / 06 Network engineering Foundation ### [Bandwidth, port speed and transfer: read the full picture](https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/) Estimate the data your project moves and understand why a larger port is only one part of network performance. 4 min read [Read the guide](https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/) FIELD NOTE / 07 Privacy by design Foundation ### [Swiss data residency: map the whole service](https://swissoctet.com/insights/swiss-data-residency-map/) A Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment. 6 min read [Read the guide](https://swissoctet.com/insights/swiss-data-residency-map/) FIELD NOTE / 08 Privacy by design Foundation ### [No KYC and privacy: understand the difference](https://swissoctet.com/insights/no-kyc-is-not-anonymity/) Document-free onboarding addresses one collection point. Understand the other records, access paths and payment traces around a hosted project. 6 min read [Read the guide](https://swissoctet.com/insights/no-kyc-is-not-anonymity/) FIELD NOTE / 09 Day-two operations Applied ### [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/) Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. 6 min read [Read the guide](https://swissoctet.com/insights/threat-model-a-hosted-project/) FIELD NOTE / 10 Cloud & VPS Applied ### [Size VPS CPU and memory from a real workload](https://swissoctet.com/insights/size-vps-cpu-and-memory/) Build a memory budget, inspect contention and separate one busy thread from work that can use several virtual cores. 6 min read [Read the guide](https://swissoctet.com/insights/size-vps-cpu-and-memory/) FIELD NOTE / 11 Day-two operations Applied ### [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/) Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. 6 min read [Read the guide](https://swissoctet.com/insights/secure-windows-rdp-administration/) FIELD NOTE / 12 Day-two operations Applied ### [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/) Secure administration, expose only required services and establish updates and recovery without locking yourself out. 6 min read [Read the guide](https://swissoctet.com/insights/linux-vps-hardening-baseline/) FIELD NOTE / 13 Storage & recovery Advanced ### [Measure NVMe performance without misleading yourself](https://swissoctet.com/insights/nvme-benchmark-methodology/) Define the I/O pattern, control cache effects and inspect latency distributions before drawing an application conclusion from a disk test. 6 min read [Read the guide](https://swissoctet.com/insights/nvme-benchmark-methodology/) FIELD NOTE / 14 Dedicated & GPU Advanced ### [Build a GPU VRAM budget before choosing hardware](https://swissoctet.com/insights/gpu-vram-budget-for-real-workloads/) Account for weights, activations, caches and temporary buffers, then test the peak workload rather than the model file alone. 6 min read [Read the guide](https://swissoctet.com/insights/gpu-vram-budget-for-real-workloads/) FIELD NOTE / 15 Dedicated & GPU Applied ### [A dedicated-server migration runbook that protects the data](https://swissoctet.com/insights/dedicated-server-migration-runbook/) Rehearse the move, establish a consistent data boundary and define what rollback means after the new system accepts writes. 6 min read [Read the guide](https://swissoctet.com/insights/dedicated-server-migration-runbook/) FIELD NOTE / 16 Web & onion Foundation ### [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/) Compare application requirements, control and maintenance responsibilities rather than treating a VPS as the automatic next step for every website. 6 min read [Read the guide](https://swissoctet.com/insights/web-hosting-or-your-own-vps/) FIELD NOTE / 17 Day-two operations Applied ### [Turn RPO and RTO into a recovery budget you can test](https://swissoctet.com/insights/rpo-rto-recovery-budget/) Translate acceptable data loss and interruption into a timed recovery plan, with dependencies, restore capacity and a measurable exercise. 4 min read [Read the guide](https://swissoctet.com/insights/rpo-rto-recovery-budget/) FIELD NOTE / 18 Storage & recovery Applied ### [Snapshots and backups: choose the failure you need to survive](https://swissoctet.com/insights/snapshots-backups-consistency/) Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection. 4 min read [Read the guide](https://swissoctet.com/insights/snapshots-backups-consistency/) FIELD NOTE / 19 Storage & recovery Foundation ### [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/) Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. 4 min read [Read the guide](https://swissoctet.com/insights/object-file-block-storage/) FIELD NOTE / 20 Network engineering Advanced ### [Size a transfer with latency, concurrency and throughput measurements](https://swissoctet.com/insights/size-throughput-with-bandwidth-delay/) Build a repeatable transfer model using payload volume, delivery windows and round-trip time, then test it without confusing a port label with useful throughput. 4 min read [Read the guide](https://swissoctet.com/insights/size-throughput-with-bandwidth-delay/) FIELD NOTE / 21 Network engineering Advanced ### [Plan a 40, 100 or 200 Gbps origin as a complete system](https://swissoctet.com/insights/plan-40-100-200-gbps/) Translate large port classes into storage, CPU, concurrency and operational questions before selecting a high-volume distribution configuration. 4 min read [Read the guide](https://swissoctet.com/insights/plan-40-100-200-gbps/) FIELD NOTE / 22 Web & onion Applied ### [A domain, DNS and TLS cutover runbook for a new server](https://swissoctet.com/insights/dns-tls-cutover-runbook/) Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections. 4 min read [Read the guide](https://swissoctet.com/insights/dns-tls-cutover-runbook/) FIELD NOTE / 23 Web & onion Applied ### [Publish an onion service without overlooking the application](https://swissoctet.com/insights/publish-onion-service-safely/) Plan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model. 4 min read [Read the guide](https://swissoctet.com/insights/publish-onion-service-safely/) FIELD NOTE / 24 Crypto payments Foundation ### [Choose the asset and network before preparing a crypto payment](https://swissoctet.com/insights/choose-crypto-asset-network/) Read a payment route as a complete asset-and-network pair, then verify invoice instructions, token identity and the amount delivered before authorising a transfer. 4 min read [Read the guide](https://swissoctet.com/insights/choose-crypto-asset-network/) FIELD NOTE / 25 Crypto payments Advanced ### [From detected transaction to reconciled order: confirmations and reorgs](https://swissoctet.com/insights/confirmations-reorgs-order-reconciliation/) Design payment states around verified chain evidence, explicit acceptance rules and unambiguous order association rather than a browser claim that funds were sent. 4 min read [Read the guide](https://swissoctet.com/insights/confirmations-reorgs-order-reconciliation/) FIELD NOTE / 26 Day-two operations Applied ### [Build monitoring that leads to a useful incident response](https://swissoctet.com/insights/monitoring-incident-response-playbook/) Connect application symptoms, actionable alerts and a small response playbook so that an operator can make clear decisions when a service degrades. 4 min read [Read the guide](https://swissoctet.com/insights/monitoring-incident-response-playbook/) FIELD NOTE / 27 Cloud & VPS Applied ### [Give your AI workers a bounded place to run](https://swissoctet.com/insights/give-ai-workers-a-bounded-runtime/) Separate model inference from orchestration, size the actual worker and limit what its tools can change before putting an AI workflow on a server. 4 min read [Read the guide](https://swissoctet.com/insights/give-ai-workers-a-bounded-runtime/) FIELD NOTE / 28 Web & onion Applied ### [Choose a hosting operating model before choosing a cloud](https://swissoctet.com/insights/choose-a-hosting-operating-model/) Compare shared hosting, a VPS, dedicated hardware and large cloud platforms through responsibility, recovery, dependencies and the complete operating budget. 4 min read [Read the guide](https://swissoctet.com/insights/choose-a-hosting-operating-model/) FIELD NOTE / 29 Network engineering Foundation ### [Choose a traffic path: server, tunnel or proxy](https://swissoctet.com/insights/choose-a-server-tunnel-or-proxy/) Understand what a VPS, VPN and proxy each change, then select routing, protocols and operating responsibilities from the connection you actually need. 4 min read [Read the guide](https://swissoctet.com/insights/choose-a-server-tunnel-or-proxy/) FIELD NOTE / 30 Cloud & VPS Foundation ### [Understand the machine boundary behind your VPS](https://swissoctet.com/insights/understand-the-vps-machine-boundary/) Read KVM, virtual hardware, containers and dedicated servers as operating boundaries, then maintain the shell and services inside the boundary you choose. 4 min read [Read the guide](https://swissoctet.com/insights/understand-the-vps-machine-boundary/) FIELD NOTE / 31 Network engineering Foundation ### [Plan addresses and DNS as parts of your deployment](https://swissoctet.com/insights/plan-addresses-and-dns-for-deployment/) Separate public, private, static and dedicated addresses, then map forward DNS, reverse DNS and TLS to the parties that can configure them. 4 min read [Read the guide](https://swissoctet.com/insights/plan-addresses-and-dns-for-deployment/) FIELD NOTE / 32 Web & onion Applied ### [Separate your public web edge from the application](https://swissoctet.com/insights/separate-the-web-edge-from-the-app/) Give the web server, reverse proxy and application distinct responsibilities, with deliberate origin access, TLS, request limits and an incident path. 4 min read [Read the guide](https://swissoctet.com/insights/separate-the-web-edge-from-the-app/) FOLLOW A THREAD ## Knowledge that builds on itself. A purposeful route through the library. Start with the foundations, then connect the operational details. LEARNING PATH / 01 ### Launch your first workload Choose resources, prepare the environment and put a site online. 1. [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/) 2. [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/) 3. [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/) 14 min · 3 connected guides LEARNING PATH / 02 ### Design for confidentiality Understand data location, exposure and the payment trail. 1. [Swiss data residency: map the whole service](https://swissoctet.com/insights/swiss-data-residency-map/) 2. [Crypto checkout and the limits of payment privacy](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/) 3. [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/) 16 min · 3 connected guides LEARNING PATH / 03 ### Scale without guessing Connect physical capacity, networking and storage behaviour. 1. [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/) 2. [Bandwidth, port speed and transfer: read the full picture](https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/) 3. [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/) 12 min · 3 connected guides LEARNING PATH / 04 ### Prepare for the unexpected Plan recovery, secure access and test the way back. 1. [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/) 2. [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/) 3. [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/) 12 min · 3 connected guides THE DECISION WORKBENCH ## Turn assumptions into numbers. Two small planning tools. Calculations are illustrative, with their assumptions visible. PLAINLY EXPLAINED ## The language of infrastructure. No unexplained acronyms. A compact reference for the concepts you will encounter in these guides. ### vCPU+ A virtual processor allocated to a virtual machine. It describes a scheduling resource, not a guaranteed physical core. ### KVM+ Linux kernel virtualization used to run isolated virtual machines with their own operating systems. ### NVMe+ A storage protocol designed for flash devices over PCIe. Application performance still depends on the workload and configuration. ### VRAM+ Memory on a GPU. Model weights, activations, batch size and runtime overhead all consume it. ### RPO+ Recovery point objective: the maximum data age your recovery plan is designed to tolerate. ### RTO+ Recovery time objective: the time your recovery plan aims to take before a usable service returns. ### Snapshot+ A point-in-time view of a system or volume. A copy in the same failure domain does not replace an independent backup. ### Failure domain+ A shared dependency whose failure can affect several resources at once, such as one host or storage system. ### Gbps+ Gigabits per second. Divide by eight to get the theoretical decimal gigabytes per second before overhead. ### Throughput+ The useful rate actually achieved by an application. It can be much lower than a network port’s line rate. ### Latency+ Time spent waiting for an operation or response. Lower latency can matter more than peak bandwidth for interactive work. ### IOPS+ Input/output operations per second. It is meaningful only alongside block size, queue depth and latency. ### TLS+ Transport Layer Security protects data in transit between endpoints that successfully authenticate and negotiate encryption. ### Onion service+ A service reached through Tor using an onion address, with different reachability and exposure properties from a public website. ### No KYC+ An onboarding model that does not request identity-verification documents. It does not describe every data flow or guarantee anonymity. ### Data residency+ Where specified data is stored or processed. It should be mapped across the main system, backups and other service providers. ### Threat model+ A description of the assets, adversaries, entry points and failure scenarios a security design needs to address. ### Confirmation+ Evidence that a transaction has been included in a blockchain. Its operational meaning differs between networks. ### Finality+ The point at which a transaction is treated as irreversible under a network’s consensus rules and the recipient’s policy. ### Reorganisation+ A change in a blockchain’s accepted history that can affect transactions previously seen in a block. OUR EDITORIAL APPROACH ## Useful knowledge has a foundation. 01 ### Start with the decision. Each guide explains a concrete infrastructure choice, then gives you a checklist to turn it into a next step. 02 ### Show the source. Primary documentation sits beside the guidance. Follow it for implementation details and version-specific behaviour. 03 ### Keep the boundaries clear. Examples are labelled. Architecture advice is separated from service specifications, availability and contractual conditions. BEFORE YOU GO DEEPER ## A few useful answers. ### Where should I start?+ Choose a learning path for a connected introduction, or search for the exact decision you need to make. The sizing guide is a useful first step before comparing configurations. ### Are these guides specific to SwissOctet?+ The engineering principles apply broadly. Related infrastructure links connect each guide to SwissOctet’s Swiss catalogue; a guide is not a promise of availability or measured performance. ### How are the guides sourced?+ Each guide links to primary documentation and distinguishes engineering principles from product-specific conditions. Check the linked documentation before implementing version-dependent settings. ### Can I save or share an article?+ Save a guide to this browser, copy its direct link, or download its deployment checklist. Saved guides do not require an account and are not synchronised between devices. ### Does Swiss location guarantee anonymity?+ Location is one part of a privacy design. Identity documents, account data, payment records, service logs, backups and your application all need separate consideration. ### What should I verify before deploying?+ Check the actual configuration, network limits, backup and restore process, operating-system support, access controls and payment instructions. Use a guide’s checklist to turn assumptions into verification steps. MAKE KNOWLEDGE PRACTICAL ## Understand it. Then build it. Put the principles to work with infrastructure located in Switzerland. [Explore Swiss infrastructure](https://swissoctet.com/catalogue/) --- # Swiss VPS, Windows RDP and Storage Compute \| SwissOctet Canonical URL: https://swissoctet.com/catalogue/compute/ SWISS INFRASTRUCTURE ## Cloud compute on Swiss ground. VPS, NVMe, RDP & storage. Compare the configurations, specifications and relevant options. 18 service families 55 configurations CH Switzerland Sort services Browse by category 4 SERVICES / SWITZERLAND Base monthly prices in USD · Options shown separately Cloud compute / CH ### Vector VPS Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. 6 configurations · Switzerland From $11.84 / month 1-month base term · Add-ons separate VCPU 2 x Xeon E5-2680 v4 RAM 1GB DDR4 Storage 30GB SSD [Explore plans](https://swissoctet.com/services/vector/) Cloud compute / CH ### DeskLink RDP A Windows workspace that follows you. Remote desktop access, configurable resources and a Swiss location. 4 configurations · Switzerland From $22.95 / month 1-month base term · Add-ons separate VCPU 4 x Xeon E5-2680 v4 RAM 2GB DDR4 Storage 35GB SSD [Explore plans](https://swissoctet.com/services/desklink/) Cloud compute / CH ### Pulse NVMe Fast NVMe storage for applications where I/O is part of the performance equation. 5 configurations · Switzerland From $13.77 / month 1-month base term · Add-ons separate VCPU 4 x Xeon E5-2680 v4 RAM 1GB DDR4 Storage 30GB NVMe [Explore plans](https://swissoctet.com/services/pulse/) Cloud compute / CH ### Vault Storage Room for media, archives and growing datasets. A storage-focused Linux configuration. 1 configuration · Switzerland From $62.42 / month 1-month base term · Add-ons separate CPU Cores 2 RAM 8GB SAN Disk Size \[GiB\] 5000 GB (Upgradable) [Explore plans](https://swissoctet.com/services/vault/) ### Need a starting point? Choose by workload. 8 project paths START WITH YOUR PROJECT ## What will you build? A useful starting point, based on what you want to run. Open the plans to check the exact resources and options. ### Apps & APIs An independent Linux environment for your application stack. [Vector VPS From $11.84 / month](https://swissoctet.com/services/vector/) 1-month base term · Add-ons separate [Explore NVMe compute](https://swissoctet.com/services/pulse/) ### Websites & publishing Web hosting for sites, domains and a familiar control panel. [Canvas Web From $12.85 / month](https://swissoctet.com/services/canvas/) 1-month base term · Add-ons separate [Explore onion hosting](https://swissoctet.com/services/veil/) ### Windows workspace A remote desktop with a choice of Windows configurations. [DeskLink RDP From $22.95 / month](https://swissoctet.com/services/desklink/) 1-month base term · Add-ons separate ### Archives & datasets A storage-focused environment for larger collections of data. [Vault Storage From $62.42 / month](https://swissoctet.com/services/vault/) 1-month base term · Add-ons separate ### GPU workloads Compare dedicated GPU resources with your software requirements. [Tensor GPU From $323.82 / month](https://swissoctet.com/services/tensor/) 1-month base term · Add-ons separate ### Your own hardware A physical machine for workloads that need dedicated resources. [Metal Origin From $146.88 / month](https://swissoctet.com/services/metal-origin/) 3-month minimum · $440.64 base total [Explore EPYC configurations](https://swissoctet.com/services/metal-epyc/) ### High-volume transfer Dedicated bandwidth plans for projects with substantial network needs. [Transit 40 From $1,926.86 / month](https://swissoctet.com/services/transit-40/) 1-month base term · Add-ons separate [Explore 100 Gbps plans](https://swissoctet.com/services/transit-100/) ### Security & private access Authorized security workspaces or a Swiss OpenVPN connection. [Sentinel Kali From $12.85 / month](https://swissoctet.com/services/sentinel-kali/) 1-month base term · Add-ons separate [Explore OpenVPN](https://swissoctet.com/services/shield/) Every configuration is listed for Switzerland. Capacity and compatibility depend on the selected plan. [Compare the full catalogue](https://swissoctet.com/catalogue/) Configuration availability, delivery and applicable tax are confirmed on your final quote. --- # Dedicated Servers and GPU Hardware in Switzerland \| SwissOctet Canonical URL: https://swissoctet.com/catalogue/dedicated/ SWISS INFRASTRUCTURE ## Dedicated & GPU on Swiss ground. Bare metal & accelerated compute. Compare the configurations, specifications and relevant options. 18 service families 55 configurations CH Switzerland Sort services Browse by category 6 SERVICES / SWITZERLAND Base monthly prices in USD · Options shown separately Dedicated & GPU / CH ### Tensor GPU Dedicated GPU configurations for accelerated compute, rendering and machine-learning workloads. 3 configurations · Switzerland From $323.82 / month 1-month base term · Add-ons separate CPU Intel Dual Xeon E5-2680 V4 GPU Nvidia Tesla P4 / T4 RAM 64GB DDR4 [Explore plans](https://swissoctet.com/services/tensor/) Dedicated & GPU / CH ### Metal Origin A practical entry to dedicated hardware. Your workload, on its own physical machine. 3 configurations · Switzerland From $146.88 / month 3-month minimum · $440.64 base total CPU Dual Intel Xeon X5670 RAM 96 GB DDR3 STORAGE 1 TB SSD SATA3 [Explore plans](https://swissoctet.com/services/metal-origin/) Dedicated & GPU / CH ### Metal Atlas Dedicated compute with more memory and storage headroom for established workloads. 4 configurations · Switzerland From $284.81 / month 1-month base term · Add-ons separate CPU Dual Xeon® E5-2680 V4 RAM 64 GB DDR4 ECC STORAGE 1 TB SSD SATA3 [Explore plans](https://swissoctet.com/services/metal-atlas/) Dedicated & GPU / CH ### Metal Zenith A step up in dedicated infrastructure for workloads that demand substantial resources. 3 configurations · Switzerland From $351.13 / month 1-month base term · Add-ons separate CPU Dual Intel Xeon ® Gold 6134 RAM 64 GB DDR4 STORAGE 1 TB SSD [Explore plans](https://swissoctet.com/services/metal-zenith/) Dedicated & GPU / CH ### Metal Hyper High-capacity dedicated configurations for intensive applications and larger deployments. 2 configurations · Switzerland From $642.59 / month 1-month base term · Add-ons separate CPU Dual Intel Gold 6430 RAM 64GB DDR5 STORAGE 1TB NVMe [Explore plans](https://swissoctet.com/services/metal-hyper/) Dedicated & GPU / CH ### Metal EPYC AMD-powered dedicated hardware for parallel workloads and serious compute. 4 configurations · Switzerland From $371.79 / month 1-month base term · Add-ons separate CPU AMD EPYC 7452 RAM 64GB DDR4 STORAGE 1TB NVMe [Explore plans](https://swissoctet.com/services/metal-epyc/) ### Need a starting point? Choose by workload. 8 project paths START WITH YOUR PROJECT ## What will you build? A useful starting point, based on what you want to run. Open the plans to check the exact resources and options. ### Apps & APIs An independent Linux environment for your application stack. [Vector VPS From $11.84 / month](https://swissoctet.com/services/vector/) 1-month base term · Add-ons separate [Explore NVMe compute](https://swissoctet.com/services/pulse/) ### Websites & publishing Web hosting for sites, domains and a familiar control panel. [Canvas Web From $12.85 / month](https://swissoctet.com/services/canvas/) 1-month base term · Add-ons separate [Explore onion hosting](https://swissoctet.com/services/veil/) ### Windows workspace A remote desktop with a choice of Windows configurations. [DeskLink RDP From $22.95 / month](https://swissoctet.com/services/desklink/) 1-month base term · Add-ons separate ### Archives & datasets A storage-focused environment for larger collections of data. [Vault Storage From $62.42 / month](https://swissoctet.com/services/vault/) 1-month base term · Add-ons separate ### GPU workloads Compare dedicated GPU resources with your software requirements. [Tensor GPU From $323.82 / month](https://swissoctet.com/services/tensor/) 1-month base term · Add-ons separate ### Your own hardware A physical machine for workloads that need dedicated resources. [Metal Origin From $146.88 / month](https://swissoctet.com/services/metal-origin/) 3-month minimum · $440.64 base total [Explore EPYC configurations](https://swissoctet.com/services/metal-epyc/) ### High-volume transfer Dedicated bandwidth plans for projects with substantial network needs. [Transit 40 From $1,926.86 / month](https://swissoctet.com/services/transit-40/) 1-month base term · Add-ons separate [Explore 100 Gbps plans](https://swissoctet.com/services/transit-100/) ### Security & private access Authorized security workspaces or a Swiss OpenVPN connection. [Sentinel Kali From $12.85 / month](https://swissoctet.com/services/sentinel-kali/) 1-month base term · Add-ons separate [Explore OpenVPN](https://swissoctet.com/services/shield/) Every configuration is listed for Switzerland. Capacity and compatibility depend on the selected plan. [Compare the full catalogue](https://swissoctet.com/catalogue/) Configuration availability, delivery and applicable tax are confirmed on your final quote. --- # 40, 100 and 200 Gbps Swiss Server Catalogue \| SwissOctet Canonical URL: https://swissoctet.com/catalogue/network/ SWISS INFRASTRUCTURE ## High bandwidth on Swiss ground. 40, 100 & 200 Gbps ports. Compare the configurations, specifications and relevant options. 18 service families 55 configurations CH Switzerland Sort services Browse by category 3 SERVICES / SWITZERLAND Base monthly prices in USD · Options shown separately High bandwidth / CH ### Transit 40 Dedicated configurations with a 40 Gbps port for bandwidth-intensive applications. 2 configurations · Switzerland From $1,926.86 / month 1-month base term · Add-ons separate CPU Dual Intel Gold 6134 RAM 64GB DDR4 STORAGE 1TB NVMe [Explore plans](https://swissoctet.com/services/transit-40/) High bandwidth / CH ### Transit 100 100 Gbps port configurations for demanding content distribution and network workloads. 1 configuration · Switzerland From $7,343.00 / month 1-month base term · Add-ons separate CPU Dual Intel Xeon ® Gold 6134 RAM 128 GB DDR4 STORAGE 1 TB SSD [Explore plans](https://swissoctet.com/services/transit-100/) High bandwidth / CH ### Transit 200 200 Gbps port configurations for projects operating at a different network scale. 1 configuration · Switzerland From $13,768.93 / month 1-month base term · Add-ons separate CPU Dual Intel Gold 6430 RAM 64GB DDR4 STORAGE 1TB NVMe [Explore plans](https://swissoctet.com/services/transit-200/) ### Need a starting point? Choose by workload. 8 project paths START WITH YOUR PROJECT ## What will you build? A useful starting point, based on what you want to run. Open the plans to check the exact resources and options. ### Apps & APIs An independent Linux environment for your application stack. [Vector VPS From $11.84 / month](https://swissoctet.com/services/vector/) 1-month base term · Add-ons separate [Explore NVMe compute](https://swissoctet.com/services/pulse/) ### Websites & publishing Web hosting for sites, domains and a familiar control panel. [Canvas Web From $12.85 / month](https://swissoctet.com/services/canvas/) 1-month base term · Add-ons separate [Explore onion hosting](https://swissoctet.com/services/veil/) ### Windows workspace A remote desktop with a choice of Windows configurations. [DeskLink RDP From $22.95 / month](https://swissoctet.com/services/desklink/) 1-month base term · Add-ons separate ### Archives & datasets A storage-focused environment for larger collections of data. [Vault Storage From $62.42 / month](https://swissoctet.com/services/vault/) 1-month base term · Add-ons separate ### GPU workloads Compare dedicated GPU resources with your software requirements. [Tensor GPU From $323.82 / month](https://swissoctet.com/services/tensor/) 1-month base term · Add-ons separate ### Your own hardware A physical machine for workloads that need dedicated resources. [Metal Origin From $146.88 / month](https://swissoctet.com/services/metal-origin/) 3-month minimum · $440.64 base total [Explore EPYC configurations](https://swissoctet.com/services/metal-epyc/) ### High-volume transfer Dedicated bandwidth plans for projects with substantial network needs. [Transit 40 From $1,926.86 / month](https://swissoctet.com/services/transit-40/) 1-month base term · Add-ons separate [Explore 100 Gbps plans](https://swissoctet.com/services/transit-100/) ### Security & private access Authorized security workspaces or a Swiss OpenVPN connection. [Sentinel Kali From $12.85 / month](https://swissoctet.com/services/sentinel-kali/) 1-month base term · Add-ons separate [Explore OpenVPN](https://swissoctet.com/services/shield/) Every configuration is listed for Switzerland. Capacity and compatibility depend on the selected plan. [Compare the full catalogue](https://swissoctet.com/catalogue/) Configuration availability, delivery and applicable tax are confirmed on your final quote. --- # Swiss Web and Onion Hosting Configurations \| SwissOctet Canonical URL: https://swissoctet.com/catalogue/hosting/ SWISS INFRASTRUCTURE ## Web & onion hosting on Swiss ground. Websites & onion services. Compare the configurations, specifications and relevant options. 18 service families 55 configurations CH Switzerland Sort services Browse by category 2 SERVICES / SWITZERLAND Base monthly prices in USD · Options shown separately Web & onion hosting / CH ### Canvas Web A clean foundation for websites and publishing. Pick your storage, domains and hosting options. 4 configurations · Switzerland From $12.85 / month 1-month base term · Add-ons separate System Cpanel Domains 1 Subdomains 5 [Explore plans](https://swissoctet.com/services/canvas/) Web & onion hosting / CH ### Veil Onion A hosting configuration built around onion services, with capacity adapted to your project. 3 configurations · Switzerland From $27.54 / month 1-month base term · Add-ons separate Onion Address 1 CPU Cores 2 RAM 2GB [Explore plans](https://swissoctet.com/services/veil/) ### Need a starting point? Choose by workload. 8 project paths START WITH YOUR PROJECT ## What will you build? A useful starting point, based on what you want to run. Open the plans to check the exact resources and options. ### Apps & APIs An independent Linux environment for your application stack. [Vector VPS From $11.84 / month](https://swissoctet.com/services/vector/) 1-month base term · Add-ons separate [Explore NVMe compute](https://swissoctet.com/services/pulse/) ### Websites & publishing Web hosting for sites, domains and a familiar control panel. [Canvas Web From $12.85 / month](https://swissoctet.com/services/canvas/) 1-month base term · Add-ons separate [Explore onion hosting](https://swissoctet.com/services/veil/) ### Windows workspace A remote desktop with a choice of Windows configurations. [DeskLink RDP From $22.95 / month](https://swissoctet.com/services/desklink/) 1-month base term · Add-ons separate ### Archives & datasets A storage-focused environment for larger collections of data. [Vault Storage From $62.42 / month](https://swissoctet.com/services/vault/) 1-month base term · Add-ons separate ### GPU workloads Compare dedicated GPU resources with your software requirements. [Tensor GPU From $323.82 / month](https://swissoctet.com/services/tensor/) 1-month base term · Add-ons separate ### Your own hardware A physical machine for workloads that need dedicated resources. [Metal Origin From $146.88 / month](https://swissoctet.com/services/metal-origin/) 3-month minimum · $440.64 base total [Explore EPYC configurations](https://swissoctet.com/services/metal-epyc/) ### High-volume transfer Dedicated bandwidth plans for projects with substantial network needs. [Transit 40 From $1,926.86 / month](https://swissoctet.com/services/transit-40/) 1-month base term · Add-ons separate [Explore 100 Gbps plans](https://swissoctet.com/services/transit-100/) ### Security & private access Authorized security workspaces or a Swiss OpenVPN connection. [Sentinel Kali From $12.85 / month](https://swissoctet.com/services/sentinel-kali/) 1-month base term · Add-ons separate [Explore OpenVPN](https://swissoctet.com/services/shield/) Every configuration is listed for Switzerland. Capacity and compatibility depend on the selected plan. [Compare the full catalogue](https://swissoctet.com/catalogue/) Configuration availability, delivery and applicable tax are confirmed on your final quote. --- # Swiss VPN and Authorised Security Workspaces \| SwissOctet Canonical URL: https://swissoctet.com/catalogue/privacy/ SWISS INFRASTRUCTURE ## Security & privacy on Swiss ground. Security workspaces & VPN. Compare the configurations, specifications and relevant options. 18 service families 55 configurations CH Switzerland Sort services Browse by category 3 SERVICES / SWITZERLAND Base monthly prices in USD · Options shown separately Security & privacy / CH ### Sentinel Kali A dedicated Kali Linux workspace for security testing on systems you are authorized to assess. 4 configurations · Switzerland From $12.85 / month 1-month base term · Add-ons separate VCPU 2 x Xeon 5600 RAM 2GB DDR4 Storage 30GB SSD [Explore plans](https://swissoctet.com/services/sentinel-kali/) Security & privacy / CH ### Sentinel Parrot An isolated Parrot Security environment for research, development and authorized security work. 4 configurations · Switzerland From $12.85 / month 1-month base term · Add-ons separate VCPU 2 x Xeon 5600 RAM 2GB DDR4 Storage 30GB SSD [Explore plans](https://swissoctet.com/services/sentinel-parrot/) Security & privacy / CH ### Shield VPN A Swiss OpenVPN configuration for one device, with AES-256 encryption and unlimited traffic. 1 configuration · Switzerland From $4.59 / month 1-month base term · Add-ons separate Devices 1 Traffic Unlimited VPN Type OpenVPN [Explore plans](https://swissoctet.com/services/shield/) ### Need a starting point? Choose by workload. 8 project paths START WITH YOUR PROJECT ## What will you build? A useful starting point, based on what you want to run. Open the plans to check the exact resources and options. ### Apps & APIs An independent Linux environment for your application stack. [Vector VPS From $11.84 / month](https://swissoctet.com/services/vector/) 1-month base term · Add-ons separate [Explore NVMe compute](https://swissoctet.com/services/pulse/) ### Websites & publishing Web hosting for sites, domains and a familiar control panel. [Canvas Web From $12.85 / month](https://swissoctet.com/services/canvas/) 1-month base term · Add-ons separate [Explore onion hosting](https://swissoctet.com/services/veil/) ### Windows workspace A remote desktop with a choice of Windows configurations. [DeskLink RDP From $22.95 / month](https://swissoctet.com/services/desklink/) 1-month base term · Add-ons separate ### Archives & datasets A storage-focused environment for larger collections of data. [Vault Storage From $62.42 / month](https://swissoctet.com/services/vault/) 1-month base term · Add-ons separate ### GPU workloads Compare dedicated GPU resources with your software requirements. [Tensor GPU From $323.82 / month](https://swissoctet.com/services/tensor/) 1-month base term · Add-ons separate ### Your own hardware A physical machine for workloads that need dedicated resources. [Metal Origin From $146.88 / month](https://swissoctet.com/services/metal-origin/) 3-month minimum · $440.64 base total [Explore EPYC configurations](https://swissoctet.com/services/metal-epyc/) ### High-volume transfer Dedicated bandwidth plans for projects with substantial network needs. [Transit 40 From $1,926.86 / month](https://swissoctet.com/services/transit-40/) 1-month base term · Add-ons separate [Explore 100 Gbps plans](https://swissoctet.com/services/transit-100/) ### Security & private access Authorized security workspaces or a Swiss OpenVPN connection. [Sentinel Kali From $12.85 / month](https://swissoctet.com/services/sentinel-kali/) 1-month base term · Add-ons separate [Explore OpenVPN](https://swissoctet.com/services/shield/) Every configuration is listed for Switzerland. Capacity and compatibility depend on the selected plan. [Compare the full catalogue](https://swissoctet.com/catalogue/) Configuration availability, delivery and applicable tax are confirmed on your final quote. --- # SwissOctet Deployment Guide: From Choice to Recovery Canonical URL: https://swissoctet.com/guide/ Getting started guide ## From choice to first deployment. A good deployment is prepared. This framework helps you move from the catalogue to a controlled environment, without entrusting your private access. 01 / DEPLOYMENT ## Define the need. List your application, its system, the necessary memory, the data volume and the expected traffic. Allow a reasonable margin for growth. 02 / DEPLOYMENT ## Confirm the configuration. Check the Swiss location, resources, billing period and options. Confirm availability and delivery before scheduling a migration. Keep your configuration in the basket or export it for your records. 03 / DEPLOYMENT ## Prepare access. After the real confirmation of your order and the service being made available, use unique credentials and a suitable administration method. Keep keys, order tokens and recovery codes in a private space. Share only the access that is strictly necessary. 04 / DEPLOYMENT ## Install and secure. Update the system, configure the firewall and install your application. Check connection encryption, permissions and the separation between public and secret files. 05 / DEPLOYMENT ## Back up and test. Create an independent backup and test a restoration. Check your application, access and alerts before opening real traffic. 06 / DEPLOYMENT ## Deploy, then maintain. Perform the switchover, observe operation and keep a rollback procedure. Then schedule updates, backups and access reviews. [Explore the infrastructure](https://swissoctet.com/catalogue/) --- # Vector VPS > A Linux foundation for applications, private services and everyday server work. Choose the resources and operating system your project needs, with every configuration located in Switzerland. Canonical human page: https://swissoctet.com/services/vector/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. ## Starting configuration Starting configuration: Vector VPS 01 (vector-01); USD 11.84 effective monthly base on the shortest available 1-month term; USD 11.84 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 2 x Xeon E5-2680 v4 | | RAM | 1GB DDR4 | | Storage | 30GB SSD | | Bandwidth | 100 Mbp/s 2TB | | DDoS Protection | Layer 3-4 | ## Service capabilities ### Your own Linux environment KVM virtualization gives your project a separate operating system. Build the application stack, users and access rules around the way you work. ### Resources that fit the workload Compare CPU, DDR4 memory and SSD capacity across the range. Add cores, memory or disk space when your configuration needs a different balance. ### A choice of server foundations Select from the Linux images in the configurator, then choose an optional hosting panel or deployment platform suited to your application. ### Useful options, clearly separated Additional IPv4 addresses, VNC, management and backup retention are individual choices. Review their recurring cost before adding the configuration to your order. ## Example workloads ### Web applications and APIs Run a compact application stack with a database, reverse proxy and workers sized to your actual traffic. ### Private tools and services Keep dashboards, internal utilities or collaboration tools in a Swiss environment with your own access controls. ### Development and staging Give a project a separate test environment before making changes to a production deployment. ## A closer look ### Start with the workload, then choose the size Memory pressure, CPU use and growing data are different constraints. Select enough RAM for the application and its database, leave disk space for updates and logs, and compare the included traffic with your expected usage. The plan table keeps these resources visible side by side. ### Build your stack without adding unnecessary complexity A minimal Linux image is a good foundation when you want to manage the software directly. The configurator also includes hosting and deployment tools for projects that benefit from a panel. Choose only the software and management level you intend to use; optional licences remain separate from the server resources. ### Swiss offshore hosting with a restrained order flow All Vector configurations in this catalogue are Swiss. The order flow is designed without documentary KYC, so choosing a server does not require sending a passport or identity card. Secure administration, encrypted application traffic and independent backups remain part of your own deployment plan. ### Administration, connectivity and recovery The KVM plans describe the virtual machine; administration is a separate practical requirement. Confirm root credentials, the initial IPv4 allocation and a recovery route before deployment. Layer 3–4 protection is listed in the base specifications, with an advanced upgrade selected separately. Custom installation media, disk encryption and later reinstalls require an agreed installation and recovery procedure. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Vector VPS 01 A compact KVM Linux configuration for a small web service, command-line tools or a learning environment: 2 vCPUs, 1 GB of DDR4 memory and 30 GB of SSD storage. Configuration ID: vector-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 11.84. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 11.84; displayed effective monthly base: USD 11.84. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 2 x Xeon E5-2680 v4 | | RAM | 1GB DDR4 | | Storage | 30GB SSD | | Bandwidth | 100 Mbp/s 2TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 11.84 | USD 11.84 | | 3 months | USD 11.25 | USD 33.75 | | 6 months | USD 10.66 | USD 63.95 | | 12 months | USD 10.07 | USD 120.79 | | 18 months | USD 9.47 | USD 170.53 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-20.04-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | almalinux-9.6-x86_64 | USD 0.00 | No | | scientific-7.4-x86_64.img | USD 0.00 | No | | oracle-9.6-x86_64.qcow2 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | opensuse | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Server management | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Management Service | USD 0.00 | Yes | | Monthly Basic Management Service | USD 91.80 | No | | Monthly Advanced Management Service | USD 183.60 | No | | Custom Installations Services (Contact Support) | Operator quote required; not assumed free | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.31 | No | | LiteSpeed (5 domains) | USD 11.92 | No | | LiteSpeed (Unlimited domains) | USD 28.45 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | | CyberPanel | USD 0.00 | No | | aaPanel Free | USD 0.00 | No | | aaPanel Pro | USD 32.13 | No | | Coolify | USD 0.00 | No | | dokploy | USD 0.00 | No | | Deplo | USD 0.00 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Daily backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | 3 Days Retention | USD 4.59 | No | | 6 Days Retention | USD 13.77 | No | | 10 Days Retention | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### Vector VPS 02 Four vCPUs and 2 GB of DDR4 memory provide a modest Linux workspace for an API, development utilities or scheduled tasks, with 45 GB of SSD storage and a 3 TB traffic allowance. Configuration ID: vector-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 22.95. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 22.95; displayed effective monthly base: USD 22.95. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 4 x Xeon E5-2680 v4 | | RAM | 2GB DDR4 | | Storage | 45GB SSD | | Bandwidth | 200 Mbp/s 3TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 22.95 | USD 22.95 | | 3 months | USD 21.80 | USD 65.41 | | 6 months | USD 20.66 | USD 123.93 | | 12 months | USD 19.51 | USD 234.09 | | 18 months | USD 18.36 | USD 330.48 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-20.04-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | almalinux-9.6-x86_64 | USD 0.00 | No | | scientific-7.4-x86_64.img | USD 0.00 | No | | oracle-9.6-x86_64.qcow2 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | opensuse | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Server management | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Management Service | USD 0.00 | Yes | | Monthly Basic Management Service | USD 91.80 | No | | Monthly Advanced Management Service | USD 183.60 | No | | Custom Installations Services (Contact Support) | Operator quote required; not assumed free | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.31 | No | | LiteSpeed (5 domains) | USD 11.92 | No | | LiteSpeed (Unlimited domains) | USD 28.45 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | | CyberPanel | USD 0.00 | No | | aaPanel Free | USD 0.00 | No | | aaPanel Pro | USD 32.13 | No | | Coolify | USD 0.00 | No | | dokploy | USD 0.00 | No | | Deplo | USD 0.00 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Daily backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | 3 Days Retention | USD 4.59 | No | | 6 Days Retention | USD 13.77 | No | | 10 Days Retention | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### Vector VPS 03 A balanced starting point for several lightweight Linux services. This configuration combines 6 vCPUs, 4 GB of DDR4 memory and a 60 GB SSD, with a 200 Mbps port. Configuration ID: vector-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 32.13. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 32.13; displayed effective monthly base: USD 32.13. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 6 x Xeon E5-2680 v4 | | RAM | 4GB DDR4 | | Storage | 60GB SSD | | Bandwidth | 200 Mbp/s 5TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 32.13 | USD 32.13 | | 3 months | USD 30.52 | USD 91.57 | | 6 months | USD 28.92 | USD 173.50 | | 12 months | USD 27.31 | USD 327.72 | | 18 months | USD 25.70 | USD 462.67 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-20.04-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | almalinux-9.6-x86_64 | USD 0.00 | No | | scientific-7.4-x86_64.img | USD 0.00 | No | | oracle-9.6-x86_64.qcow2 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | opensuse | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Server management | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Management Service | USD 0.00 | Yes | | Monthly Basic Management Service | USD 91.80 | No | | Monthly Advanced Management Service | USD 183.60 | No | | Custom Installations Services (Contact Support) | Operator quote required; not assumed free | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.31 | No | | LiteSpeed (5 domains) | USD 11.92 | No | | LiteSpeed (Unlimited domains) | USD 28.45 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | | CyberPanel | USD 0.00 | No | | aaPanel Free | USD 0.00 | No | | aaPanel Pro | USD 32.13 | No | | Coolify | USD 0.00 | No | | dokploy | USD 0.00 | No | | Deplo | USD 0.00 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Daily backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | 3 Days Retention | USD 4.59 | No | | 6 Days Retention | USD 13.77 | No | | 10 Days Retention | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### Vector VPS 04 Move to 8 vCPUs and 6 GB of DDR4 memory for a busier application stack or a larger development environment. An 80 GB SSD and 7 TB traffic allowance round out the configuration. Configuration ID: vector-04. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 55.08. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 55.08; displayed effective monthly base: USD 55.08. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 8 x Xeon E5-2680 v4 | | RAM | 6GB DDR4 | | Storage | 80GB SSD | | Bandwidth | 300 Mbp/s 7TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 55.08 | USD 55.08 | | 3 months | USD 52.33 | USD 156.98 | | 6 months | USD 49.57 | USD 297.43 | | 12 months | USD 46.82 | USD 561.81 | | 18 months | USD 44.06 | USD 793.14 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-20.04-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | almalinux-9.6-x86_64 | USD 0.00 | No | | scientific-7.4-x86_64.img | USD 0.00 | No | | oracle-9.6-x86_64.qcow2 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | opensuse | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Server management | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Management Service | USD 0.00 | Yes | | Monthly Basic Management Service | USD 91.80 | No | | Monthly Advanced Management Service | USD 183.60 | No | | Custom Installations Services (Contact Support) | Operator quote required; not assumed free | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.31 | No | | LiteSpeed (5 domains) | USD 11.92 | No | | LiteSpeed (Unlimited domains) | USD 28.45 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | | CyberPanel | USD 0.00 | No | | aaPanel Free | USD 0.00 | No | | aaPanel Pro | USD 32.13 | No | | Coolify | USD 0.00 | No | | dokploy | USD 0.00 | No | | Deplo | USD 0.00 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Daily backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | 3 Days Retention | USD 4.59 | No | | 6 Days Retention | USD 13.77 | No | | 10 Days Retention | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### Vector VPS 05 A Linux configuration with 10 vCPUs, 8 GB of DDR4 memory and 100 GB of SSD storage for projects that need more room for processes, application files and working data. Configuration ID: vector-05. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 68.85. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 68.85; displayed effective monthly base: USD 68.85. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 10 x Xeon E5-2680 v4 | | RAM | 8GB DDR4 | | Storage | 100GB SSD | | Bandwidth | 300 Mbp/s 10TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 68.85 | USD 68.85 | | 3 months | USD 65.41 | USD 196.22 | | 6 months | USD 61.97 | USD 371.79 | | 12 months | USD 58.52 | USD 702.26 | | 18 months | USD 55.08 | USD 991.43 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-20.04-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | almalinux-9.6-x86_64 | USD 0.00 | No | | scientific-7.4-x86_64.img | USD 0.00 | No | | oracle-9.6-x86_64.qcow2 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | opensuse | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Server management | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Management Service | USD 0.00 | Yes | | Monthly Basic Management Service | USD 91.80 | No | | Monthly Advanced Management Service | USD 183.60 | No | | Custom Installations Services (Contact Support) | Operator quote required; not assumed free | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.31 | No | | LiteSpeed (5 domains) | USD 11.92 | No | | LiteSpeed (Unlimited domains) | USD 28.45 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | | CyberPanel | USD 0.00 | No | | aaPanel Free | USD 0.00 | No | | aaPanel Pro | USD 32.13 | No | | Coolify | USD 0.00 | No | | dokploy | USD 0.00 | No | | Deplo | USD 0.00 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Daily backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | 3 Days Retention | USD 4.59 | No | | 6 Days Retention | USD 13.77 | No | | 10 Days Retention | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### Vector VPS 06 The largest Vector memory allocation pairs 16 GB of DDR4 with 10 vCPUs and a 150 GB SSD. Its 400 Mbps port and 12 TB traffic allowance suit a broader mix of Linux services. Configuration ID: vector-06. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 91.80. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 91.80; displayed effective monthly base: USD 91.80. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 10 x Xeon E5-2680 v4 | | RAM | 16GB DDR4 | | Storage | 150GB SSD | | Bandwidth | 400 Mbp/s 12TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 91.80 | USD 91.80 | | 3 months | USD 87.21 | USD 261.63 | | 6 months | USD 82.62 | USD 495.71 | | 12 months | USD 78.03 | USD 936.35 | | 18 months | USD 73.44 | USD 1321.91 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-20.04-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | almalinux-9.6-x86_64 | USD 0.00 | No | | scientific-7.4-x86_64.img | USD 0.00 | No | | oracle-9.6-x86_64.qcow2 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | opensuse | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Server management | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Management Service | USD 0.00 | Yes | | Monthly Basic Management Service | USD 91.80 | No | | Monthly Advanced Management Service | USD 183.60 | No | | Custom Installations Services (Contact Support) | Operator quote required; not assumed free | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.31 | No | | LiteSpeed (5 domains) | USD 11.92 | No | | LiteSpeed (Unlimited domains) | USD 28.45 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | | CyberPanel | USD 0.00 | No | | aaPanel Free | USD 0.00 | No | | aaPanel Pro | USD 32.13 | No | | Coolify | USD 0.00 | No | | dokploy | USD 0.00 | No | | Deplo | USD 0.00 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Daily backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | 3 Days Retention | USD 4.59 | No | | 6 Days Retention | USD 13.77 | No | | 10 Days Retention | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ## Service questions ### How does Vector differ from Pulse NVMe? Vector lists SSD storage; Pulse lists NVMe storage. Compare the complete CPU, RAM, storage and network configuration rather than choosing on the disk label alone. ### Can I choose a Linux distribution? Yes. The operating-system selector shows the images available for this family. Check your application's support requirements and choose a maintained release before deployment. ### Are management and automatic backups included by default? They are configurable options. Check the selected management level and backup retention in your order summary; a default selection may contain neither. ### Does a faster port also increase the included traffic? Port speed and traffic allowance are separate characteristics. Check both the base plan and the selected options; increasing speed does not by itself change the traffic allowance. ### Will I need to submit an identity document? The SwissOctet order flow is designed without documentary KYC. Crypto payments still create a public transaction trail, and the absence of ID collection does not imply absolute anonymity. ### What level of operating-system control should I plan for? Vector is intended for customer-managed Linux workloads. Confirm full root access and the credential handover before delivery, then take responsibility for package updates, application installation and access rules. ### What does the protection selection cover? The base plans list Layer 3–4 network protection. The paid advanced choice is separate; leaving that upgrade unselected does not remove the listed baseline. Application-layer security remains a deployment responsibility. ### Is a dedicated IPv4 part of the initial setup? Additional IPv4 addresses are configurable. Confirm the initial dedicated address and any IPv6 allocation with the operator; the current plan table does not specify them. ### Can I use my own ISO or encrypt the system disk? Prepare the image, boot requirements and key-recovery method for operator review. Neither custom ISO installation nor a particular disk-encryption setup is confirmed by simply selecting a KVM plan. ### How are reinstalls and later upgrades arranged? The catalogue lets you compare larger resources now. For an existing server, confirm the upgrade or reinstall procedure, compatibility, downtime and backup requirements before making a change. ## Relevant guides - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [Crypto checkout and the limits of payment privacy](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/index.txt): Understand the asset, network and confirmation journey, and protect the information that connects your project to a payment. - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. - [Swiss data residency: map the whole service](https://swissoctet.com/insights/swiss-data-residency-map/index.txt): A Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment. - [No KYC and privacy: understand the difference](https://swissoctet.com/insights/no-kyc-is-not-anonymity/index.txt): Document-free onboarding addresses one collection point. Understand the other records, access paths and payment traces around a hosted project. - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [Size VPS CPU and memory from a real workload](https://swissoctet.com/insights/size-vps-cpu-and-memory/index.txt): Build a memory budget, inspect contention and separate one busy thread from work that can use several virtual cores. - [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/index.txt): Secure administration, expose only required services and establish updates and recovery without locking yourself out. - [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/index.txt): Compare application requirements, control and maintenance responsibilities rather than treating a VPS as the automatic next step for every website. - [Turn RPO and RTO into a recovery budget you can test](https://swissoctet.com/insights/rpo-rto-recovery-budget/index.txt): Translate acceptable data loss and interruption into a timed recovery plan, with dependencies, restore capacity and a measurable exercise. - [A domain, DNS and TLS cutover runbook for a new server](https://swissoctet.com/insights/dns-tls-cutover-runbook/index.txt): Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections. - [Publish an onion service without overlooking the application](https://swissoctet.com/insights/publish-onion-service-safely/index.txt): Plan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model. - [Choose the asset and network before preparing a crypto payment](https://swissoctet.com/insights/choose-crypto-asset-network/index.txt): Read a payment route as a complete asset-and-network pair, then verify invoice instructions, token identity and the amount delivered before authorising a transfer. - [From detected transaction to reconciled order: confirmations and reorgs](https://swissoctet.com/insights/confirmations-reorgs-order-reconciliation/index.txt): Design payment states around verified chain evidence, explicit acceptance rules and unambiguous order association rather than a browser claim that funds were sent. - [Build monitoring that leads to a useful incident response](https://swissoctet.com/insights/monitoring-incident-response-playbook/index.txt): Connect application symptoms, actionable alerts and a small response playbook so that an operator can make clear decisions when a service degrades. - [Give your AI workers a bounded place to run](https://swissoctet.com/insights/give-ai-workers-a-bounded-runtime/index.txt): Separate model inference from orchestration, size the actual worker and limit what its tools can change before putting an AI workflow on a server. - [Choose a hosting operating model before choosing a cloud](https://swissoctet.com/insights/choose-a-hosting-operating-model/index.txt): Compare shared hosting, a VPS, dedicated hardware and large cloud platforms through responsibility, recovery, dependencies and the complete operating budget. - [Choose a traffic path: server, tunnel or proxy](https://swissoctet.com/insights/choose-a-server-tunnel-or-proxy/index.txt): Understand what a VPS, VPN and proxy each change, then select routing, protocols and operating responsibilities from the connection you actually need. - [Understand the machine boundary behind your VPS](https://swissoctet.com/insights/understand-the-vps-machine-boundary/index.txt): Read KVM, virtual hardware, containers and dedicated servers as operating boundaries, then maintain the shell and services inside the boundary you choose. - [Plan addresses and DNS as parts of your deployment](https://swissoctet.com/insights/plan-addresses-and-dns-for-deployment/index.txt): Separate public, private, static and dedicated addresses, then map forward DNS, reverse DNS and TLS to the parties that can configure them. - [Separate your public web edge from the application](https://swissoctet.com/insights/separate-the-web-edge-from-the-app/index.txt): Give the web server, reverse proxy and application distinct responsibilities, with deliberate origin access, TLS, request limits and an incident path. --- # DeskLink RDP > Bring your Windows tools into a Swiss remote environment. DeskLink combines KVM resources with RDP access for applications, administration and a workspace you can reach from another device. Canonical human page: https://swissoctet.com/services/desklink/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. A Windows workspace that follows you. Remote desktop access, configurable resources and a Swiss location. ## Starting configuration Starting configuration: DeskLink RDP 01 (desklink-01); USD 22.95 effective monthly base on the shortest available 1-month term; USD 22.95 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 4 x Xeon E5-2680 v4 | | RAM | 2GB DDR4 | | Storage | 35GB SSD | | Bandwidth | 100Mbp/s 2TB | | DDoS Protection | Layer 3-4 | ## Service capabilities ### A familiar Windows environment Choose a Windows Server image from the configurator and build a remote workspace around the applications your project requires. ### Memory for the applications you use Compare the base RAM and CPU allocation, then add memory or cores when your software needs more working room. ### SSD space for an active desktop Keep applications and project files on the plan's SSD storage. Additional disk options help separate capacity planning from the choice of base tier. ### Backups and network choices Select optional daily backup retention and review port-speed upgrades. The order summary keeps each addition alongside your Windows configuration. ## Example workloads ### Windows application access Use software that requires Windows from a compatible remote desktop client, while the environment stays in Switzerland. ### Administration workbench Create a separate workspace for managing your own systems and running approved administrative tools. ### Application testing Validate Windows application behaviour in a remote environment before introducing changes to a working setup. ## A closer look ### Keep the workspace separate from the device Your remote environment and your local device play different roles: one runs the Windows applications, the other provides the desktop connection. DeskLink lets you plan the server resources independently of the laptop or workstation you connect from. Connection quality still depends on the route and the network at both ends. ### Choose resources for concurrent activity A lightweight utility, a browser session and a demanding business application do not consume the same amount of memory. Count the programs you will run together and allow space for the operating system. Verify application licences and any remote-session requirements before using the environment for multiple people. ### Protect the door to the desktop Treat RDP as an administration interface. Use strong, unique credentials, keep the Windows environment updated and restrict access through suitable network controls. A Swiss location and a no-KYC order flow reduce what you hand over at purchase; your access settings determine who can reach the workspace. ### A desktop connection is only one part of the setup RDP connects you to Windows, while administrative rights determine which software and settings you can change. Confirm the account permissions, address allocation and recovery access before delivery. The plans list KVM and SSD storage with baseline Layer 3–4 protection. A custom ISO, disk-encryption setup or later reinstall needs separate operator approval and a data-recovery plan. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### DeskLink RDP 01 An entry Windows remote workspace with 4 vCPUs, 2 GB of DDR4 memory and a 35 GB SSD. Choose the operating system and optional resources to match a focused desktop task. Configuration ID: desklink-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 22.95. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 22.95; displayed effective monthly base: USD 22.95. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 4 x Xeon E5-2680 v4 | | RAM | 2GB DDR4 | | Storage | 35GB SSD | | Bandwidth | 100Mbp/s 2TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 22.95 | USD 22.95 | | 3 months | USD 21.80 | USD 65.41 | | 6 months | USD 20.66 | USD 123.93 | | 12 months | USD 19.51 | USD 234.09 | | 15 months | USD 18.93 | USD 284.00 | | 18 months | USD 18.36 | USD 330.48 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | windows-2016 | USD 0.00 | Yes | | windows-2019 | USD 0.00 | No | | windows-2022 | USD 0.00 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 1.38 | No | | + 10GB SSD | USD 2.75 | No | | + 20GB SSD | USD 5.51 | No | | + 50GB SSD | USD 10.10 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | | 6 X Extra GB Memory | USD 41.31 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 5 X Extra CPU Core | USD 22.95 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### DeskLink RDP 02 A Windows workspace with 4 GB of DDR4 memory and 50 GB of SSD storage for everyday remote applications. The configuration includes 4 vCPUs and a 5 TB traffic allowance. Configuration ID: desklink-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 32.13. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 32.13; displayed effective monthly base: USD 32.13. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 4 x Xeon E5-2680 v4 | | RAM | 4GB DDR4 | | Storage | 50GB SSD | | Bandwidth | 200Mbp/s 5TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 32.13 | USD 32.13 | | 3 months | USD 30.52 | USD 91.57 | | 6 months | USD 28.92 | USD 173.50 | | 12 months | USD 27.31 | USD 327.72 | | 15 months | USD 26.51 | USD 397.61 | | 18 months | USD 25.70 | USD 462.67 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | windows-2016 | USD 0.00 | Yes | | windows-2019 | USD 0.00 | No | | windows-2022 | USD 0.00 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 1.38 | No | | + 10GB SSD | USD 2.75 | No | | + 20GB SSD | USD 5.51 | No | | + 50GB SSD | USD 10.10 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | | 6 X Extra GB Memory | USD 41.31 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 5 X Extra CPU Core | USD 22.95 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### DeskLink RDP 03 Six vCPUs, 6 GB of DDR4 memory and an 80 GB SSD give a Windows remote environment more room for applications and project files, alongside a 400 Mbps port. Configuration ID: desklink-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 55.08. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 55.08; displayed effective monthly base: USD 55.08. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 6 x Xeon E5-2680 v4 | | RAM | 6GB DDR4 | | Storage | 80GB SSD | | Bandwidth | 400Mbp/s 7TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 55.08 | USD 55.08 | | 3 months | USD 52.33 | USD 156.98 | | 6 months | USD 49.57 | USD 297.43 | | 12 months | USD 46.82 | USD 561.81 | | 15 months | USD 45.44 | USD 681.61 | | 18 months | USD 44.06 | USD 793.14 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | windows-2016 | USD 0.00 | Yes | | windows-2019 | USD 0.00 | No | | windows-2022 | USD 0.00 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 1.38 | No | | + 10GB SSD | USD 2.75 | No | | + 20GB SSD | USD 5.51 | No | | + 50GB SSD | USD 10.10 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | | 6 X Extra GB Memory | USD 41.31 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 5 X Extra CPU Core | USD 22.95 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### DeskLink RDP 04 A larger Windows configuration for workloads with more concurrent processes: 12 vCPUs, 12 GB of DDR4 memory, 100 GB of SSD storage and a 10 TB traffic allowance. Configuration ID: desklink-04. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 96.39. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 96.39; displayed effective monthly base: USD 96.39. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 12 x Xeon E5-2680 v4 | | RAM | 12GB DDR4 | | Storage | 100GB SSD | | Bandwidth | 400Mbp/s 10TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 96.39 | USD 96.39 | | 3 months | USD 91.57 | USD 274.71 | | 6 months | USD 86.75 | USD 520.50 | | 12 months | USD 81.93 | USD 983.17 | | 15 months | USD 79.52 | USD 1192.81 | | 18 months | USD 77.11 | USD 1388.00 | Technical input requested for an order: Desired Hostname (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | windows-2016 | USD 0.00 | Yes | | windows-2019 | USD 0.00 | No | | windows-2022 | USD 0.00 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 1.38 | No | | + 10GB SSD | USD 2.75 | No | | + 20GB SSD | USD 5.51 | No | | + 50GB SSD | USD 10.10 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | | 6 X Extra GB Memory | USD 41.31 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 5 X Extra CPU Core | USD 22.95 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ## Service questions ### Which Windows images can I select? The DeskLink configurator lists the Windows Server versions attached to this family. Check the selected image and its licensing terms in the configuration. ### Can I connect from a non-Windows device? You need a compatible RDP client on your device. Check your client's support for the selected Windows environment and test the connection before depending on it. ### Is this a multi-user desktop service? The catalogue specifies server resources, not an unlimited number of licensed remote sessions. Confirm the intended number of users and relevant Windows or application licences. ### What should I increase if applications run out of memory? Compare the RAM in the next plan or select an additional-memory option. More disk space or a faster network port will not resolve an application memory limit. ### Should I expose RDP to everyone on the internet? Restrict administration access to the sources that need it, use suitable firewall rules and keep recovery access available. The correct controls depend on your deployment. ### Can I install and administer my own Windows applications? Plan a customer-administered Windows environment and confirm full administrator rights at delivery. Each application must support the chosen image, resource allocation and remote-session model, with appropriate licences. ### Does DeskLink include NVMe storage? The published DeskLink plans list SSD. This catalogue does not describe those disks as NVMe; choose resources from the plan table. ### What is the baseline DDoS specification? The plans list Layer 3–4 protection. A paid advanced selection is separate from that baseline, and neither replaces Windows firewall rules or secure RDP access. ### Are a dedicated IP, custom ISO and reinstall controls included? Confirm address allocation and recovery access before delivery. Custom installation media, encrypted boot and reinstall procedures require operator review and an agreed recovery process. ## Relevant guides - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. - [Size VPS CPU and memory from a real workload](https://swissoctet.com/insights/size-vps-cpu-and-memory/index.txt): Build a memory budget, inspect contention and separate one busy thread from work that can use several virtual cores. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. - [Understand the machine boundary behind your VPS](https://swissoctet.com/insights/understand-the-vps-machine-boundary/index.txt): Read KVM, virtual hardware, containers and dedicated servers as operating boundaries, then maintain the shell and services inside the boundary you choose. --- # Pulse NVMe > Put storage-sensitive applications on an NVMe foundation in Switzerland. Pulse pairs Linux KVM environments with configurable CPU, memory and network resources for projects where disk activity matters. Canonical human page: https://swissoctet.com/services/pulse/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. Fast NVMe storage for applications where I/O is part of the performance equation. ## Starting configuration Starting configuration: Pulse NVMe 01 (pulse-01); USD 13.77 effective monthly base on the shortest available 1-month term; USD 13.77 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 4 x Xeon E5-2680 v4 | | RAM | 1GB DDR4 | | Storage | 30GB NVMe | | Bandwidth | 100Mbp/s 2TB | | DDoS Protection | Layer 3-4 | ## Service capabilities ### NVMe at the centre The base plans list NVMe storage for your system and application data. Size the volume around active data, updates and working files. ### CPU and memory in balance Disk performance is only one part of the stack. Compare the listed processor allocation and RAM alongside storage when choosing a Pulse plan. ### Linux images and hosting tools Choose a Linux image and optional hosting software in the configurator. A minimal system or a panel-based workflow can share the same NVMe foundation. ### An explicit network configuration Review port speed, traffic and optional IPv4 addresses independently. Add network capacity only where it fits the application's usage. ## Example workloads ### Database-driven applications Provide a foundation for applications that frequently read and write a working dataset, with enough RAM for the database. ### Build and development tools Run your own project builds, package preparation or staging workflows that use many small files. ### Active content platforms Host a publishing or commerce stack whose storage needs are more about active access than long-term archiving. ## A closer look ### Choose NVMe for the right reason Pulse is the storage-focused alternative to the standard SSD VPS range. It makes sense to compare when your application spends time waiting for disk operations. It is not a substitute for a well-sized database cache, efficient queries or enough memory. Measure the bottleneck before deciding which resource to increase. ### Configure the complete application environment The Linux image sets the starting point; the application stack determines the rest. Decide how you will deploy, update and administer the software, then choose optional hosting tools, CPU, memory and disk additions. Read the description of each storage addition rather than assuming it changes the base volume's technology. ### Privacy includes your working data A Swiss offshore location is only one layer of a private deployment. Keep credentials outside your public web directory, separate administrative and public access, and decide which application logs you actually need. Optional daily backups have their own retention choices; maintain a recovery plan appropriate to the data. ### Keep control as the working dataset grows The Pulse catalogue combines KVM with NVMe base storage and Layer 3–4 network protection. Root administration, initial address allocation and recovery access should be confirmed before delivery. Use the optional resources and hosting tools to define your starting configuration; changes to an existing instance, reinstallations and encrypted-disk recovery need an agreed procedure. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Pulse NVMe 01 Start with NVMe storage for a focused Linux workload. This KVM configuration combines 4 vCPUs, 1 GB of DDR4 memory and a 30 GB NVMe drive with a 2 TB traffic allowance. Configuration ID: pulse-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 13.77. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 13.77; displayed effective monthly base: USD 13.77. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 4 x Xeon E5-2680 v4 | | RAM | 1GB DDR4 | | Storage | 30GB NVMe | | Bandwidth | 100Mbp/s 2TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 13.77 | USD 13.77 | | 3 months | USD 13.08 | USD 39.24 | | 6 months | USD 12.39 | USD 74.36 | | 12 months | USD 11.70 | USD 140.45 | | 18 months | USD 11.02 | USD 198.29 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-24.04.3-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 4 X Extra CPU Core | USD 16.52 | No | | 8 X Extra CPU Core | USD 33.05 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 4 X Extra GB Memory | USD 25.70 | No | | 8 X Extra GB Memory | USD 51.41 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 6.43 | No | | Daily Backups (6 Days Retention) | USD 18.36 | No | | Daily Backups (10 Days Retention) | USD 45.90 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 15GB SSD | USD 20.20 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.26 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ### Pulse NVMe 02 A compact NVMe configuration for a small application or development service, with 4 vCPUs, 2 GB of DDR4 memory and 40 GB of storage on a 200 Mbps port. Configuration ID: pulse-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 26.62. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 26.62; displayed effective monthly base: USD 26.62. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 4 x Xeon E5-2680 v4 | | RAM | 2GB DDR4 | | Storage | 40GB NVMe | | Bandwidth | 200Mbp/s 3TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 26.62 | USD 26.62 | | 3 months | USD 25.29 | USD 75.87 | | 6 months | USD 23.96 | USD 143.76 | | 12 months | USD 22.63 | USD 271.54 | | 18 months | USD 21.30 | USD 383.35 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-24.04.3-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 4 X Extra CPU Core | USD 16.52 | No | | 8 X Extra CPU Core | USD 33.05 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 4 X Extra GB Memory | USD 25.70 | No | | 8 X Extra GB Memory | USD 51.41 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 6.43 | No | | Daily Backups (6 Days Retention) | USD 18.36 | No | | Daily Backups (10 Days Retention) | USD 45.90 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 15GB SSD | USD 20.20 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.26 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ### Pulse NVMe 03 Bring together 6 vCPUs, 4 GB of DDR4 memory and 50 GB of NVMe storage for a Linux application that performs frequent disk operations. Its traffic allowance is 5 TB. Configuration ID: pulse-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 41.31. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 41.31; displayed effective monthly base: USD 41.31. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 6 x Xeon E5-2680 v4 | | RAM | 4GB DDR4 | | Storage | 50GB NVMe | | Bandwidth | 200Mbp/s 5TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 41.31 | USD 41.31 | | 3 months | USD 39.24 | USD 117.73 | | 6 months | USD 37.18 | USD 223.07 | | 12 months | USD 35.11 | USD 421.36 | | 18 months | USD 33.05 | USD 594.86 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-24.04.3-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 4 X Extra CPU Core | USD 16.52 | No | | 8 X Extra CPU Core | USD 33.05 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 4 X Extra GB Memory | USD 25.70 | No | | 8 X Extra GB Memory | USD 51.41 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 6.43 | No | | Daily Backups (6 Days Retention) | USD 18.36 | No | | Daily Backups (10 Days Retention) | USD 45.90 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 15GB SSD | USD 20.20 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.26 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ### Pulse NVMe 04 A broader Linux workspace with 8 vCPUs and 6 GB of DDR4 memory. The 70 GB NVMe drive leaves room for a larger working dataset, with a 300 Mbps port and 7 TB of traffic. Configuration ID: pulse-04. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 60.59. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 60.59; displayed effective monthly base: USD 60.59. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 8 x Xeon E5-2680 v4 | | RAM | 6GB DDR4 | | Storage | 70GB NVMe | | Bandwidth | 300Mbp/s 7TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 60.59 | USD 60.59 | | 3 months | USD 57.56 | USD 172.67 | | 6 months | USD 54.53 | USD 327.17 | | 12 months | USD 51.50 | USD 617.99 | | 18 months | USD 48.47 | USD 872.46 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-24.04.3-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 4 X Extra CPU Core | USD 16.52 | No | | 8 X Extra CPU Core | USD 33.05 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 4 X Extra GB Memory | USD 25.70 | No | | 8 X Extra GB Memory | USD 51.41 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 6.43 | No | | Daily Backups (6 Days Retention) | USD 18.36 | No | | Daily Backups (10 Days Retention) | USD 45.90 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 15GB SSD | USD 20.20 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.26 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ### Pulse NVMe 05 The highest-capacity Pulse configuration combines 14 Xeon 5600 vCPUs, 16 GB of DDR4 memory and a 100 GB NVMe drive, plus a 400 Mbps port and a 10 TB traffic allowance. Configuration ID: pulse-05. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 105.57. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 105.57; displayed effective monthly base: USD 105.57. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 14 x Xeon 5600 | | RAM | 16GB DDR4 | | Storage | 100GB NVMe | | Bandwidth | 400Mbp/s 10TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 105.57 | USD 105.57 | | 3 months | USD 100.29 | USD 300.87 | | 6 months | USD 95.01 | USD 570.07 | | 12 months | USD 89.73 | USD 1076.80 | | 18 months | USD 84.46 | USD 1520.19 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ubuntu-24.04.3-x86_64 | USD 0.00 | Yes | | ubuntu-22.04.5-x86_64 | USD 0.00 | No | | fedora-42-x86_64 | USD 0.00 | No | | rocky-9.6-x86_64 | USD 0.00 | No | | debian-11-x86_64 | USD 0.00 | No | | debian-12-x86_64 | USD 0.00 | No | | ubuntu-24.04.3-x86_64 | USD 0.00 | No | | centos-9.6-x86_64 | USD 0.00 | No | | debian-13.0-x86_64 | USD 0.00 | No | | almalinux-10.1-x86_64 | USD 0.00 | No | | oracle-9.7-x86_64 | USD 0.00 | No | | oracle-10.0-x86_64 | USD 0.00 | No | | rocky-10.1-x86_64 | USD 0.00 | No | ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 4 X Extra CPU Core | USD 16.52 | No | | 8 X Extra CPU Core | USD 33.05 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Extra GB Memory | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 4 X Extra GB Memory | USD 25.70 | No | | 8 X Extra GB Memory | USD 51.41 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 6.43 | No | | Daily Backups (6 Days Retention) | USD 18.36 | No | | Daily Backups (10 Days Retention) | USD 45.90 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 15GB SSD | USD 20.20 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### Hosting software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional application | USD 0.00 | Yes | | Cpanel 5 accounts license | USD 38.56 | No | | Cpanel 30 accounts license | USD 45.90 | No | | Cpanel 100 accounts license | USD 64.26 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ## Service questions ### Does NVMe guarantee a specific application speed? No application benchmark is promised here. Performance depends on the complete resource allocation, software, dataset and workload; test with your own application. ### Is every optional disk addition NVMe? Read each option's label. The base plans specify NVMe, while an extra-disk option may describe SSD storage separately. Do not assume the two are identical. ### Can I add a hosting or deployment panel? Yes. The configurator lists the hosting-software choices for Pulse. Verify the panel's system requirements and any licence limits against your selected resources. ### Is Pulse suitable for storing a very large archive? It depends on capacity and access patterns. For a storage-heavy archive, compare Vault Storage as well; an active NVMe volume and bulk storage serve different needs. ### How do I protect application data after deployment? Use controlled access, application-appropriate encryption and tested backups. Select backup retention deliberately and keep a separate copy for failures beyond the primary environment. ### How much control do I have over the Linux stack? Pulse is intended for customer-administered applications. Confirm root access at delivery, then choose the supported packages, services and access rules for the operating system. ### Is network protection part of the base configuration? Layer 3–4 protection appears in the base specifications. The advanced DDoS choice is a separate upgrade; application security, rate limiting and backups still require their own plan. ### What should I confirm about IP addresses? The configurator lists additional IPv4 choices. Confirm the initial dedicated address, IPv6 availability and network configuration before relying on a particular allocation. ### Can I reinstall or change resources after deployment? The current configurator defines a proposed configuration. Confirm the procedure, potential downtime and data handling for an existing instance. Custom media and disk-encryption requirements also need operator review. ## Relevant guides - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. - [Size VPS CPU and memory from a real workload](https://swissoctet.com/insights/size-vps-cpu-and-memory/index.txt): Build a memory budget, inspect contention and separate one busy thread from work that can use several virtual cores. - [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/index.txt): Secure administration, expose only required services and establish updates and recovery without locking yourself out. - [Measure NVMe performance without misleading yourself](https://swissoctet.com/insights/nvme-benchmark-methodology/index.txt): Define the I/O pattern, control cache effects and inspect latency distributions before drawing an application conclusion from a disk test. - [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/index.txt): Compare application requirements, control and maintenance responsibilities rather than treating a VPS as the automatic next step for every website. - [Snapshots and backups: choose the failure you need to survive](https://swissoctet.com/insights/snapshots-backups-consistency/index.txt): Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection. - [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/index.txt): Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. - [A domain, DNS and TLS cutover runbook for a new server](https://swissoctet.com/insights/dns-tls-cutover-runbook/index.txt): Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections. - [Give your AI workers a bounded place to run](https://swissoctet.com/insights/give-ai-workers-a-bounded-runtime/index.txt): Separate model inference from orchestration, size the actual worker and limit what its tools can change before putting an AI workflow on a server. - [Separate your public web edge from the application](https://swissoctet.com/insights/separate-the-web-edge-from-the-app/index.txt): Give the web server, reverse proxy and application distinct responsibilities, with deliberate origin access, TLS, request limits and an incident path. --- # Vault Storage > Make room for the data behind your project. Vault separates a dedicated NVMe boot drive from configurable SAN storage, with CPU, memory and transfer allowances you can size independently. Canonical human page: https://swissoctet.com/services/vault/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. Room for media, archives and growing datasets. A storage-focused Linux configuration. ## Starting configuration Starting configuration: Vault Storage 01 (vault-01); USD 62.42 effective monthly base on the shortest available 1-month term; USD 62.42 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | CPU Cores | 2 | | RAM | 8GB | | SAN Disk Size [GiB] | 5000 GB (Upgradable) | | Bandwidth limit [TB] | 20TB | | IPv4 Addresses | 1 | | Boot Drive | 50GB NVME | ## Service capabilities ### Separate system and data storage The configuration lists an NVMe boot drive alongside SAN capacity, making the system volume distinct from the space intended for larger datasets. ### Capacity as a configuration choice Choose the SAN storage option that matches your data volume and expected growth. Read the units in the selector when calculating usable capacity. ### Processing resources for stored data Adjust CPU cores and memory for indexing, checksums, cataloguing or applications around the storage, rather than selecting capacity alone. ### Transfer and addresses under control Select a traffic allowance and IPv4 count suited to the workflow. Storage capacity and monthly data transfer are separate parts of the configuration. ## Example workloads ### Media and document libraries Keep larger collections behind an application that controls who can browse, upload or retrieve each item. ### Dataset repositories Provide a Swiss storage environment for project data, exports and research collections with a defined access policy. ### Backup destinations Use storage as one component of an independent backup strategy, with encryption, retention and restoration tests under your control. ## A closer look ### Plan for growth before filling the volume Count the data you already hold, the rate at which it grows and any temporary space needed for processing. Capacity options allow a larger data allocation, while the boot drive remains a separate specification. Filesystem overhead and your storage layout can change the space an application sees. ### Data movement belongs in the same calculation A large storage volume may be quiet most days or move substantial amounts of data. Initial uploads, regular backups and repeated downloads all affect traffic. Choose the bandwidth allowance alongside storage, then ensure your own connection and software can complete the workflow within the required time. ### Decide how the data should remain private You control the software and access model around the stored files. Encrypt sensitive archives before upload where appropriate, keep encryption keys separate, and restrict storage interfaces to authorised users. A storage environment can hold a backup, but the existence of a second folder does not by itself make the original data recoverable. ### Choose the storage interface as well as the capacity Vault lists SAN capacity, an NVMe boot drive and Linux template choices. Decide whether applications will read a local volume or use a file-sharing service such as NFS or SMB, then check operating-system support and protect the interface. Ceph, RBD, replication and failover describe possible storage architectures; the operator must confirm the actual backend and recovery scope before they become service commitments. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Vault Storage 01 A storage-oriented Linux configuration with a listed 5,000 GB SAN allocation and a separate 50 GB NVMe boot drive. Two CPU cores, 8 GB of memory and 20 TB of traffic support archive and file-storage projects. Configuration ID: vault-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 62.42. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 62.42; displayed effective monthly base: USD 62.42. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | CPU Cores | 2 | | RAM | 8GB | | SAN Disk Size [GiB] | 5000 GB (Upgradable) | | Bandwidth limit [TB] | 20TB | | IPv4 Addresses | 1 | | Boot Drive | 50GB NVME | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 62.42 | USD 62.42 | | 3 months | USD 62.42 | USD 187.27 | | 6 months | USD 62.42 | USD 374.54 | | 12 months | USD 62.42 | USD 749.08 | #### Plan-specific available choices ##### CPU allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | 2 CPU Cores | USD 0.00 | Yes | | 4 CPU Cores | USD 13.77 | No | | 6 CPU Cores | USD 18.36 | No | | 8 CPU Cores | USD 27.54 | No | | 10 CPU Cores | USD 36.72 | No | | 12 CPU Cores | USD 45.90 | No | | 14 CPU Cores | USD 55.08 | No | | 16 CPU Cores | USD 64.26 | No | | 18 CPU Cores | USD 73.44 | No | | 20 CPU Cores | USD 82.62 | No | | 22 CPU Cores | USD 91.80 | No | | 24 CPU Cores | USD 100.98 | No | | 26 CPU Cores | USD 110.16 | No | | 28 CPU Cores | USD 119.34 | No | | 30 CPU Cores | USD 128.52 | No | | 32 CPU Cores | USD 137.70 | No | ##### Memory [GB] | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | 8 GB RAM | USD 0.00 | Yes | | 16 GB RAM | USD 9.18 | No | | 24 GB RAM | USD 16.52 | No | | 32 GB RAM | USD 23.87 | No | | 40 GB RAM | USD 31.21 | No | | 48 GB RAM | USD 36.72 | No | | 64 GB RAM | USD 51.41 | No | | 128 GB RAM | USD 110.16 | No | | 256 GB RAM | USD 227.66 | No | ##### SAN Disk Size [GiB] | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | SAN Disk Size 5000 GiB | USD 0.00 | Yes | | SAN Disk Size 10000 GiB | USD 50.49 | No | | SAN Disk Size 15000 GiB | USD 100.98 | No | | SAN Disk Size 20000 GiB | USD 137.70 | No | | SAN Disk Size 25000 GiB | USD 183.60 | No | | SAN Disk Size 30000 GiB | USD 229.50 | No | | SAN Disk Size 35000 GiB | USD 275.40 | No | | SAN Disk Size 40000 GiB | USD 321.30 | No | | SAN Disk Size 45000 GiB | USD 367.20 | No | | SAN Disk Size 50000 GiB | USD 413.10 | No | | SAN Disk Size 55000 GiB | USD 459.00 | No | | SAN Disk Size 60000 GiB | USD 504.89 | No | | SAN Disk Size 65000 GiB | USD 550.79 | No | | SAN Disk Size 70000 GiB | USD 596.69 | No | | SAN Disk Size 75000 GiB | USD 642.59 | No | | 80,000 GiB SAN · variant A · operator quote | Operator quote required; not assumed free | No | | 80,000 GiB SAN · variant B · operator quote | Operator quote required; not assumed free | No | | SAN Disk Size 90000 GiB | USD 780.29 | No | | SAN Disk Size 95000 GiB | USD 826.19 | No | | SAN Disk Size 100000 GiB | USD 872.09 | No | ##### Bandwidth limit [TB] | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | 20TB | USD 0.00 | Yes | | 40TB | USD 27.54 | No | | 60TB | USD 41.31 | No | | 80TB | USD 55.08 | No | | 100TB | USD 73.44 | No | | 150TB | USD 119.34 | No | | 200TB | USD 165.24 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | 1 | USD 0.00 | Yes | | 2 | USD 3.67 | No | | 3 | USD 6.43 | No | | 4 | USD 8.26 | No | | 5 | USD 11.02 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Debian 11 (Stable) | USD 0.00 | Yes | | Ubuntu 20 (Stable) | USD 0.00 | No | | Ubuntu 21 (Stable) | USD 0.00 | No | | Ubuntu 22 (Stable) | USD 0.00 | No | ## Service questions ### What is the difference between the boot drive and SAN storage? The catalogue lists the NVMe boot drive separately from the SAN allocation. Plan the operating system and large data volume as distinct storage components. ### Why do some labels use GB and others GiB? The catalogue preserves the source units for each specification and option. Compare the actual selected capacity and confirm the allocation rather than treating different unit labels as interchangeable. ### Does more storage also include more traffic? No. SAN capacity and the bandwidth allowance have separate selectors. Check both in the configuration summary when preparing a data-heavy workflow. ### Is Vault automatically a backup service? Vault is a storage configuration. You still need backup software or a transfer process, retention rules, encryption where appropriate and a tested restoration procedure. ### Can I increase processing resources as well as capacity? Yes. The configurator includes CPU-core and memory choices in addition to SAN storage, traffic and IPv4 addresses. Select resources for the applications using the data. ### Can I provide NFS or SMB access to the stored files? A supported Linux setup can run a suitable file-sharing service. Verify package support, authentication and firewall rules, and restrict storage access to the intended users or private network. ### Is Ceph replication or RBD guaranteed for Vault? The current catalogue specifies SAN capacity, not a verified Ceph topology or RBD interface. Confirm backend technology, redundancy, failure handling and recovery responsibility with the operator. ### Can the allocation grow after the server is delivered? The catalogue lists capacity options for the initial request. Later resizing, filesystem changes and any downtime must be confirmed for the installed environment. ## Relevant guides - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. - [Swiss data residency: map the whole service](https://swissoctet.com/insights/swiss-data-residency-map/index.txt): A Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment. - [Turn RPO and RTO into a recovery budget you can test](https://swissoctet.com/insights/rpo-rto-recovery-budget/index.txt): Translate acceptable data loss and interruption into a timed recovery plan, with dependencies, restore capacity and a measurable exercise. - [Snapshots and backups: choose the failure you need to survive](https://swissoctet.com/insights/snapshots-backups-consistency/index.txt): Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection. - [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/index.txt): Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. - [Publish an onion service without overlooking the application](https://swissoctet.com/insights/publish-onion-service-safely/index.txt): Plan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model. - [Choose a hosting operating model before choosing a cloud](https://swissoctet.com/insights/choose-a-hosting-operating-model/index.txt): Compare shared hosting, a VPS, dedicated hardware and large cloud platforms through responsibility, recovery, dependencies and the complete operating budget. --- # Sentinel Kali > A separate Kali Linux environment for scoped security assessments, training and defensive research. Keep your tools in Switzerland and your testing within systems you own or have permission to assess. Canonical human page: https://swissoctet.com/services/sentinel-kali/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. A dedicated Kali Linux workspace for security testing on systems you are authorized to assess. ## Starting configuration Starting configuration: Sentinel Kali 04 (sentinel-kali-04); USD 12.85 effective monthly base on the shortest available 1-month term; USD 12.85 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 2 x Xeon 5600 | | RAM | 2GB DDR4 | | Storage | 30GB SSD | | Bandwidth | 100 Mbp/s 2TB | | DDoS Protection | Layer 3-4 | ## Service capabilities ### A separate assessment workspace Use a Kali environment away from your everyday computer. Organise project tools, notes and approved test data inside a dedicated KVM system. ### CLI or graphical workflow Select the GUI and VNC options when a desktop interface fits your work. Keep their access limited to the people who need it. ### Resources for the assessment Choose CPU, RAM and SSD capacity for the tools and datasets involved. Additional resources let you adapt the workspace to a defined project. ### Retention you decide Optional backup retention can support ongoing work. Consider what sensitive assessment material a backup contains before selecting how long to keep it. ## Example workloads ### Approved infrastructure assessments Prepare and perform tests against an agreed set of systems with a documented scope and permission from the owner. ### Security training environments Work with your own deliberately vulnerable labs and exercises without mixing them into your daily workspace. ### Defensive tool validation Evaluate approved security utilities, reproduce findings in a lab and prepare clear evidence for remediation. ## A closer look ### A useful lab starts with a clear scope List the authorised targets, permitted techniques, time window and people who can approve changes to the assessment. Sentinel Kali provides the environment; it does not grant permission to access a third-party system. Keep the workspace aligned with the agreed assessment and avoid unrelated traffic. ### Keep project material organised Assessment notes, logs and captured evidence may contain sensitive information. Use separate project directories, limit access and establish a retention period before work begins. If you select automatic backups, include those copies in the same data-handling plan rather than treating them as harmless duplicates. ### Choose the interface that suits the work A command-line environment keeps the setup focused for scripted tasks. A graphical session can suit tools that require a desktop, but it also needs memory and careful remote-access controls. Review the GUI, VNC, resource and network options together when configuring the workspace. ### Prepare the tools and the way into the lab Kali supplies a security-focused starting point, but a named distribution does not establish every package or version in a delivered image. Confirm the installed toolset and root credentials, plan SSH access, and review the separate GUI and VNC options if needed. The base plans list Layer 3–4 protection; later upgrades, console recovery and custom-image requests require operator confirmation. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Sentinel Kali 04 A compact Kali setup for command-line tools, introductory labs and focused authorized testing. Its base allocation is 2 vCPUs, 2 GB of DDR4 memory and 30 GB of SSD storage. Configuration ID: sentinel-kali-04. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 12.85. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 12.85; displayed effective monthly base: USD 12.85. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 2 x Xeon 5600 | | RAM | 2GB DDR4 | | Storage | 30GB SSD | | Bandwidth | 100 Mbp/s 2TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 12.85 | USD 12.85 | | 3 months | USD 12.47 | USD 37.40 | | 6 months | USD 12.08 | USD 72.48 | | 12 months | USD 11.31 | USD 135.72 | | 18 months | USD 10.54 | USD 189.69 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### Port speed upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | +100 MBP/S | USD 9.18 | No | | Upgrade to 1 Gbps | USD 55.08 | No | ##### Graphical desktop | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | NO-GUI | USD 0.00 | Yes | | GUI ENABLED | USD 0.92 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ### Sentinel Kali 01 A Kali Linux workspace for authorized assessment tools and security study. It combines 5 Xeon 5600 vCPUs, 2 GB of DDR4 memory and a 45 GB SSD with a 3 TB traffic allowance. Configuration ID: sentinel-kali-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 26.53. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 26.53; displayed effective monthly base: USD 26.53. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 5 x Xeon 5600 | | RAM | 2GB DDR4 | | Storage | 45GB SSD | | Bandwidth | 200 Mbp/s 3TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 26.53 | USD 26.53 | | 3 months | USD 25.73 | USD 77.20 | | 6 months | USD 24.94 | USD 149.63 | | 12 months | USD 23.35 | USD 280.16 | | 18 months | USD 21.75 | USD 391.58 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### Port speed upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | +100 MBP/S | USD 9.18 | No | | Upgrade to 1 Gbps | USD 55.08 | No | ##### Graphical desktop | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | NO-GUI | USD 0.00 | Yes | | GUI ENABLED | USD 0.92 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ### Sentinel Kali 02 Eight vCPUs and 4 GB of DDR4 memory provide room for a wider collection of Kali tools and research tasks. The configuration includes a 60 GB SSD and 5 TB of traffic. Configuration ID: sentinel-kali-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 38.46. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 38.46; displayed effective monthly base: USD 38.46. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 8 x Xeon 5600 | | RAM | 4GB DDR4 | | Storage | 60GB SSD | | Bandwidth | 200 Mbp/s 5TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 38.46 | USD 38.46 | | 3 months | USD 37.31 | USD 111.93 | | 6 months | USD 36.16 | USD 216.94 | | 12 months | USD 33.85 | USD 406.18 | | 18 months | USD 31.54 | USD 567.73 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### Port speed upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | +100 MBP/S | USD 9.18 | No | | Upgrade to 1 Gbps | USD 55.08 | No | ##### Graphical desktop | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | NO-GUI | USD 0.00 | Yes | | GUI ENABLED | USD 0.92 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ### Sentinel Kali 03 A larger Kali environment for authorized work that needs more processes and working files: 12 vCPUs, 8 GB of DDR4 memory, a 100 GB SSD and a 10 TB traffic allowance. Configuration ID: sentinel-kali-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 75.18. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 75.18; displayed effective monthly base: USD 75.18. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 12 x Xeon 5600 | | RAM | 8GB DDR4 | | Storage | 100GB SSD | | Bandwidth | 300 Mbp/s 10TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 75.18 | USD 75.18 | | 3 months | USD 72.93 | USD 218.78 | | 6 months | USD 70.67 | USD 424.03 | | 12 months | USD 66.16 | USD 793.94 | | 18 months | USD 61.65 | USD 1109.71 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### Port speed upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | +100 MBP/S | USD 9.18 | No | | Upgrade to 1 Gbps | USD 55.08 | No | ##### Graphical desktop | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | NO-GUI | USD 0.00 | Yes | | GUI ENABLED | USD 0.92 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ## Service questions ### Can I test systems belonging to another organisation? Only with explicit authorisation and an agreed scope. Purchasing a security environment does not authorise scanning, exploitation or access to third-party systems. ### Can I use a graphical desktop? The configurator includes GUI and VNC choices. Review both selections and allow enough memory for the desktop and tools you plan to run. ### Is this intended for offensive activity without permission? No. Sentinel is intended for authorised assessments, education and defensive research. Fraud, harmful attacks and unauthorised access are outside the service's intended use. ### Should I keep assessment evidence in automatic backups? Only when it fits the project's handling and retention rules. Evidence may contain confidential client data; include backup copies in your access and deletion plan. ### How does this differ from Sentinel Parrot? The starting security distribution differs. Compare the tools and workflow you need, then review the actual resources and available options for the selected family. ### Are all Kali tools already installed? Confirm the delivered image, package versions and tools required for the assessment. No fixed tool count or complete preinstalled suite is promised by the current catalogue. ### How do I connect and install my own utilities? Plan SSH for command-line work and confirm root credentials at delivery. GUI and VNC are separate configuration choices. Secure every entry point before installing or using assessment tools. ### What protection and upgrade choices are listed? Layer 3–4 protection is in the base plan. CPU, memory, disk and network additions are configurable, while a change to an existing workstation requires a confirmed procedure and availability. ### Can the workstation be used for forensic work? It can form part of an authorised analysis workflow. Preserve evidence separately, verify tool suitability and avoid altering original material; the server alone does not establish a forensic chain of custody. --- # Sentinel Parrot > A Parrot Security environment for careful research and authorised testing. Bring project tools, development work and lab evidence into a Swiss KVM workspace configured around your assessment. Canonical human page: https://swissoctet.com/services/sentinel-parrot/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. An isolated Parrot Security environment for research, development and authorized security work. ## Starting configuration Starting configuration: Sentinel Parrot 04 (sentinel-parrot-04); USD 12.85 effective monthly base on the shortest available 1-month term; USD 12.85 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 2 x Xeon 5600 | | RAM | 2GB DDR4 | | Storage | 30GB SSD | | Bandwidth | 100 Mbp/s 2TB | | DDoS Protection | Layer 3-4 | ## Service capabilities ### Parrot as your starting point Build the workspace around the Parrot Security environment, with your project utilities and a workflow appropriate to the systems you are authorised to assess. ### A choice of working interfaces GUI and VNC options let you select a desktop workflow where needed. Administration access remains something to configure and secure deliberately. ### A configurable research environment Compare the listed CPU, RAM and SSD resources. Add capacity based on the tools and material involved in the work, rather than the plan number. ### Network and backup options Review additional IPv4, port-speed and daily-backup choices. Keep data movement and evidence retention consistent with the approved project. ## Example workloads ### Defensive research projects Study your own application behaviour and evaluate security tools in a separate environment with controlled access. ### Authorised client work Maintain a project workspace for assessments whose targets, permissions and evidence-handling requirements are documented. ### Security development Prepare and test utilities against your own lab systems before using them in an approved assessment. ## A closer look ### Choose the environment your workflow expects Parrot and Kali are different starting points for security work. Choose the environment that suits your team's tooling, package requirements and habits. The name of a distribution is not a substitute for verifying that the applications and versions you require are present and maintained. ### Keep one project from leaking into the next Separate project files, remove expired access and clean up temporary material when an assessment ends. A research workspace may hold customer information, so use appropriate access restrictions and retention rules. These controls matter as much as the Swiss location of the server. ### Configure from the resource table The Parrot range contains different combinations of CPU, memory, disk and network capacity. Compare the actual table rather than assuming that a higher numbered plan always suits a larger workload. GUI, backup and network additions are separate choices that should be reviewed before confirming the configuration. ### Check the delivered workspace against your methodology Define the packages and versions needed for your research before choosing the environment. Confirm the Parrot image, root access and SSH credentials at delivery; a GUI and VNC are separate choices. The base specifications list Layer 3–4 protection. Console recovery, a custom image and changes to an existing workstation require operator confirmation, while project authorisation remains yours to establish. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Sentinel Parrot 04 A smaller Parrot Security configuration for learning, utilities and targeted authorized assessments. Two vCPUs, 2 GB of DDR4 memory and a 30 GB SSD keep the resource allocation focused. Configuration ID: sentinel-parrot-04. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 12.85. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 12.85; displayed effective monthly base: USD 12.85. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 2 x Xeon 5600 | | RAM | 2GB DDR4 | | Storage | 30GB SSD | | Bandwidth | 100 Mbp/s 2TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 12.85 | USD 12.85 | | 3 months | USD 12.47 | USD 37.40 | | 6 months | USD 12.08 | USD 72.48 | | 12 months | USD 11.31 | USD 135.72 | | 18 months | USD 10.54 | USD 189.69 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### Port speed upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | +100 MBP/S | USD 9.18 | No | | Upgrade to 1 Gbps | USD 50.49 | No | ##### Graphical desktop | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | NO-GUI | USD 0.00 | Yes | | GUI ENABLED | USD 0.92 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### Sentinel Parrot 01 A Parrot Security environment for authorized research and development, with 5 Xeon 5600 vCPUs, 2 GB of DDR4 memory and a 45 GB SSD. The traffic allowance is 3 TB. Configuration ID: sentinel-parrot-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 26.53. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 26.53; displayed effective monthly base: USD 26.53. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 5 x Xeon 5600 | | RAM | 2GB DDR4 | | Storage | 45GB SSD | | Bandwidth | 200 Mbp/s 3TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 26.53 | USD 26.53 | | 3 months | USD 25.73 | USD 77.20 | | 6 months | USD 24.94 | USD 149.63 | | 12 months | USD 23.35 | USD 280.16 | | 18 months | USD 21.75 | USD 391.58 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### Port speed upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | +100 MBP/S | USD 9.18 | No | | Upgrade to 1 Gbps | USD 50.49 | No | ##### Graphical desktop | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | NO-GUI | USD 0.00 | Yes | | GUI ENABLED | USD 0.92 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### Sentinel Parrot 02 A Parrot workspace with 8 vCPUs and 4 GB of DDR4 memory for maintaining several tools or development tasks. It includes 60 GB of SSD storage and 5 TB of traffic. Configuration ID: sentinel-parrot-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 38.46. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 38.46; displayed effective monthly base: USD 38.46. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 8 x Xeon 5600 | | RAM | 4GB DDR4 | | Storage | 60GB SSD | | Bandwidth | 200 Mbp/s 5TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 38.46 | USD 38.46 | | 3 months | USD 37.31 | USD 111.93 | | 6 months | USD 36.16 | USD 216.94 | | 12 months | USD 33.85 | USD 406.18 | | 18 months | USD 31.54 | USD 567.73 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### Port speed upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | +100 MBP/S | USD 9.18 | No | | Upgrade to 1 Gbps | USD 50.49 | No | ##### Graphical desktop | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | NO-GUI | USD 0.00 | Yes | | GUI ENABLED | USD 0.92 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ### Sentinel Parrot 03 The largest Parrot allocation offers 12 vCPUs, 8 GB of DDR4 memory and a 100 GB SSD for more substantial authorized research workloads, with a 300 Mbps port and 10 TB of traffic. Configuration ID: sentinel-parrot-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 75.18. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 75.18; displayed effective monthly base: USD 75.18. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Virtualization | KVM | | VCPU | 12 x Xeon 5600 | | RAM | 8GB DDR4 | | Storage | 100GB SSD | | Bandwidth | 300 Mbp/s 10TB | | DDoS Protection | Layer 3-4 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 75.18 | USD 75.18 | | 3 months | USD 72.93 | USD 218.78 | | 6 months | USD 70.67 | USD 424.03 | | 12 months | USD 66.16 | USD 793.94 | | 18 months | USD 61.65 | USD 1109.71 | Technical input requested for an order: Desired Hostname : (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional IPv4 addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional IP | USD 0.00 | Yes | | + 1 Ipv4 | USD 4.59 | No | | + 2 Ipv4 | USD 9.18 | No | | + 3 Ipv4 | USD 13.77 | No | | + 4 Ipv4 | USD 18.36 | No | | + 5 Ipv4 | USD 22.95 | No | ##### Additional storage | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional disk space | USD 0.00 | Yes | | + 5GB SSD | USD 2.75 | No | | + 10GB SSD | USD 5.51 | No | | + 20GB SSD | USD 9.18 | No | | + 50GB SSD | USD 18.36 | No | ##### Additional CPU cores | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Extra CPU Core | USD 0.00 | Yes | | 1 X Extra CPU Core | USD 4.59 | No | | 2 X Extra CPU Core | USD 9.18 | No | | 3 X Extra CPU Core | USD 13.77 | No | | 4 X Extra CPU Core | USD 18.36 | No | | 6 X Extra CPU Core | USD 27.54 | No | ##### Remote console | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No remote-console add-on | USD 0.00 | Yes | | VNC Activated | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backups | USD 0.00 | Yes | | Daily Backups (3 Days Retention) | USD 4.59 | No | | Daily Backups (6 Days Retention) | USD 13.77 | No | | Daily Backups (10 Days Retention) | USD 22.95 | No | ##### Additional memory | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | 1 X Extra GB Memory | USD 6.88 | No | | 2 X Extra GB Memory | USD 13.77 | No | | 3 X Extra GB Memory | USD 20.65 | No | | 4 X Extra GB Memory | USD 27.54 | No | ##### Port speed upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | +100 MBP/S | USD 9.18 | No | | Upgrade to 1 Gbps | USD 50.49 | No | ##### Graphical desktop | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | NO-GUI | USD 0.00 | Yes | | GUI ENABLED | USD 0.92 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Included baseline protection · no advanced upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ##### 1 Gbps Port speed | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No port speed upgrade | USD 0.00 | Yes | | 1 Gbps | USD 50.49 | No | ## Service questions ### Is Parrot the same environment as Kali? No. They are different distributions. Select based on the tools and workflow your project needs, and compare the listed resources independently. ### Are the plans ordered from smallest to largest? Use the CPU, memory, disk and traffic specifications to compare them. Plan names are identifiers and should not be treated as a resource ranking. ### Is a GUI enabled automatically? Check the selected GUI option in the configurator. A graphical interface is a distinct choice, and VNC has its own selection. ### What targets can I assess from the environment? Systems you own or targets for which you have explicit permission within an agreed scope. The server location does not change that requirement. ### How should I handle confidential research material? Restrict access, protect credentials and choose a defined retention period. Treat automatic backups and exported evidence as part of the same confidential project. ### Does the image contain every security and forensic utility? Confirm the delivered toolset against the requirements of your project. A distribution name does not guarantee every package, version or specialist application is installed. ### Can I manage the workspace over SSH? Plan a protected SSH administration path and confirm root credentials at delivery. GUI and VNC selections are separate from command-line access and need their own secure access rules. ### Is basic network protection listed? Yes. The base specifications list Layer 3–4 protection. The advanced paid selection is separate; it does not define the privacy of commands, evidence or application data. ### Can an existing Parrot configuration be expanded? CPU, RAM, disk and network options are visible in the catalogue. Confirm the actual upgrade procedure, stock and any interruption before changing a delivered workstation. --- # Tensor GPU > Give accelerated workloads their own physical environment in Switzerland. Tensor combines NVIDIA Tesla options with dedicated server resources for compatible inference, rendering and GPU processing workflows. Canonical human page: https://swissoctet.com/services/tensor/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. Dedicated GPU configurations for accelerated compute, rendering and machine-learning workloads. ## Starting configuration Starting configuration: Tensor GPU 01 (tensor-01); USD 323.82 effective monthly base on the shortest available 1-month term; USD 323.82 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Intel Dual Xeon E5-2680 V4 | | GPU | Nvidia Tesla P4 / T4 | | RAM | 64GB DDR4 | | STORAGE | 1TB SSD | | PORT SPEED | 1 Gbit/s | | BANDWIDTH | UNMETERED | | IP(s) | 5 | ## Service capabilities ### A physical GPU environment The Tensor range is listed as bare metal. Plan your operating system, drivers and application stack around the selected hardware rather than a generic virtual instance. ### Choose the accelerator deliberately The configurator distinguishes NVIDIA Tesla P4 and T4 options. Compare the listed GPU memory with the model or task you want to run. ### CPU, RAM and disk around the GPU A GPU workflow also needs host memory, data preparation and storage. Review the Xeon platform and select RAM or disk additions where useful. ### Network choices for your datasets Compare the port and traffic characteristics across Tensor configurations. Dataset imports and output distribution can be as important as the accelerator itself. ## Example workloads ### Compatible model inference Run inference workloads whose framework, precision and memory requirements match the selected NVIDIA accelerator. ### GPU-enabled rendering Prepare a rendering or visual-processing workflow after checking the engine's GPU and driver compatibility. ### Batch data processing Use an accelerator-aware application for repeatable image, media or numerical tasks on data you are entitled to process. ## A closer look ### GPU memory is a practical first filter Before selecting a server, check whether the application and its working data fit the chosen accelerator's memory. The model architecture, precision and batch size all affect this requirement. A larger host-RAM option does not automatically increase the GPU's own memory. ### The complete stack determines the result Choose an operating system supported by your software, then verify the NVIDIA driver and framework requirements. CPU preprocessing, storage reads and data transfer can limit a workflow even when the GPU is suitable. Benchmark a representative task before scheduling a large production job. ### Keep project data in your own operating environment Tensor gives you a Swiss location for an application stack you configure. Decide who may access datasets, models and results, and keep sensitive material out of public directories. Use licensed software and authorised datasets; no external AI service or data-processing claim is implied by the presence of a GPU. ### From a GPU specification to a usable software path Treat the selected accelerator, driver and application as one compatibility decision. CUDA-based work, TensorFlow or PyTorch, scientific processing and GPU rendering need a supported software combination. Video workflows may also use FFmpeg and hardware encoding, but supported codecs and practical throughput must be checked for the chosen P4 or T4. Confirm installation work and operator access before delivery. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Tensor GPU 01 Dedicated GPU hardware combining dual Xeon E5-2680 v4 processors, a listed Tesla P4 / T4 GPU configuration, 64 GB of DDR4 memory and a 1 TB SSD. The network specification is a 1 Gbps port with unmetered traffic. Configuration ID: tensor-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 380.97. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 323.82; displayed effective monthly base: USD 323.82. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Intel Dual Xeon E5-2680 V4 | | GPU | Nvidia Tesla P4 / T4 | | RAM | 64GB DDR4 | | STORAGE | 1TB SSD | | PORT SPEED | 1 Gbit/s | | BANDWIDTH | UNMETERED | | IP(s) | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 323.82 | USD 323.82 | | 3 months | USD 323.82 | USD 971.46 | | 6 months | USD 323.82 | USD 1942.93 | | 12 months | USD 323.82 | USD 3885.85 | | 18 months | USD 323.82 | USD 5828.78 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024 GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 2 TB SSD | USD 22.95 | No | | 4 TB SSD | USD 32.13 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 22.95 | No | | 4 TB SSD | USD 32.13 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 22.95 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | /28 (14 IPs) | USD 20.20 | No | | /27 (30 IPs) | USD 29.38 | No | | /26 (62 IPs) | USD 64.26 | No | | /25 (126 IPs) | USD 128.52 | No | | /24 (254 IPs) | USD 257.04 | No | ##### GPU upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Nvidia Tesla P4 8GB DDR5 | USD 0.00 | Yes | | Nvidia Tesla T4 16 GB GDDR6 | USD 119.34 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Debian 10.X Minimal stable (64 Bit) | USD 0.00 | Yes | | Debian 10.X Stable (64 Bit) | USD 0.00 | No | | Debian 9.X Minimal stable (64 Bit) | USD 0.00 | No | | Debian 9.X Stable (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Centos 7.X (64 Bit) | USD 0.00 | No | | Centos 6.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | ESXi 8.x (64 Bit) | USD 0.00 | No | | AlmaLinux 9.2 (64 Bit) | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Kali Linux 2023 (64 Bit) | USD 0.00 | No | | Proxmox 8.x Stable (64 Bit) | USD 0.00 | No | | Ubuntu 23.04 (64 Bit) | USD 0.00 | No | | Debian 12 Stable (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Custom OS | Operator quote required; not assumed free | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ### Tensor GPU 02 A GPU configuration with a 10 Gbps port for accelerated projects that also move larger datasets. The listed hardware includes dual Xeon E5-2680 v4 processors, Tesla P4 / T4 GPUs, 64 GB of DDR4 memory and a 1 TB SSD. Configuration ID: tensor-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 962.97. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 818.53; displayed effective monthly base: USD 818.53. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Intel Dual Xeon E5-2680 V4 | | GPU | Nvidia Tesla P4 / T4 | | RAM | 64GB DDR4 | | STORAGE | 1TB SSD | | PORT SPEED | 10 Gbit/s | | BANDWIDTH | UNMETERED | | IP(s) | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 818.53 | USD 818.53 | | 3 months | USD 818.53 | USD 2455.58 | | 6 months | USD 818.53 | USD 4911.15 | | 12 months | USD 818.53 | USD 9822.31 | | 18 months | USD 818.53 | USD 14733.46 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024 GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 2 TB SSD | USD 22.95 | No | | 4 TB SSD | USD 32.13 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 22.95 | No | | 4 TB SSD | USD 32.13 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 22.95 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | /28 (14 IPs) | USD 20.20 | No | | /27 (30 IPs) | USD 29.38 | No | | /26 (62 IPs) | USD 64.26 | No | | /25 (126 IPs) | USD 128.52 | No | | /24 (254 IPs) | USD 257.04 | No | ##### GPU upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Nvidia Tesla P4 8GB DDR5 | USD 0.00 | Yes | | Nvidia Tesla T4 16 GB GDDR6 | USD 119.34 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Debian 10.X Minimal stable (64 Bit) | USD 0.00 | Yes | | Debian 10.X Stable (64 Bit) | USD 0.00 | No | | Debian 9.X Minimal stable (64 Bit) | USD 0.00 | No | | Debian 9.X Stable (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Centos 7.X (64 Bit) | USD 0.00 | No | | Centos 6.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | ESXi 8.x (64 Bit) | USD 0.00 | No | | AlmaLinux 9.2 (64 Bit) | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Kali Linux 2023 (64 Bit) | USD 0.00 | No | | Proxmox 8.x Stable (64 Bit) | USD 0.00 | No | | Ubuntu 23.04 (64 Bit) | USD 0.00 | No | | Debian 12 Stable (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Custom OS | Operator quote required; not assumed free | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ### Tensor GPU 03 Dual Xeon Gold 6134 processors accompany the listed Tesla P4 / T4 GPU configuration for dedicated accelerated compute. This plan includes 64 GB of DDR4 memory, a 1 TB SSD and a 1 Gbps port with unmetered traffic. Configuration ID: tensor-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 1101.59. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 936.35; displayed effective monthly base: USD 936.35. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Intel Dual Xeon Gold 6134 | | GPU | Nvidia Tesla P4 / T4 | | RAM | 64GB DDR4 | | STORAGE | 1TB SSD | | PORT SPEED | 1 Gbit/s | | BANDWIDTH | UNMETERED | | IP(s) | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 936.35 | USD 936.35 | | 3 months | USD 936.35 | USD 2809.05 | | 6 months | USD 936.35 | USD 5618.10 | | 12 months | USD 936.35 | USD 11236.20 | | 18 months | USD 936.35 | USD 16854.30 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024 GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 2 TB SSD | USD 22.95 | No | | 4 TB SSD | USD 32.13 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 22.95 | No | | 4 TB SSD | USD 32.13 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 22.95 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | /28 (14 IPs) | USD 20.20 | No | | /27 (30 IPs) | USD 29.38 | No | | /26 (62 IPs) | USD 64.26 | No | | /25 (126 IPs) | USD 128.52 | No | | /24 (254 IPs) | USD 257.04 | No | ##### GPU upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Nvidia Tesla P4 8GB DDR5 | USD 0.00 | Yes | | Nvidia Tesla T4 16 GB GDDR6 | USD 119.34 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Debian 10.X Minimal stable (64 Bit) | USD 0.00 | Yes | | Debian 10.X Stable (64 Bit) | USD 0.00 | No | | Debian 9.X Minimal stable (64 Bit) | USD 0.00 | No | | Debian 9.X Stable (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Centos 7.X (64 Bit) | USD 0.00 | No | | Centos 6.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | ESXi 8.x (64 Bit) | USD 0.00 | No | | AlmaLinux 9.2 (64 Bit) | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Kali Linux 2023 (64 Bit) | USD 0.00 | No | | Proxmox 8.x Stable (64 Bit) | USD 0.00 | No | | Ubuntu 23.04 (64 Bit) | USD 0.00 | No | | Debian 12 Stable (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Custom OS | Operator quote required; not assumed free | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ## Service questions ### Which GPU should I choose? Compare the P4 and T4 options with your software's support list and memory needs. The selected option, rather than the family headline, defines the accelerator configuration. ### Does more system RAM increase GPU memory? No. System RAM and the GPU's own memory are different resources. Review the accelerator option and host-memory option separately. ### Is a machine-learning framework preconfigured? The catalogue lists operating-system and software choices. Confirm any required framework, driver and installation work as part of your deployment plan. ### Can every rendering application use this GPU? Check the application's supported accelerator, driver and operating-system requirements. A GPU listed in a server specification does not establish compatibility with every engine. ### How should I choose between the server variants? Compare the CPU platform and network port as well as the GPU selection. A workload with large data transfers may need a different balance from a compute-heavy local batch. ### Are A100, H100, RTX or multiple GPUs part of this range? The published Tensor choices list Tesla P4 and T4. Other accelerators or several GPUs are not included catalogue selections and would require a separately validated configuration. ### Can Tensor run CUDA, TensorFlow or PyTorch? Check the chosen GPU, driver, toolkit and framework versions together. Installation and a working test job need confirmation; listing an NVIDIA accelerator does not make a framework preconfigured. ### Can I use it for video encoding or streaming? Evaluate FFmpeg, hardware-encoding support and the codecs required by your workflow. HLS, DASH, WebRTC or RTMP support depends on the software you deploy, and no stream count or latency is promised. ### What comes with the network and operating environment? The plan lists its port, unmetered traffic and five IPs. Confirm root or administrator access, recovery controls and baseline protection with the operator; additional IP and software options are separate. ## Relevant guides - [Build a GPU VRAM budget before choosing hardware](https://swissoctet.com/insights/gpu-vram-budget-for-real-workloads/index.txt): Account for weights, activations, caches and temporary buffers, then test the peak workload rather than the model file alone. - [Give your AI workers a bounded place to run](https://swissoctet.com/insights/give-ai-workers-a-bounded-runtime/index.txt): Separate model inference from orchestration, size the actual worker and limit what its tools can change before putting an AI workflow on a server. --- # Canvas Web > A Swiss home for websites and publishing projects. Canvas brings cPanel, SSD capacity and clearly listed domain allowances together for hosting that stays focused on the site you want to run. Canonical human page: https://swissoctet.com/services/canvas/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. A clean foundation for websites and publishing. Pick your storage, domains and hosting options. ## Starting configuration Starting configuration: Canvas Web 01 (canvas-01); USD 12.85 effective monthly base on the shortest available 1-month term; USD 12.85 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | System | Cpanel | | Domains | 1 | | Subdomains | 5 | | Storage | 50GB SSD | | Bandwidth | Unlimited | ## Service capabilities ### A hosting panel at the centre The Canvas plans list cPanel as the hosting environment, giving you a panel-based starting point instead of a complete server to administer. ### Domain allowances you can compare Check the number of domains and subdomains in each plan. Add a domain option when the project needs another hosted site. ### SSD space for your sites Select storage for site files, uploads and ongoing growth. The listed capacity is a clearer starting point than a promise that every resource is unlimited. ### Address and protection options A dedicated IPv4 and additional DDoS option appear separately in the configurator. Review them against your site's requirements before selecting. ## Example workloads ### Publishing and editorial sites Provide a panel-based home for a blog, publication or project site after checking its application requirements. ### Small business websites Host a company or professional site with room for its content, uploads and chosen domain structure. ### A collection of projects Choose a larger domain allowance for several compatible websites without moving directly to full server administration. ## A closer look ### Focus on the website and its requirements A web-hosting plan is a different starting point from a VPS. You choose the storage and domain allowance for the site, then verify the runtime and application requirements it needs. Canvas fits projects that prefer a hosting panel to configuring an entire operating system. ### Plan your domain structure clearly A second site and a subdomain of an existing site may use different allowances. Compare the domains and subdomains in the plan table, then review any extra-domain option. Hosting a domain is also separate from registering it; make sure you control the domain and can update its DNS. ### Privacy belongs in the website as well Swiss offshore hosting and a no-KYC order flow do not decide what your own website collects. Keep forms proportionate, protect administrative accounts and avoid placing credentials or configuration secrets in public files. Check backups and a migration plan before moving an existing site. ### Check the website services behind the panel cPanel is listed for managing the hosting account. A site's PHP version, database support, CMS installer, email service and HTTPS setup should be confirmed against the delivered environment. Domain registration remains separate from hosted-domain capacity. Keep external copies of files and databases, and agree migration and restoration responsibilities before moving a working website. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Canvas Web 01 A cPanel hosting allocation for one domain and up to five subdomains. Its 50 GB of SSD storage gives a single website room for pages, media and publishing files. Configuration ID: canvas-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 12.85. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 12.85; displayed effective monthly base: USD 12.85. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | System | Cpanel | | Domains | 1 | | Subdomains | 5 | | Storage | 50GB SSD | | Bandwidth | Unlimited | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 12.85 | USD 12.85 | | 2 months | USD 11.31 | USD 22.62 | | 3 months | USD 10.92 | USD 32.77 | | 6 months | USD 10.28 | USD 61.69 | | 12 months | USD 9.64 | USD 115.67 | Technical input requested for an order: Main Domain (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional domains | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional domain | USD 0.00 | Yes | | + 1 additional domain | USD 3.67 | No | | + 2 additional domain | USD 7.34 | No | | + 5 additional domain | USD 18.36 | No | ##### Dedicated IPv4 address | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Dedicated IPV4 Address | USD 0.00 | Yes | | 1 Dedicated IPV4 Address | USD 4.59 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No advanced DDoS upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ### Canvas Web 02 Host two domains within one cPanel configuration, with up to ten subdomains and 80 GB of SSD storage. A practical option for a main site and a separate project. Configuration ID: canvas-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 22.03. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 22.03; displayed effective monthly base: USD 22.03. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | System | Cpanel | | Domains | 2 | | Subdomains | 10 | | Storage | 80GB SSD | | Bandwidth | Unlimited | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 22.03 | USD 22.03 | | 2 months | USD 19.39 | USD 38.78 | | 3 months | USD 18.73 | USD 56.18 | | 6 months | USD 17.63 | USD 105.75 | | 12 months | USD 16.52 | USD 198.29 | Technical input requested for an order: Main Domain (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional domains | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional domain | USD 0.00 | Yes | | + 1 additional domain | USD 3.67 | No | | + 2 additional domain | USD 7.34 | No | | + 5 additional domain | USD 18.36 | No | ##### Dedicated IPv4 address | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Dedicated IPV4 Address | USD 0.00 | Yes | | 1 Dedicated IPV4 Address | USD 4.59 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No advanced DDoS upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ### Canvas Web 03 A cPanel configuration for up to four domains and fifteen subdomains, with 150 GB of SSD storage for a small collection of websites and their media libraries. Configuration ID: canvas-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 31.21. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 31.21; displayed effective monthly base: USD 31.21. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | System | Cpanel | | Domains | 4 | | Subdomains | 15 | | Storage | 150GB SSD | | Bandwidth | Unlimited | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 31.21 | USD 31.21 | | 2 months | USD 27.47 | USD 54.93 | | 3 months | USD 26.53 | USD 79.59 | | 6 months | USD 24.97 | USD 149.82 | | 12 months | USD 23.41 | USD 280.91 | Technical input requested for an order: Main Domain (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional domains | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional domain | USD 0.00 | Yes | | + 1 additional domain | USD 3.67 | No | | + 2 additional domain | USD 7.34 | No | | + 5 additional domain | USD 18.36 | No | ##### Dedicated IPv4 address | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Dedicated IPV4 Address | USD 0.00 | Yes | | 1 Dedicated IPV4 Address | USD 4.59 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No advanced DDoS upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ### Canvas Web 04 The broadest Canvas allocation supports eight domains, an unrestricted listed subdomain count and 500 GB of SSD storage for a larger portfolio of publishing projects. Configuration ID: canvas-04. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 44.98. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 44.98; displayed effective monthly base: USD 44.98. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | System | Cpanel | | Domains | 8 | | Subdomains | Unlimited | | Storage | 500GB SSD | | Bandwidth | Unlimited | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 44.98 | USD 44.98 | | 2 months | USD 39.59 | USD 79.17 | | 3 months | USD 38.23 | USD 114.70 | | 6 months | USD 35.99 | USD 215.91 | | 12 months | USD 33.74 | USD 404.83 | Technical input requested for an order: Main Domain (Required). You may add a technical label while preparing your configuration before ordering; never enter a password or identity information. #### Plan-specific available choices ##### Additional domains | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional domain | USD 0.00 | Yes | | + 1 additional domain | USD 3.67 | No | | + 2 additional domain | USD 7.34 | No | | + 5 additional domain | USD 18.36 | No | ##### Dedicated IPv4 address | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No Dedicated IPV4 Address | USD 0.00 | Yes | | 1 Dedicated IPV4 Address | USD 4.59 | No | ##### DDoS Protection | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No advanced DDoS upgrade | USD 0.00 | Yes | | Advanced DDoS protection · 3 Tbps | USD 22.95 | No | ## Service questions ### Does the plan include domain registration? The catalogue lists hosted-domain allowances. It does not list a domain-registration service; ensure you own the domain and can manage its DNS. ### Can I host more than one website? Choose a plan with the required domain allowance or review an additional-domain option. Verify that each site's application requirements fit the hosting environment. ### Do I need a dedicated IPv4 address? That depends on your application and deployment requirements. It is an optional selection in Canvas, not a requirement simply because you host a website. ### Can I install any server software I want? Canvas is a cPanel web-hosting range. If your application requires control of the whole operating system or a custom server stack, compare the VPS families. ### Does unlimited bandwidth mean unlimited server resources? No. The plans list storage and domain allowances separately. Traffic wording does not establish unlimited CPU, memory, files or application capacity. ### Can I deploy WordPress or another PHP CMS? Confirm the available PHP versions, extensions, database engine and installer tools against the application's requirements. cPanel in the plan table does not establish every runtime or one-click installation. ### Are email accounts and bulk sending included? Mailbox support, storage and sending limits require operator confirmation. Plan delivery requirements separately, especially for application mail or campaigns; a web-hosting plan does not establish unlimited SMTP use. ### How are HTTPS certificates provided? Confirm certificate issuance, renewal and DNS requirements before deployment. Agree the certificate workflow and responsibilities for the selected hosting configuration. ### What should I check about backups and isolation? Confirm account separation, backup coverage, retention and restoration access. Maintain independent copies of critical files and databases; panel access is not a recovery guarantee. ### Is baseline DDoS protection or log anonymisation promised? The advanced protection selection is optional. Baseline network protection and access-log handling need a documented operator policy; the current Canvas table does not establish those guarantees. ## Relevant guides - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/index.txt): Compare application requirements, control and maintenance responsibilities rather than treating a VPS as the automatic next step for every website. - [A domain, DNS and TLS cutover runbook for a new server](https://swissoctet.com/insights/dns-tls-cutover-runbook/index.txt): Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections. - [Choose the asset and network before preparing a crypto payment](https://swissoctet.com/insights/choose-crypto-asset-network/index.txt): Read a payment route as a complete asset-and-network pair, then verify invoice instructions, token identity and the amount delivered before authorising a transfer. - [Choose a hosting operating model before choosing a cloud](https://swissoctet.com/insights/choose-a-hosting-operating-model/index.txt): Compare shared hosting, a VPS, dedicated hardware and large cloud platforms through responsibility, recovery, dependencies and the complete operating budget. - [Plan addresses and DNS as parts of your deployment](https://swissoctet.com/insights/plan-addresses-and-dns-for-deployment/index.txt): Separate public, private, static and dedicated addresses, then map forward DNS, reverse DNS and TLS to the parties that can configure them. - [Separate your public web edge from the application](https://swissoctet.com/insights/separate-the-web-edge-from-the-app/index.txt): Give the web server, reverse proxy and application distinct responsibilities, with deliberate origin access, TLS, request limits and an incident path. --- # Veil Onion > Publish an onion service from a Swiss hosting environment. Veil pairs listed CPU, memory and SSD resources with stack choices, onion-address allowances and optional backup retention for legitimate private publishing. Canonical human page: https://swissoctet.com/services/veil/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. A hosting configuration built around onion services, with capacity adapted to your project. ## Starting configuration Starting configuration: Veil Onion 01 (veil-01); USD 27.54 effective monthly base on the shortest available 1-month term; USD 27.54 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | Onion Address | 1 | | CPU Cores | 2 | | RAM | 2GB | | Storage | 30GB SSD | | Traffic | Unlimited | | Databases | Unlimited | ## Service capabilities ### Onion services as the destination Compare the onion-address allowance in each plan and select additional generated addresses if your project needs separate services. ### Choose the application stack The configurator includes Nginx, Apache and Node.js stack choices. Select the environment that matches your site's software and deployment method. ### Resources behind the service CPU, RAM and SSD capacity remain visible in the plan table. Onion routing does not remove the need to size the application and its data. ### A deliberate retention choice Daily backup options have distinct retention periods. Consider site data, database contents and service-key handling as part of your recovery plan. ## Example workloads ### Privacy-minded publications Offer an onion access point for a lawful publication whose readers benefit from an alternative connection path. ### Project and community sites Run a legitimate community or research site with an application stack appropriate to its audience and data. ### Alternative service access Prepare an onion version of your own service while keeping application security and publishing controls consistent. ## A closer look ### Choose the stack before the plan size An application expecting a PHP web stack has different requirements from a Node.js service. Review the stack selector, then compare the CPU, memory and storage needed for the application and its databases. The number of onion addresses is a separate allowance, not a measure of application performance. ### Private access still needs secure publishing Review what the application reveals through pages, uploads, error messages and embedded resources. Protect administrator access and avoid exposing configuration files or credentials. Onion hosting provides a connection method; it does not establish that an application is secure or that an operator is anonymous. ### Keep a recovery plan for the whole service Your content, database and onion-service identity may all matter when restoring a site. Define what must be backed up and who can access the copies before relying on a retention option. Veil is intended for lawful publishing and private services; fraud, abuse and harmful content remain outside its intended use. ### Design a Tor-only publishing path deliberately Plan access through the onion address and avoid exposing the application through an unintended public interface. Check embedded resources, callbacks and outgoing connections that could reveal infrastructure details. Panel choice, PHP support, mail access and service-key handover need operator confirmation. A separate public website can share content through a planned publishing process without assuming Veil supplies a clearnet endpoint. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Veil Onion 01 A focused onion-service configuration for one address, with 2 CPU cores, 2 GB of memory and a 30 GB SSD. Traffic and database counts are listed as unlimited. Configuration ID: veil-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 27.54. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 27.54; displayed effective monthly base: USD 27.54. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Onion Address | 1 | | CPU Cores | 2 | | RAM | 2GB | | Storage | 30GB SSD | | Traffic | Unlimited | | Databases | Unlimited | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 27.54 | USD 27.54 | | 3 months | USD 24.79 | USD 74.36 | | 6 months | USD 22.03 | USD 132.19 | #### Plan-specific available choices ##### Application stack | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | LEMP · NGINX | USD 0.00 | Yes | | LAMP · Apache | USD 0.00 | No | | Node.js stack | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backup | USD 0.00 | Yes | | Daily Backup (3days holding) | USD 8.26 | No | | Daily Backup (6 days holding) | USD 22.95 | No | | Daily Backup (10 days holding) | USD 32.13 | No | ##### Additional onion addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No extra domain | USD 0.00 | Yes | | 1 Extra Domain | USD 4.59 | No | | 2 Extra Domains | USD 9.18 | No | | 3 Extra Domains | USD 13.77 | No | | 4 Extra Domains | USD 18.36 | No | | 5 Extra Domains | USD 20.65 | No | ### Veil Onion 02 Allocate up to three onion addresses with 4 CPU cores, 4 GB of memory and a 60 GB SSD. This configuration adds capacity for separate services or a growing onion project. Configuration ID: veil-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 55.08. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 55.08; displayed effective monthly base: USD 55.08. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Onion Address | 3 | | CPU Cores | 4 | | RAM | 4GB | | Storage | 60GB SSD | | Traffic | Unlimited | | Databases | Unlimited | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 55.08 | USD 55.08 | | 3 months | USD 49.57 | USD 148.71 | | 6 months | USD 44.06 | USD 264.38 | #### Plan-specific available choices ##### Application stack | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | LEMP · NGINX | USD 0.00 | Yes | | LAMP · Apache | USD 0.00 | No | | Node.js stack | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backup | USD 0.00 | Yes | | Daily Backup (3days holding) | USD 8.26 | No | | Daily Backup (6 days holding) | USD 22.95 | No | | Daily Backup (10 days holding) | USD 32.13 | No | ##### Additional onion addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No extra domain | USD 0.00 | Yes | | 1 Extra Domain | USD 4.59 | No | | 2 Extra Domains | USD 9.18 | No | | 3 Extra Domains | USD 13.77 | No | | 4 Extra Domains | USD 18.36 | No | | 5 Extra Domains | USD 20.65 | No | ### Veil Onion 03 A larger onion-hosting allocation for up to five addresses. Four CPU cores, 6 GB of memory and 100 GB of SSD storage provide more room for content and service data. Configuration ID: veil-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 73.44. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 73.44; displayed effective monthly base: USD 73.44. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Onion Address | 5 | | CPU Cores | 4 | | RAM | 6GB | | Storage | 100GB SSD | | Traffic | Unlimited | | Databases | Unlimited | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 73.44 | USD 73.44 | | 3 months | USD 66.10 | USD 198.29 | | 6 months | USD 58.75 | USD 352.51 | #### Plan-specific available choices ##### Application stack | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | LEMP · NGINX | USD 0.00 | Yes | | LAMP · Apache | USD 0.00 | No | | Node.js stack | USD 0.00 | No | ##### Backup retention | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No backup | USD 0.00 | Yes | | Daily Backup (3days holding) | USD 8.26 | No | | Daily Backup (6 days holding) | USD 22.95 | No | | Daily Backup (10 days holding) | USD 32.13 | No | ##### Additional onion addresses | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No extra domain | USD 0.00 | Yes | | 1 Extra Domain | USD 4.59 | No | | 2 Extra Domains | USD 9.18 | No | | 3 Extra Domains | USD 13.77 | No | | 4 Extra Domains | USD 18.36 | No | | 5 Extra Domains | USD 20.65 | No | ## Service questions ### How do visitors access an onion address? Visitors need software capable of connecting to onion services. Provide clear access instructions for your audience and test your service through a compatible connection. ### Can I choose Apache, Nginx or Node.js? The stack selector lists those environment choices for Veil. Match the selection to the application's requirements rather than choosing on the stack name alone. ### Does onion hosting guarantee anonymity? No. Application behaviour, access practices, payments and data handling can expose information. The connection method is one part of the privacy design. ### Are additional onion addresses included automatically? Each plan lists its address allowance. Additional generated addresses are an optional configuration choice and appear separately in the summary. ### Does unlimited traffic remove every usage limit? No. CPU, memory and storage remain defined resources, and acceptable-use requirements still apply. Traffic wording does not make every application or activity suitable. ### Can ordinary browsers reach the same Veil endpoint? Plan Veil as onion publishing and use a Tor-capable client. Any clearnet counterpart requires a separate reviewed deployment; the onion-address allowance does not include a public-domain endpoint. ### Which management panel and mail tools are included? The catalogue defines application-stack choices, not a verified aaPanel installation or mail service. Confirm panel access, PHP features, database administration and any Tor-accessible mail workflow before delivery. ### What should I expect for performance and HTTPS? Tor routing affects latency, so test the application with its intended audience. Review HTTPS and authentication for your design; no streaming rate or protection from every denial-of-service attack is guaranteed. ### How do I migrate and preserve an onion identity? Plan files, database exports, stack compatibility and service-key custody together. Confirm how keys are delivered and restored, and what a selected backup option covers before replacing an existing service. ## Relevant guides - [Crypto checkout and the limits of payment privacy](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/index.txt): Understand the asset, network and confirmation journey, and protect the information that connects your project to a payment. - [No KYC and privacy: understand the difference](https://swissoctet.com/insights/no-kyc-is-not-anonymity/index.txt): Document-free onboarding addresses one collection point. Understand the other records, access paths and payment traces around a hosted project. - [Publish an onion service without overlooking the application](https://swissoctet.com/insights/publish-onion-service-safely/index.txt): Plan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model. - [From detected transaction to reconciled order: confirmations and reorgs](https://swissoctet.com/insights/confirmations-reorgs-order-reconciliation/index.txt): Design payment states around verified chain evidence, explicit acceptance rules and unambiguous order association rather than a browser claim that funds were sent. --- # Metal Origin > An accessible starting point for your own physical server. Metal Origin offers a dual-Xeon foundation in Switzerland, with memory, disk and network choices for established workloads and practical deployments. Canonical human page: https://swissoctet.com/services/metal-origin/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. A practical entry to dedicated hardware. Your workload, on its own physical machine. ## Starting configuration Starting configuration: Metal Origin 01 (metal-origin-01); USD 146.88 effective monthly base on the shortest available 3-month term; USD 440.64 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon X5670 | | RAM | 96 GB DDR3 | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 1 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | | MIN RENT | 3 MONTHS | ## Service capabilities ### A physical machine for the workload The range is listed as bare metal, separating your server choice from a virtual instance. Build the system around the listed dual-Xeon platform. ### Capacity for useful server roles Compare the base memory and SATA SSD storage, then choose supported RAM or additional-drive options for the services you intend to run. ### Choose the traffic model The Origin variants list different port-speed and traffic combinations. A metered allocation and an unmetered configuration are separate choices. ### An explicit rental commitment The catalogue lists a minimum rental period for Origin. Review that commitment alongside optional software, IP space and the chosen billing term. ## Example workloads ### Established application stacks Bring several compatible application components onto a physical environment with a clearly sized memory and disk allocation. ### File and archive services Use supported drive additions for a storage-oriented deployment, with access controls and an independent recovery strategy. ### Migration from a virtual server Compare dedicated resources when a project needs its own physical foundation and can accommodate the rental term. ## A closer look ### Dedicated hardware, chosen for a concrete job Origin is a practical physical-server option when the workload fits the listed processor generation. Compare application compatibility and resource needs before selecting; newer server families may suit a different workload. Owning the software environment also means planning updates, access, monitoring and recovery. ### Use the drive options to shape the server The configurator separates primary storage from additional drives, with SSD and HDD choices where listed. Choose according to active data, archive capacity and the layout you intend to build. Several drives do not automatically create a RAID array or an independent backup. ### Choose the term as carefully as the resources The minimum rental is part of the Origin specification and should be included in your project budget. Review the network variant, optional licences and IP allocation before confirming a term. Keep an existing environment available until a migrated application has been tested on the new server. ### Prepare the administration and recovery boundary Origin lists bare-metal hardware and five IPs in a /29 allocation. Confirm root or administrator access, the remote-console method and any IPv6 allocation before delivery. Disk count, NVMe compatibility and network protection need review for the chosen hardware. The listed port describes the configuration; any dedicated-throughput commitment requires explicit operating terms. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Metal Origin 01 Dedicated dual Xeon X5670 hardware with 96 GB of DDR3 memory and a 1 TB SATA3 SSD. The network allocation pairs a 1 Gbps port with unmetered traffic; the listed minimum rental term is three months. Configuration ID: metal-origin-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 146.88. This rate is not a separate payable invoice total. Shortest available billing term: 3 months. Base charge for this term: USD 440.64; displayed effective monthly base: USD 146.88. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon X5670 | | RAM | 96 GB DDR3 | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 1 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | | MIN RENT | 3 MONTHS | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 3 months | USD 146.88 | USD 440.64 | | 6 months | USD 146.88 | USD 881.27 | | 12 months | USD 146.88 | USD 1762.54 | | 18 months | USD 146.88 | USD 2643.81 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 192 GB DDR3 | USD 118.42 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | | Upgrade to 4 TB HDD | USD 27.54 | No | | Upgrade to 8 TB HDD | USD 41.31 | No | | Upgrade to 10 TB HDD | USD 55.08 | No | | Upgrade to 16 TB HDD | USD 55.08 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 27.54 | No | | Add 8 TB HDD | USD 41.31 | No | | Add 10 TB HDD | USD 55.08 | No | | Add 16 TB HDD | USD 73.44 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 22.95 | No | | Add 2 TB SSD | USD 27.54 | No | | Add 4 TB SSD | USD 36.72 | No | | Add 4 TB HDD | USD 32.13 | No | | Add 8 TB HDD | USD 45.90 | No | | Add 10 TB HDD | USD 55.08 | No | | Add 16 TB HDD | USD 73.44 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 143.21 | No | | Upgrade to /24 (254 IPs) | USD 286.41 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Almalinux 8 | USD 0.00 | Yes | | Debian 11 | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows Server 2022 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2019 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2016 (Trial) | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Arch Linux Latest | USD 0.00 | No | ### Metal Origin 02 A dedicated configuration for projects that need a 10 Gbps port within a 100 TB traffic allowance. It retains dual Xeon X5670 processors, 96 GB of DDR3 memory and a 1 TB SATA3 SSD, with a listed three-month minimum term. Configuration ID: metal-origin-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 183.60. This rate is not a separate payable invoice total. Shortest available billing term: 3 months. Base charge for this term: USD 550.79; displayed effective monthly base: USD 183.60. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon X5670 | | RAM | 96 GB DDR3 | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 10 Gbps | | BANDWIDTH | 100TB | | IPS | 5 IP /29 | | MIN RENT | 3 MONTHS | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 3 months | USD 183.60 | USD 550.79 | | 6 months | USD 183.60 | USD 1101.59 | | 12 months | USD 183.60 | USD 2203.18 | | 18 months | USD 183.60 | USD 3304.76 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 192 GB DDR3 | USD 118.42 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | | Upgrade to 4 TB HDD | USD 27.54 | No | | Upgrade to 8 TB HDD | USD 41.31 | No | | Upgrade to 10 TB HDD | USD 55.08 | No | | Upgrade to 16 TB HDD | USD 55.08 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 27.54 | No | | Add 8 TB HDD | USD 41.31 | No | | Add 10 TB HDD | USD 55.08 | No | | Add 16 TB HDD | USD 73.44 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 22.95 | No | | Add 2 TB SSD | USD 27.54 | No | | Add 4 TB SSD | USD 36.72 | No | | Add 4 TB HDD | USD 32.13 | No | | Add 8 TB HDD | USD 45.90 | No | | Add 10 TB HDD | USD 55.08 | No | | Add 16 TB HDD | USD 73.44 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 143.21 | No | | Upgrade to /24 (254 IPs) | USD 286.41 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Almalinux 8 | USD 0.00 | Yes | | Debian 11 | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows Server 2022 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2019 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2016 (Trial) | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Arch Linux Latest | USD 0.00 | No | ### Metal Origin 03 Combine a 10 Gbps port and unmetered traffic with dual Xeon X5670 processors, 96 GB of DDR3 memory and a 1 TB SATA3 SSD. The catalogue lists a minimum rental term of three months. Configuration ID: metal-origin-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 724.29. This rate is not a separate payable invoice total. Shortest available billing term: 3 months. Base charge for this term: USD 2172.88; displayed effective monthly base: USD 724.29. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon X5670 | | RAM | 96 GB DDR3 | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 10 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | | MIN RENT | 3 MONTHS | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 3 months | USD 724.29 | USD 2172.88 | | 6 months | USD 724.29 | USD 4345.76 | | 12 months | USD 724.29 | USD 8691.53 | | 18 months | USD 724.29 | USD 13037.29 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 192 GB DDR3 | USD 118.42 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | | Upgrade to 4 TB HDD | USD 27.54 | No | | Upgrade to 8 TB HDD | USD 41.31 | No | | Upgrade to 10 TB HDD | USD 55.08 | No | | Upgrade to 16 TB HDD | USD 55.08 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 27.54 | No | | Add 8 TB HDD | USD 41.31 | No | | Add 10 TB HDD | USD 55.08 | No | | Add 16 TB HDD | USD 73.44 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 22.95 | No | | Add 2 TB SSD | USD 27.54 | No | | Add 4 TB SSD | USD 36.72 | No | | Add 4 TB HDD | USD 32.13 | No | | Add 8 TB HDD | USD 45.90 | No | | Add 10 TB HDD | USD 55.08 | No | | Add 16 TB HDD | USD 73.44 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 143.21 | No | | Upgrade to /24 (254 IPs) | USD 286.41 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Almalinux 8 | USD 0.00 | Yes | | Debian 11 | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows Server 2022 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2019 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2016 (Trial) | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Arch Linux Latest | USD 0.00 | No | ## Service questions ### What does the minimum rental specification mean? Origin lists a minimum rental commitment in its plan specifications. Confirm the billing term and renewal conditions before committing to this family. ### How do the Origin variants differ? Compare the network port and traffic allowance. The listed CPU, base memory and storage can be similar while the network configuration changes. ### Can I add HDD storage instead of SSD? The drive selectors show the SSD and HDD choices available for Origin. Check the selected drive type, capacity and role in the order summary. ### Are several disks automatically configured as RAID? The catalogue lists individual disk selections. It does not establish an automatic RAID layout; confirm the intended configuration and maintain independent backups. ### Is Windows included with every operating-system choice? Read the selected image and software licence labels. A trial image and a paid licence are different choices, and application licensing remains your responsibility. ### Will I control the operating system and remote console? Plan customer administration and confirm root or administrator credentials. IPMI or an equivalent console must be confirmed, including how recovery access is protected when the operating system is unavailable. ### Is IPv6 included alongside the five IPs? The plan table lists five IPs in a /29 allocation. A /64 IPv6 subnet requires separate operator confirmation; additional address blocks are selected separately. ### Can I request hardware changes after delivery? Confirm compatibility, available drive positions and the maintenance window first. Additional disks, RAM or a migration can require downtime; neither live resizing nor a specific NVMe-drive count is promised. ### How do I verify network protection and bandwidth commitments? Request the actual protection scope and network terms. Port speed and metered or unmetered traffic are listed specifications, rather than an application-throughput or availability guarantee. ## Relevant guides - [Choose a hosting operating model before choosing a cloud](https://swissoctet.com/insights/choose-a-hosting-operating-model/index.txt): Compare shared hosting, a VPS, dedicated hardware and large cloud platforms through responsibility, recovery, dependencies and the complete operating budget. - [Choose a traffic path: server, tunnel or proxy](https://swissoctet.com/insights/choose-a-server-tunnel-or-proxy/index.txt): Understand what a VPS, VPN and proxy each change, then select routing, protocols and operating responsibilities from the connection you actually need. - [Understand the machine boundary behind your VPS](https://swissoctet.com/insights/understand-the-vps-machine-boundary/index.txt): Read KVM, virtual hardware, containers and dedicated servers as operating boundaries, then maintain the shell and services inside the boundary you choose. - [Plan addresses and DNS as parts of your deployment](https://swissoctet.com/insights/plan-addresses-and-dns-for-deployment/index.txt): Separate public, private, static and dedicated addresses, then map forward DNS, reverse DNS and TLS to the parties that can configure them. --- # Metal Atlas > 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. Canonical human page: https://swissoctet.com/services/metal-atlas/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. Dedicated compute with more memory and storage headroom for established workloads. ## Starting configuration Starting configuration: Metal Atlas 01 (metal-atlas-01); USD 284.81 effective monthly base on the shortest available 1-month term; USD 284.81 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Xeon® E5-2680 V4 | | RAM | 64 GB DDR4 ECC | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 1 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | ## Service capabilities ### Dual-Xeon server resources Start from the listed E5-2680 v4 platform and compare the memory, disks and operating-system choices needed for your application environment. ### Memory for a denser stack DDR4 ECC is listed in the base configuration. Review the RAM upgrade choices when combining databases, caches and multiple application services. ### Network variants in the same family Atlas contains different port-speed and traffic combinations. Select the variant that fits the movement of data as well as the compute workload. ### Storage, IPs and software options Add supported drives, review IPv4 allocation and select optional licences. The final summary keeps hardware and software selections visible together. ## Example workloads ### Multi-service application platforms Plan a physical environment for databases, workers and web services with enough memory for their combined activity. ### Virtualisation projects Evaluate the listed hypervisor images and hardware requirements for your own virtual environments and operational model. ### Content and download services Compare the faster network variants when the project moves substantial content to its authorised users. ## A closer look ### Choose the server around the full stack 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. ### A faster port is a separate decision 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. ### Keep administration and hosted services separate 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. ### Plan the management plane before the public workload 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. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Metal Atlas 01 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. Configuration ID: metal-atlas-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 335.07. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 284.81; displayed effective monthly base: USD 284.81. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Xeon® E5-2680 V4 | | RAM | 64 GB DDR4 ECC | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 1 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 284.81 | USD 284.81 | | 3 months | USD 284.81 | USD 854.42 | | 6 months | USD 284.81 | USD 1708.84 | | 12 months | USD 284.81 | USD 3417.68 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024 GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | | Upgrade to 4 TB HDD | USD 13.77 | No | | Upgrade to 8 TB HDD | USD 22.95 | No | | Upgrade to 10 TB HDD | USD 27.54 | No | | Upgrade to 16 TB HDD | USD 41.31 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 22.95 | No | | Add 8 TB HDD | USD 27.54 | No | | Add 10 TB HDD | USD 36.72 | No | | Add 16 TB HDD | USD 45.90 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 22.95 | No | | Add 8 TB HDD | USD 32.13 | No | | Add 10 TB HDD | USD 36.72 | No | | Add 16 TB HDD | USD 45.90 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 143.21 | No | | Upgrade to /24 (254 IPs) | USD 286.41 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ESXi 8.x (64 Bit) | USD 0.00 | Yes | | Ubuntu 23.04 (64 Bit) | USD 0.00 | No | | AlmaLinux 9.2 (64 Bit) | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Ubuntu 22.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 12 Stable (64 Bit) | USD 0.00 | No | | Kali Linux 2023 (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 11 Stable (64 Bit) | USD 0.00 | No | | Windows Server 2022 (64 Bits) (Trial) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Debian 9.X Minimal Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2016 (Licensed) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 9. Stable (64 Bit) | USD 0.00 | No | | Proxmox 8.x Stable (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ### Metal Atlas 02 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. Configuration ID: metal-atlas-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 348.84. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 296.51; displayed effective monthly base: USD 296.51. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Xeon® E5-2680 V4 | | RAM | 64 GB DDR4 ECC | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 10 Gbps | | BANDWIDTH | 100TB | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 296.51 | USD 296.51 | | 3 months | USD 296.51 | USD 889.53 | | 6 months | USD 296.51 | USD 1779.06 | | 12 months | USD 296.51 | USD 3558.13 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024 GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | | Upgrade to 4 TB HDD | USD 13.77 | No | | Upgrade to 8 TB HDD | USD 22.95 | No | | Upgrade to 10 TB HDD | USD 27.54 | No | | Upgrade to 16 TB HDD | USD 41.31 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 22.95 | No | | Add 8 TB HDD | USD 27.54 | No | | Add 10 TB HDD | USD 36.72 | No | | Add 16 TB HDD | USD 45.90 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 22.95 | No | | Add 8 TB HDD | USD 32.13 | No | | Add 10 TB HDD | USD 36.72 | No | | Add 16 TB HDD | USD 45.90 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 143.21 | No | | Upgrade to /24 (254 IPs) | USD 286.41 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ESXi 8.x (64 Bit) | USD 0.00 | Yes | | Ubuntu 23.04 (64 Bit) | USD 0.00 | No | | AlmaLinux 9.2 (64 Bit) | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Ubuntu 22.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 12 Stable (64 Bit) | USD 0.00 | No | | Kali Linux 2023 (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 11 Stable (64 Bit) | USD 0.00 | No | | Windows Server 2022 (64 Bits) (Trial) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Debian 9.X Minimal Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2016 (Licensed) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 9. Stable (64 Bit) | USD 0.00 | No | | Proxmox 8.x Stable (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ### Metal Atlas 03 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. Configuration ID: metal-atlas-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 761.93. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 647.64; displayed effective monthly base: USD 647.64. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Xeon® E5-2680 V4 | | RAM | 64 GB DDR4 ECC | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 10 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 647.64 | USD 647.64 | | 3 months | USD 647.64 | USD 1942.93 | | 6 months | USD 647.64 | USD 3885.85 | | 12 months | USD 647.64 | USD 7771.70 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024 GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | | Upgrade to 4 TB HDD | USD 13.77 | No | | Upgrade to 8 TB HDD | USD 22.95 | No | | Upgrade to 10 TB HDD | USD 27.54 | No | | Upgrade to 16 TB HDD | USD 41.31 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 22.95 | No | | Add 8 TB HDD | USD 27.54 | No | | Add 10 TB HDD | USD 36.72 | No | | Add 16 TB HDD | USD 45.90 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 22.95 | No | | Add 8 TB HDD | USD 32.13 | No | | Add 10 TB HDD | USD 36.72 | No | | Add 16 TB HDD | USD 45.90 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 143.21 | No | | Upgrade to /24 (254 IPs) | USD 286.41 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ESXi 8.x (64 Bit) | USD 0.00 | Yes | | Ubuntu 23.04 (64 Bit) | USD 0.00 | No | | AlmaLinux 9.2 (64 Bit) | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Ubuntu 22.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 12 Stable (64 Bit) | USD 0.00 | No | | Kali Linux 2023 (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 11 Stable (64 Bit) | USD 0.00 | No | | Windows Server 2022 (64 Bits) (Trial) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Debian 9.X Minimal Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2016 (Licensed) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 9. Stable (64 Bit) | USD 0.00 | No | | Proxmox 8.x Stable (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ### Metal Atlas 04 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. Configuration ID: metal-atlas-04. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 1192.47. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 1013.60; displayed effective monthly base: USD 1013.60. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Xeon® E5-2680 V4 | | RAM | 64 GB DDR4 ECC | | STORAGE | 1 TB SSD SATA3 | | PORT SPEED | 20 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 1013.60 | USD 1013.60 | | 3 months | USD 1013.60 | USD 3040.80 | | 6 months | USD 1013.60 | USD 6081.59 | | 12 months | USD 1013.60 | USD 12163.18 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024 GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | | Upgrade to 4 TB HDD | USD 13.77 | No | | Upgrade to 8 TB HDD | USD 22.95 | No | | Upgrade to 10 TB HDD | USD 27.54 | No | | Upgrade to 16 TB HDD | USD 41.31 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 22.95 | No | | Add 8 TB HDD | USD 27.54 | No | | Add 10 TB HDD | USD 36.72 | No | | Add 16 TB HDD | USD 45.90 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | | Add 4 TB HDD | USD 22.95 | No | | Add 8 TB HDD | USD 32.13 | No | | Add 10 TB HDD | USD 36.72 | No | | Add 16 TB HDD | USD 45.90 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 143.21 | No | | Upgrade to /24 (254 IPs) | USD 286.41 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | ESXi 8.x (64 Bit) | USD 0.00 | Yes | | Ubuntu 23.04 (64 Bit) | USD 0.00 | No | | AlmaLinux 9.2 (64 Bit) | USD 0.00 | No | | FreeBSD 13.2 (64 Bit) | USD 0.00 | No | | Ubuntu 22.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 12 Stable (64 Bit) | USD 0.00 | No | | Kali Linux 2023 (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 11 Stable (64 Bit) | USD 0.00 | No | | Windows Server 2022 (64 Bits) (Trial) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Debian 9.X Minimal Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2016 (Licensed) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Debian 9. Stable (64 Bit) | USD 0.00 | No | | Proxmox 8.x Stable (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ## Service questions ### Which Atlas variant should I choose? Compare port speed and traffic alongside price and options. Select the network configuration that fits your usage, then verify the complete hardware summary. ### Can I choose a hypervisor image? The operating-system selector includes hypervisor choices where listed. Verify hardware, licensing and operational requirements before using one for your own virtualisation platform. ### What does ECC in the memory specification tell me? It identifies the memory type listed for the base server. It does not replace backups, software monitoring or a tested recovery process. ### Can I separate data across additional drives? Yes. The configurator lists additional-drive choices. Confirm your intended storage layout and filesystem plan; the options describe drives, not an automatic application architecture. ### Are the optional hosting panels unrestricted? Check each licence's account or domain allowance and system requirements. The server resources and the limits of a selected software licence are separate. ### What access is available if the operating system stops responding? 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. ### Can I build a private network or cluster? 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. ### What address allocation is included? Atlas lists five IPs in a /29 allocation, with optional additional blocks. Confirm IPv6 availability and usable addressing before planning firewall or routing rules. ### Are hardware upgrades and guaranteed throughput automatic? 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. ## Relevant guides - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. - [Swiss data residency: map the whole service](https://swissoctet.com/insights/swiss-data-residency-map/index.txt): A Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment. - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. - [A dedicated-server migration runbook that protects the data](https://swissoctet.com/insights/dedicated-server-migration-runbook/index.txt): Rehearse the move, establish a consistent data boundary and define what rollback means after the new system accepts writes. - [Turn RPO and RTO into a recovery budget you can test](https://swissoctet.com/insights/rpo-rto-recovery-budget/index.txt): Translate acceptable data loss and interruption into a timed recovery plan, with dependencies, restore capacity and a measurable exercise. - [Size a transfer with latency, concurrency and throughput measurements](https://swissoctet.com/insights/size-throughput-with-bandwidth-delay/index.txt): Build a repeatable transfer model using payload volume, delivery windows and round-trip time, then test it without confusing a port label with useful throughput. - [Build monitoring that leads to a useful incident response](https://swissoctet.com/insights/monitoring-incident-response-playbook/index.txt): Connect application symptoms, actionable alerts and a small response playbook so that an operator can make clear decisions when a service degrades. --- # Metal Zenith > A Swiss physical platform built around dual Xeon Gold processors. Metal Zenith offers a configurable balance of memory, SSD storage and network capacity for applications ready for a dedicated server. Canonical human page: https://swissoctet.com/services/metal-zenith/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. A step up in dedicated infrastructure for workloads that demand substantial resources. ## Starting configuration Starting configuration: Metal Zenith 01 (metal-zenith-01); USD 351.13 effective monthly base on the shortest available 1-month term; USD 351.13 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon ® Gold 6134 | | RAM | 64 GB DDR4 | | STORAGE | 1 TB SSD | | PORT SPEED | 1 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | ## Service capabilities ### A Xeon Gold foundation The Zenith plans list a dual Gold 6134 platform. Compare your software's requirements against the exact server specification before choosing the range. ### Memory matched to the application Choose the RAM allocation for databases, caching and concurrent services. Upgrade options are separate from the network variant you select. ### Several SSD positions to plan The configurator lists primary and additional SSD options, giving you choices for application data, working space or a planned storage layout. ### A defined network configuration Compare the listed port speed and traffic in each Zenith plan. Optional IP and bandwidth choices are displayed alongside the hardware. ## Example workloads ### Production application backends Plan a dedicated server for a measured application workload with controlled access and a documented recovery process. ### Database and analytics stacks Size memory and SSD capacity for your dataset and query patterns before selecting a network-focused variant. ### Consolidated service environments Organise several compatible services on a physical foundation, with deliberate separation of access and resource use. ## A closer look ### Choose performance by requirement A processor family name is a starting point, not an application benchmark. Compare the actual CPU platform, memory and storage with your workload. For a CPU-heavy service, test representative jobs; for a database, include memory usage and disk activity in the decision. ### Shape the storage before deploying Zenith's drive selectors allow a larger or multi-drive configuration where listed. Decide what belongs on each volume, how it will be backed up and what a restoration requires. Extra drives can help organise a server, but copies on the same machine do not protect against every failure. ### Keep the Swiss location meaningful The catalogue offers this family only in Switzerland, keeping the hosting destination explicit. Use the same clarity for your deployment: document which data is stored, who administers it and which public services are exposed. A no-KYC purchase path works best with careful access and data handling afterwards. ### Confirm the practical controls of a physical deployment Zenith lists a physical server and five IPs in a /29 allocation. Agree root or administrator access and an IPMI or equivalent recovery route before delivery. Confirm IPv6, network protection, storage compatibility and the upgrade procedure for the actual machine. A port specification does not establish a dedicated-throughput commitment or delivery deadline. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Metal Zenith 01 A dedicated dual Xeon Gold 6134 configuration with 64 GB of DDR4 memory and a 1 TB SSD. Its 1 Gbps port is paired with a listed unmetered traffic allocation. Configuration ID: metal-zenith-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 413.10. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 351.13; displayed effective monthly base: USD 351.13. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon ® Gold 6134 | | RAM | 64 GB DDR4 | | STORAGE | 1 TB SSD | | PORT SPEED | 1 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 351.13 | USD 351.13 | | 3 months | USD 330.48 | USD 991.43 | | 6 months | USD 330.48 | USD 1982.86 | | 12 months | USD 309.82 | USD 3717.86 | | 18 months | USD 309.82 | USD 5576.79 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Sixth Drive Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 161.57 | No | | Upgrade to /24 (254 IPs) | USD 323.13 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | Yes | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ### Metal Zenith 02 Dual Xeon Gold 6134 processors provide the compute foundation, while a 10 Gbps port carries a 100 TB traffic allowance. The configuration includes 64 GB of DDR4 memory and a 1 TB SSD. Configuration ID: metal-zenith-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 550.79. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 468.17; displayed effective monthly base: USD 468.17. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon ® Gold 6134 | | RAM | 64 GB DDR4 | | STORAGE | 1TB SSD | | PORT SPEED | 10 Gbps | | BANDWIDTH | 100TB | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 468.17 | USD 468.17 | | 3 months | USD 440.64 | USD 1321.91 | | 6 months | USD 440.64 | USD 2643.81 | | 12 months | USD 413.10 | USD 4957.15 | | 18 months | USD 413.10 | USD 7435.72 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Sixth Drive Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 161.57 | No | | Upgrade to /24 (254 IPs) | USD 323.13 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | Yes | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ### Metal Zenith 03 An unmetered-traffic option on a 10 Gbps port for the dual Xeon Gold 6134 platform. This dedicated configuration includes 64 GB of DDR4 memory and 1 TB of SSD storage. Configuration ID: metal-zenith-03. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 826.19. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 702.26; displayed effective monthly base: USD 702.26. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon ® Gold 6134 | | RAM | 64 GB DDR4 | | STORAGE | 1TB SSD | | PORT SPEED | 10 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 702.26 | USD 702.26 | | 3 months | USD 660.95 | USD 1982.86 | | 6 months | USD 660.95 | USD 3965.72 | | 12 months | USD 619.64 | USD 7435.72 | | 18 months | USD 619.64 | USD 11153.58 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 1024GB DDR4 | USD 1101.59 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 32.13 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### Sixth Drive Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 32.13 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 161.57 | No | | Upgrade to /24 (254 IPs) | USD 323.13 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | Yes | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ## Service questions ### How does Zenith differ from Atlas? The listed CPU platform differs, as do some available options. Compare the complete processor, memory, storage and network specifications rather than relying on the family name. ### Can I add more than one storage drive? The Zenith configurator lists multiple additional-drive positions. Review each selected capacity and confirm the storage layout intended for the server. ### Is the faster network variant always the best choice? Only when it fits your data-transfer requirements. A faster port does not solve CPU, memory or database limits, and the traffic model also needs review. ### Can I request a custom operating system? A custom choice is listed where available and requires confirmation. Treat it as a configuration request rather than assuming any image can be installed automatically. ### What should I prepare before moving a production service? Check software compatibility, create an independent backup and plan a rollback. Test the application and access on the new environment before switching real traffic. ### How does Zenith differ from a virtual server? The catalogue specifies bare-metal hardware rather than a KVM instance. A virtualisation layer is your own deployment choice; confirm operating-system administration and hardware compatibility for the intended stack. ### Will I have an IPMI recovery console? Confirm IPMI or equivalent management access and how it is secured. The current plan table does not establish a verified recovery-console service. ### Are IPv6 and basic network protection included? Five IPs in a /29 allocation are listed. IPv6 availability and the protection scope must be confirmed with the operator before becoming part of the delivery agreement. ### Can I upgrade the installed hardware later? Changes require compatibility, stock and maintenance review. Confirm any interruption or migration; the initial drive and RAM selectors do not promise live hardware upgrades. ## Relevant guides - [A dedicated-server migration runbook that protects the data](https://swissoctet.com/insights/dedicated-server-migration-runbook/index.txt): Rehearse the move, establish a consistent data boundary and define what rollback means after the new system accepts writes. - [Snapshots and backups: choose the failure you need to survive](https://swissoctet.com/insights/snapshots-backups-consistency/index.txt): Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection. --- # Metal Hyper > A dual Gold 6430 platform for a substantial Swiss deployment. Metal Hyper combines DDR5 memory with configurable storage and a listed high-speed port, keeping the final hardware choices in your hands. Canonical human page: https://swissoctet.com/services/metal-hyper/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. High-capacity dedicated configurations for intensive applications and larger deployments. ## Starting configuration Starting configuration: Metal Hyper 01 (metal-hyper-01); USD 642.59 effective monthly base on the shortest available 1-month term; USD 642.59 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Gold 6430 | | RAM | 64GB DDR5 | | STORAGE | 1TB NVMe | | PORT SPEED | 10GBPS | | BANDWIDTH | 100TB | | IPS | 5 | ## Service capabilities ### A modern listed compute foundation The range lists dual Intel Gold 6430 processors and DDR5 memory. Review the exact hardware summary alongside your application and operating-system requirements. ### Memory headroom by selection Choose among the listed DDR5 upgrades when the application needs a larger working set. Memory and CPU demands should be planned together. ### Storage defined by the variant Hyper variants differ in their primary storage and traffic description. Read the selected plan rather than assuming every variant has the same disk technology. ### A complete configurable server Additional disks, IPv4 space, operating systems and optional software are separate choices. Review the resulting machine as a whole before ordering. ## Example workloads ### Larger application platforms Plan a Swiss physical environment for multiple services with measured memory, CPU and data-transfer needs. ### Memory-intensive processing Choose RAM for substantial working datasets or concurrent tasks that need to remain in memory. ### Private infrastructure foundations Evaluate the hypervisor and system options for your own managed environment with a clear access and recovery model. ## A closer look ### Size the machine as one system A substantial server needs a balanced plan. Large memory allocations are useful only when the software can use them, while disk access and network traffic may remain the bottleneck. Begin with a measured workload and the expected growth, then choose the hardware options that address those requirements. ### Read the differences between the variants Hyper's plan table lists the primary disk and traffic model separately for each variant. Compare those details carefully, then add supported secondary drives if the project needs more capacity. The storage layout and backup strategy should be defined before the machine receives production data. ### Build private operations around a Swiss location The catalogue keeps this server family in Switzerland. Use restricted management access, separate operator roles and a documented software-maintenance process around it. Protect customer information in applications and backups; neither the server's size nor its offshore location establishes an automatic security policy. ### Agree the operational details before reserving capacity Hyper's catalogue describes physical resources with five IPs. Confirm stock, deployment timing, root or administrator access and a secured remote console before an order. IPv6 allocation, protection scope and any dedicated-network commitment also require actual delivery terms. Decide how later hardware work will be backed up and scheduled, rather than assuming an existing machine can change without interruption. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Metal Hyper 01 A dedicated dual Intel Gold 6430 configuration with 64 GB of DDR5 memory and a 1 TB NVMe drive. The listed network allocation is a 10 Gbps port with 100 TB of traffic. Configuration ID: metal-hyper-01. Location: Switzerland / CH. Availability: operator review required. Nominal monthly base rate before billing-period pricing: USD 642.59. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 642.59; displayed effective monthly base: USD 642.59. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Gold 6430 | | RAM | 64GB DDR5 | | STORAGE | 1TB NVMe | | PORT SPEED | 10GBPS | | BANDWIDTH | 100TB | | IPS | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 642.59 | USD 642.59 | | 3 months | USD 642.59 | USD 1927.78 | | 6 months | USD 642.59 | USD 3855.56 | | 12 months | USD 610.46 | USD 7325.56 | | 18 months | USD 578.33 | USD 10410.01 | The option defaults need operator confirmation before collection. #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | Upgrade to 128 GB DDR5 | USD 367.20 | No | | Upgrade to 256 GB DDR5 | USD 734.39 | No | | Upgrade to 512 GB DDR5 | USD 1468.78 | No | | Upgrade to 1024 GB DDR5 | USD 5507.94 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### Sixth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | /28 (14 IPs) | USD 20.20 | No | | /27 (30 IPs) | USD 40.39 | No | | /26 (62 IPs) | USD 80.78 | No | | /25 (126 IPs) | USD 143.21 | No | | /24 (254 IPs) | USD 286.41 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Alma Linux 9 | USD 0.00 | Yes | | Alma Linux 8 | USD 0.00 | No | | Debian 12 | USD 0.00 | No | | Debian 11 | USD 0.00 | No | | FreeBSD 14 | USD 0.00 | No | | FreeBSD 13 | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows 10 PRO (Trial) | USD 0.00 | No | | Microsoft Windows 11 PRO (Trial) | USD 0.00 | No | | Microsoft Servers 2016 (Trial) | USD 0.00 | No | | Microsoft Servers 2019 (Trial) | USD 0.00 | No | | Microsoft Servers 2022 (Trial) | USD 0.00 | No | | Microsoft Servers 2025 (Trial) | USD 0.00 | No | | Proxmox 8 | USD 0.00 | No | | Proxmox 7 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 23 | USD 0.00 | No | | Ubuntu 24 | USD 0.00 | No | | Rocky Linux 9 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Fedora Server 41 | USD 0.00 | No | | Custom OS | Operator quote required; not assumed free | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 78.03 | No | ### Metal Hyper 02 This dual Intel Gold 6430 variant pairs 64 GB of DDR5 memory and a 1 TB SSD with a 10 Gbps port and unmetered traffic. Compare its SSD specification with the NVMe allocation in Hyper 01. Configuration ID: metal-hyper-02. Location: Switzerland / CH. Availability: operator review required. Nominal monthly base rate before billing-period pricing: USD 1055.69. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 1055.69; displayed effective monthly base: USD 1055.69. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Gold 6430 | | RAM | 64GB DDR5 | | STORAGE | 1TB SSD | | PORT SPEED | 10GBPS | | BANDWIDTH | UNMETERED | | IPS | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 1055.69 | USD 1055.69 | | 3 months | USD 1055.69 | USD 3167.07 | | 6 months | USD 1055.69 | USD 6334.13 | | 12 months | USD 1002.90 | USD 12034.85 | | 18 months | USD 950.12 | USD 17102.15 | The option defaults need operator confirmation before collection. #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base memory allocation | USD 0.00 | Yes | | Upgrade to 128 GB DDR5 | USD 367.20 | No | | Upgrade to 256 GB DDR5 | USD 734.39 | No | | Upgrade to 512 GB DDR5 | USD 1468.78 | No | | Upgrade to 1024 GB DDR5 | USD 5507.94 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### Sixth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1 TB SSD | USD 13.77 | No | | 2 TB SSD | USD 27.54 | No | | 4 TB SSD | USD 41.31 | No | | 8 TB SSD | USD 55.08 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | /28 (14 IPs) | USD 20.20 | No | | /27 (30 IPs) | USD 40.39 | No | | /26 (62 IPs) | USD 80.78 | No | | /25 (126 IPs) | USD 143.21 | No | | /24 (254 IPs) | USD 286.41 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Alma Linux 9 | USD 0.00 | Yes | | Alma Linux 8 | USD 0.00 | No | | Debian 12 | USD 0.00 | No | | Debian 11 | USD 0.00 | No | | FreeBSD 14 | USD 0.00 | No | | FreeBSD 13 | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows 10 PRO (Trial) | USD 0.00 | No | | Microsoft Windows 11 PRO (Trial) | USD 0.00 | No | | Microsoft Servers 2016 (Trial) | USD 0.00 | No | | Microsoft Servers 2019 (Trial) | USD 0.00 | No | | Microsoft Servers 2022 (Trial) | USD 0.00 | No | | Microsoft Servers 2025 (Trial) | USD 0.00 | No | | Proxmox 8 | USD 0.00 | No | | Proxmox 7 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 23 | USD 0.00 | No | | Ubuntu 24 | USD 0.00 | No | | Rocky Linux 9 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Fedora Server 41 | USD 0.00 | No | | Custom OS | Operator quote required; not assumed free | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 78.03 | No | ## Service questions ### Do both Hyper variants use the same primary storage? Check the plan table. The listed primary-storage description differs between variants, so the selected plan is the reference for the base disk. ### Can I choose a larger DDR5 allocation? Yes. The RAM selector lists the available DDR5 upgrades. Review the selected capacity and recurring price in the final configuration. ### Is all traffic unmetered? The Hyper variants list different traffic models. Select the appropriate plan and review its allowance rather than applying one variant's description to the whole family. ### Can I use the server for virtualisation? Hyper lists hypervisor choices in the operating-system options. Verify your hypervisor requirements, licensing and intended configuration before deploying virtual machines. ### Does the server include a fully managed application platform? The catalogue describes hardware and selected software options. Define installation, ongoing administration, monitoring and backups as part of your own operational plan. ### Is a configuration listing proof of current stock? No. A configuration listing does not establish current hardware availability. Confirm stock and delivery for the complete selected configuration before ordering. ### Can I recover the machine through IPMI? Confirm an IPMI or equivalent console, its access restrictions and administrator credentials before delivery. Its inclusion is not verified by the current hardware table. ### What IP and protection details should I confirm? The plan lists five IPs, with additional blocks as options. Confirm IPv6, usable allocation and baseline network protection separately. ### Can hardware change without affecting my applications? Hardware work may require a maintenance window or migration. Confirm compatibility, backup requirements and expected interruption before adding resources to a delivered server. ## Relevant guides - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. - [Measure NVMe performance without misleading yourself](https://swissoctet.com/insights/nvme-benchmark-methodology/index.txt): Define the I/O pattern, control cache effects and inspect latency distributions before drawing an application conclusion from a disk test. - [Build a GPU VRAM budget before choosing hardware](https://swissoctet.com/insights/gpu-vram-budget-for-real-workloads/index.txt): Account for weights, activations, caches and temporary buffers, then test the peak workload rather than the model file alone. - [From detected transaction to reconciled order: confirmations and reorgs](https://swissoctet.com/insights/confirmations-reorgs-order-reconciliation/index.txt): Design payment states around verified chain evidence, explicit acceptance rules and unambiguous order association rather than a browser claim that funds were sent. --- # Metal EPYC > An AMD EPYC foundation for your Swiss server stack. Choose the network variant, memory and storage around parallel applications, virtual environments or data-heavy services that fit the listed hardware. Canonical human page: https://swissoctet.com/services/metal-epyc/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. AMD-powered dedicated hardware for parallel workloads and serious compute. ## Starting configuration Starting configuration: Metal EPYC 01 (metal-epyc-01); USD 371.79 effective monthly base on the shortest available 1-month term; USD 371.79 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | AMD EPYC 7452 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 10GBPS | | BANDWIDTH | 100TB | | IPS | 5 | ## Service capabilities ### An AMD server platform The range lists an EPYC 7452 processor foundation. Check application support and workload behaviour when comparing it with the Intel server families. ### NVMe in the base plans The EPYC plans list NVMe primary storage. Additional drive selections have their own descriptions and should be reviewed separately. ### Network variants for your data Compare port speed and metered or unmetered traffic combinations. Choose the transfer model that suits the application rather than selecting speed alone. ### Memory, IPs and software choices Select the listed RAM upgrades, address allocation and operating environment. Optional hosting licences remain distinct from the physical resources. ## Example workloads ### Parallel application workers Run a workload that can distribute useful work across the processor, after checking its actual CPU and memory needs. ### Virtual infrastructure Evaluate the listed hypervisor options for a private environment with deliberate resource allocation and restricted administration. ### Data-intensive services Combine primary NVMe storage with a suitable network variant for applications that process and move significant datasets. ## A closer look ### Choose AMD for the workload it serves Software uses processor resources in different ways. A service with one busy thread and a batch job with many independent tasks may favour different configurations. Compare your application's compatibility and measured behaviour against the listed EPYC platform instead of relying on a generic performance claim. ### Keep storage and transfer in balance The EPYC base plans list NVMe storage, but the amount of data you can serve also depends on the application, network and traffic model. Review the port and allowance together. Additional-drive choices can expand capacity; their labels identify the storage being added. ### Give each operational layer a clear owner A dedicated server can support several applications or virtual environments, each with its own access needs. Decide who handles the host, guest systems, software and backups. A Swiss location and no-KYC order flow sit alongside these controls, while secure operation depends on how you configure the stack. ### Take the AMD platform through a compatibility review For virtualisation, databases, scientific processing or business applications, verify the software against the EPYC model and the selected memory and storage layout. The physical-server plan lists five IPs; confirm root or administrator credentials, recovery-console access, IPv6 and network protection before delivery. Hardware stock, reinstall methods and later upgrades need a specific operator-approved procedure. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Metal EPYC 01 An AMD EPYC 7452 dedicated configuration with 64 GB of DDR4 memory and a 1 TB NVMe drive. A 10 Gbps port is paired with a 100 TB traffic allowance. Configuration ID: metal-epyc-01. Location: Switzerland / CH. Availability: operator review required. Nominal monthly base rate before billing-period pricing: USD 413.10. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 371.79; displayed effective monthly base: USD 371.79. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | AMD EPYC 7452 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 10GBPS | | BANDWIDTH | 100TB | | IPS | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 371.79 | USD 371.79 | | 3 months | USD 371.79 | USD 1115.36 | | 6 months | USD 371.79 | USD 2230.72 | | 12 months | USD 371.79 | USD 4461.43 | | 18 months | USD 371.79 | USD 6692.15 | The option defaults need operator confirmation before collection. #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Sixth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 161.57 | No | | Upgrade to /24 (254 IPs) | USD 323.13 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 78.03 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Alma Linux 8 | USD 0.00 | Yes | | Alma Linux 9 | USD 8.26 | No | | Debian 12 | USD 0.00 | No | | Debian 11 | USD 0.00 | No | | FreeBSD 14 | USD 0.00 | No | | FreeBSD 13 | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows 10 Pro (Trial) | USD 0.00 | No | | Microsoft Windows 11 Pro (Trial) | USD 0.00 | No | | Microsoft Windows Server 2016 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2019 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2022 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2025 (Trial) | USD 0.00 | No | | Proxmox 7 | USD 0.00 | No | | Proxmox 8 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 23 | USD 0.00 | No | | Ubuntu 24 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Rocky Linux 9 | USD 0.00 | No | | Fedora Server 41 | USD 0.00 | No | ### Metal EPYC 03 Move to a 25 Gbps port while keeping a 100 TB traffic allowance. The dedicated AMD EPYC 7452 platform includes 64 GB of DDR4 memory and a 1 TB NVMe drive. Configuration ID: metal-epyc-03. Location: Switzerland / CH. Availability: operator review required. Nominal monthly base rate before billing-period pricing: USD 439.72. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 395.75; displayed effective monthly base: USD 395.75. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | AMD EPYC 7452 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 25GBPS | | BANDWIDTH | 100tb | | IPS | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 395.75 | USD 395.75 | | 3 months | USD 395.75 | USD 1187.24 | | 6 months | USD 395.75 | USD 2374.47 | | 12 months | USD 395.75 | USD 4748.95 | | 18 months | USD 395.75 | USD 7123.42 | The option defaults need operator confirmation before collection. #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Sixth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 161.57 | No | | Upgrade to /24 (254 IPs) | USD 323.13 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 78.03 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Alma Linux 8 | USD 0.00 | Yes | | Alma Linux 9 | USD 8.26 | No | | Debian 12 | USD 0.00 | No | | Debian 11 | USD 0.00 | No | | FreeBSD 14 | USD 0.00 | No | | FreeBSD 13 | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows 10 Pro (Trial) | USD 0.00 | No | | Microsoft Windows 11 Pro (Trial) | USD 0.00 | No | | Microsoft Windows Server 2016 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2019 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2022 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2025 (Trial) | USD 0.00 | No | | Proxmox 7 | USD 0.00 | No | | Proxmox 8 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 23 | USD 0.00 | No | | Ubuntu 24 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Rocky Linux 9 | USD 0.00 | No | | Fedora Server 41 | USD 0.00 | No | ### Metal EPYC 02 The 10 Gbps EPYC configuration with unmetered traffic, using an AMD EPYC 7452 processor, 64 GB of DDR4 memory and 1 TB of NVMe storage. Configuration ID: metal-epyc-02. Location: Switzerland / CH. Availability: operator review required. Nominal monthly base rate before billing-period pricing: USD 917.99. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 826.19; displayed effective monthly base: USD 826.19. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | AMD EPYC 7452 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 10GBPS | | BANDWIDTH | UNMETERED | | IPS | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 826.19 | USD 826.19 | | 3 months | USD 826.19 | USD 2478.57 | | 6 months | USD 826.19 | USD 4957.15 | | 12 months | USD 826.19 | USD 9914.29 | | 18 months | USD 826.19 | USD 14871.44 | The option defaults need operator confirmation before collection. #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Sixth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 161.57 | No | | Upgrade to /24 (254 IPs) | USD 323.13 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 78.03 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Alma Linux 8 | USD 0.00 | Yes | | Alma Linux 9 | USD 8.26 | No | | Debian 12 | USD 0.00 | No | | Debian 11 | USD 0.00 | No | | FreeBSD 14 | USD 0.00 | No | | FreeBSD 13 | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows 10 Pro (Trial) | USD 0.00 | No | | Microsoft Windows 11 Pro (Trial) | USD 0.00 | No | | Microsoft Windows Server 2016 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2019 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2022 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2025 (Trial) | USD 0.00 | No | | Proxmox 7 | USD 0.00 | No | | Proxmox 8 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 23 | USD 0.00 | No | | Ubuntu 24 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Rocky Linux 9 | USD 0.00 | No | | Fedora Server 41 | USD 0.00 | No | ### Metal EPYC 04 The broadest EPYC network allocation combines a 25 Gbps port with unmetered traffic. Its hardware specification includes an AMD EPYC 7452 processor, 64 GB of DDR4 memory and a 1 TB NVMe drive. Configuration ID: metal-epyc-04. Location: Switzerland / CH. Availability: operator review required. Nominal monthly base rate before billing-period pricing: USD 1652.38. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 1487.14; displayed effective monthly base: USD 1487.14. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | AMD EPYC 7452 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 25GBPS | | BANDWIDTH | UNMETERED | | IPS | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 1487.14 | USD 1487.14 | | 3 months | USD 1487.14 | USD 4461.43 | | 6 months | USD 1487.14 | USD 8922.86 | | 12 months | USD 1487.14 | USD 17845.73 | | 18 months | USD 1487.14 | USD 26768.59 | The option defaults need operator confirmation before collection. #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### Sixth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | 1TB SSD | USD 13.77 | No | | 2TB SSD | USD 27.54 | No | | 4TB SSD | USD 41.31 | No | | 8TB SSD | USD 55.08 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 161.57 | No | | Upgrade to /24 (254 IPs) | USD 323.13 | No | ##### Bandwidth | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base traffic allowance | USD 0.00 | Yes | | Upgrade to 200 TB | USD 45.90 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 78.03 | No | | Plesk (10 Domains) | USD 18.36 | No | | Plesk (30 Domains) | USD 27.54 | No | | Plesk (50 Domains) | USD 59.67 | No | | ISPManager Lite (10 domains) | USD 9.18 | No | | ISPManager Pro (50 Domains) | USD 13.77 | No | | ISPManager Unlimited (Unlimited domains) | USD 27.54 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Alma Linux 8 | USD 0.00 | Yes | | Alma Linux 9 | USD 8.26 | No | | Debian 12 | USD 0.00 | No | | Debian 11 | USD 0.00 | No | | FreeBSD 14 | USD 0.00 | No | | FreeBSD 13 | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows 10 Pro (Trial) | USD 0.00 | No | | Microsoft Windows 11 Pro (Trial) | USD 0.00 | No | | Microsoft Windows Server 2016 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2019 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2022 (Trial) | USD 0.00 | No | | Microsoft Windows Server 2025 (Trial) | USD 0.00 | No | | Proxmox 7 | USD 0.00 | No | | Proxmox 8 | USD 0.00 | No | | Ubuntu 20 | USD 0.00 | No | | Ubuntu 22 | USD 0.00 | No | | Ubuntu 23 | USD 0.00 | No | | Ubuntu 24 | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Rocky Linux 9 | USD 0.00 | No | | Fedora Server 41 | USD 0.00 | No | ## Service questions ### What changes between the EPYC plans? Compare the network port and traffic model in the table. Review all specifications and options before choosing, even when the base CPU and storage appear similar. ### Does every additional disk use NVMe? The primary storage is listed as NVMe. Read the separate additional-drive labels; they may specify SSD storage without describing it as NVMe. ### Will EPYC make any application faster? No universal benchmark is claimed. The benefit depends on software compatibility, parallelism and the workload's CPU, memory and storage limits. ### Can I select an Intel server instead? Yes. The Metal families include Intel configurations. Compare the complete hardware, network and software requirements rather than choosing only by processor brand. ### What should I check for a virtualisation deployment? Verify the selected hypervisor's requirements, plan resource allocation and secure host administration. Include guest backups and recovery procedures before running production services. ### Does EPYC imply a GPU or an AI stack is included? No. The EPYC specification describes a CPU platform. Accelerated workloads need a separately listed GPU and compatible software; compare Tensor if an accelerator is part of the requirement. ### What administration and recovery access should I expect? Confirm root or administrator credentials and a secured IPMI or equivalent console. Bare-metal hardware does not itself verify a delivered remote-management workflow. ### What is the address and protection scope? The plans list five IPs and optional additional blocks. Confirm IPv6 allocation and baseline network protection separately before relying on them. ### Are stock, reinstallations and upgrades confirmed? They require operator validation for the actual server. Review image support, disk compatibility and any maintenance window; a listed configuration does not establish current stock or instant reinstalls. ## Relevant guides - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. - [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/index.txt): Secure administration, expose only required services and establish updates and recovery without locking yourself out. - [Measure NVMe performance without misleading yourself](https://swissoctet.com/insights/nvme-benchmark-methodology/index.txt): Define the I/O pattern, control cache effects and inspect latency distributions before drawing an application conclusion from a disk test. - [A dedicated-server migration runbook that protects the data](https://swissoctet.com/insights/dedicated-server-migration-runbook/index.txt): Rehearse the move, establish a consistent data boundary and define what rollback means after the new system accepts writes. - [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/index.txt): Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. - [Understand the machine boundary behind your VPS](https://swissoctet.com/insights/understand-the-vps-machine-boundary/index.txt): Read KVM, virtual hardware, containers and dedicated servers as operating boundaries, then maintain the shell and services inside the boundary you choose. --- # Transit 40 > Build around a listed 40 Gbps port in Switzerland. Transit 40 pairs dedicated hardware with an unmetered traffic specification for projects where moving data is a central part of the job. Canonical human page: https://swissoctet.com/services/transit-40/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. Dedicated configurations with a 40 Gbps port for bandwidth-intensive applications. ## Starting configuration Starting configuration: Transit 40 01 (transit-40-01); USD 1926.86 effective monthly base on the shortest available 1-month term; USD 1926.86 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Gold 6134 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 40 GBPS | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | ## Service capabilities ### A high-capacity server port Each Transit 40 plan lists a 40 Gbps port. Treat that specification as the network interface choice when designing the complete application pipeline. ### Dedicated compute beside the network Choose between the listed CPU variants, then size memory and storage to keep up with the work performed around the data. ### A configurable disk layout Review the primary and additional-drive options for content, caches or working datasets. Storage performance matters when serving large amounts of data. ### Addresses and operating environment Select additional IPv4 allocation and the listed system or software choices. Keep application, public network and administration requirements distinct. ## Example workloads ### Content distribution origins Provide a Swiss origin environment for authorised downloads or media, with storage and application capacity sized alongside the port. ### Large data-transfer workflows Move your own project datasets or exports through a dedicated environment with appropriate receiver capacity. ### Network-heavy application services Evaluate a high-port-speed server when measurement shows that data movement is a limiting factor in the application. ## A closer look ### A fast port needs a capable pipeline Network port speed is one component of end-to-end throughput. Disk reads, protocol overhead, CPU processing, remote networks and the receiving application can all reduce the transfer rate. Design and test the full pipeline instead of treating the port label as a guaranteed download speed. ### Compare the compute variants as well Transit 40 keeps the port specification consistent while offering different CPU foundations. Choose the hardware around any encryption, compression, media handling or request processing your application performs. Add memory and storage for the active working set rather than increasing them without a purpose. ### Keep data movement accountable High network capacity is intended for legitimate applications and authorised content distribution. Use access controls, monitor your application and document which data may be served. A Swiss offshore location does not make network abuse acceptable or replace a response plan for compromised software. ### Specify the connection agreement around the port Transit 40 lists bare-metal hardware, unmetered traffic and five IPs in a /29 allocation. Confirm IPv6, network protection and secure remote-console access with the operator. Dedicated bandwidth, burst handling and dashboard monitoring require documented service terms. Plan application measurements and management access alongside those network questions before delivery. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Transit 40 01 A 40 Gbps port and unmetered traffic accompany dedicated dual Intel Gold 6134 hardware. The base configuration includes 64 GB of DDR4 memory, a 1 TB NVMe drive and five IP addresses in a /29 allocation. Configuration ID: transit-40-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 1926.86. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 1926.86; displayed effective monthly base: USD 1926.86. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Gold 6134 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 40 GBPS | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 1926.86 | USD 1926.86 | | 3 months | USD 1734.17 | USD 5202.52 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 768 GB DDR4 | USD 1101.59 | No | | Upgrade to 1024 GB DDR4 | USD 275.40 | No | ##### Upgrade primary disk | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 9.18 | No | | Upgrade to 4 TB SSD | USD 13.77 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### Sixth Drive Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 18.36 | No | | Upgrade to /27 (30 IPs) | USD 27.54 | No | | Upgrade to /26 (62 IPs) | USD 59.67 | No | | Upgrade to /25 (126 IPs) | USD 110.16 | No | | Upgrade to /24 (254 IPs) | USD 201.96 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 45.90 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | Yes | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ### Transit 40 02 Select the dual Intel Gold 6430 variant of the 40 Gbps configuration. Its listed resources include 64 GB of DDR4 memory, 1 TB of NVMe storage, unmetered traffic and five IP addresses in a /29 allocation. Configuration ID: transit-40-02. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 2936.65. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 2936.65; displayed effective monthly base: USD 2936.65. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Gold 6430 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 40 GBPS | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 2936.65 | USD 2936.65 | | 3 months | USD 2642.99 | USD 7928.96 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 91.80 | No | | Upgrade to 256 GB DDR4 | USD 183.60 | No | | Upgrade to 512 GB DDR4 | USD 367.20 | No | | Upgrade to 768 GB DDR4 | USD 1101.59 | No | | Upgrade to 1024 GB DDR4 | USD 275.40 | No | ##### Upgrade primary disk | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 2 TB SSD | USD 9.18 | No | | Upgrade to 4 TB SSD | USD 13.77 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### Sixth Drive Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 9.18 | No | | Add 2 TB SSD | USD 18.36 | No | | Add 4 TB SSD | USD 27.54 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 18.36 | No | | Upgrade to /27 (30 IPs) | USD 27.54 | No | | Upgrade to /26 (62 IPs) | USD 59.67 | No | | Upgrade to /25 (126 IPs) | USD 110.16 | No | | Upgrade to /24 (254 IPs) | USD 201.96 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 45.90 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | Yes | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ## Service questions ### Will every connection reach the listed port speed? No end-to-end transfer rate is guaranteed by a port specification. The remote connection, route, storage, software and protocol also determine actual throughput. ### How do the Transit 40 variants differ? Compare the CPU foundation and full hardware specification. The listed network port is the same class, but compute requirements can favour one variant. ### Does unmetered traffic mean every use is permitted? No. It describes the listed traffic model. Acceptable-use requirements and the need for authorised content and activity still apply. ### Can extra drives help a distribution service? They can provide capacity for content or working data. The effect on throughput depends on the storage layout and application, so benchmark a representative workload. ### Should I select Transit 40 just for a normal website? Compare your measured traffic and application needs first. A smaller hosting or compute configuration may fit; a large port does not correct inefficient application code. ### Are the port's bandwidth and burst behaviour guaranteed? The plan lists a 40 Gbps port and unmetered traffic. Confirm dedicated-capacity terms, fair-use conditions and any burst policy separately; there is no automatic permission to exceed the listed interface. ### What is included for IP addressing? The plan table lists five IPs in a /29 allocation. Additional blocks are optional. Confirm any IPv6 subnet and usable allocation with the operator. ### Will a dashboard show live traffic statistics? Agree traffic telemetry, metric retention and monitoring access for the delivered service. Include the application measurements you need in the technical brief. ### What should I confirm about protection and recovery? Agree baseline network protection, root or administrator credentials and secured IPMI or equivalent access. A high-bandwidth plan does not establish those operational controls on its own. ## Relevant guides - [Bandwidth, port speed and transfer: read the full picture](https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/index.txt): Estimate the data your project moves and understand why a larger port is only one part of network performance. - [Size a transfer with latency, concurrency and throughput measurements](https://swissoctet.com/insights/size-throughput-with-bandwidth-delay/index.txt): Build a repeatable transfer model using payload volume, delivery windows and round-trip time, then test it without confusing a port label with useful throughput. - [Plan a 40, 100 or 200 Gbps origin as a complete system](https://swissoctet.com/insights/plan-40-100-200-gbps/index.txt): Translate large port classes into storage, CPU, concurrency and operational questions before selecting a high-volume distribution configuration. - [Build monitoring that leads to a useful incident response](https://swissoctet.com/insights/monitoring-incident-response-playbook/index.txt): Connect application symptoms, actionable alerts and a small response playbook so that an operator can make clear decisions when a service degrades. - [Separate your public web edge from the application](https://swissoctet.com/insights/separate-the-web-edge-from-the-app/index.txt): Give the web server, reverse proxy and application distinct responsibilities, with deliberate origin access, TLS, request limits and an incident path. --- # Transit 100 > A Swiss dedicated configuration centred on a listed 100 Gbps port. Transit 100 brings a Xeon Gold foundation and configurable memory and storage to demanding, authorised data-distribution workloads. Canonical human page: https://swissoctet.com/services/transit-100/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. 100 Gbps port configurations for demanding content distribution and network workloads. ## Starting configuration Starting configuration: Transit 100 01 (transit-100-01); USD 7343.00 effective monthly base on the shortest available 1-month term; USD 7343.00 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon ® Gold 6134 | | RAM | 128 GB DDR4 | | STORAGE | 1 TB SSD | | PORT SPEED | 100 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | ## Service capabilities ### A defined 100 Gbps port The base configuration lists the high-speed port explicitly. Plan the application and storage pipeline around that interface without assuming an end-to-end rate. ### A Xeon Gold compute foundation The CPU and memory specifications remain visible beside the network. Account for request processing, encryption and application work when sizing the environment. ### Storage choices for the working set Select supported primary or additional SSD capacity for served content and active data. Capacity and achievable read rates remain different considerations. ### An unmetered traffic specification Transit 100 lists unmetered traffic. Review the server, IP and software choices as part of the same network-intensive deployment. ## Example workloads ### Large distribution origins Prepare a Swiss origin for content you are authorised to distribute, with a tested application and storage design. ### Bulk project-data delivery Serve substantial exports or research datasets to capable receivers while controlling access to private material. ### Measured network-intensive services Choose this class of port when workload measurement justifies it and the rest of the stack can support the traffic. ## A closer look ### High network capacity begins with measurement Estimate concurrent transfers, request sizes and the amount of data the application must read or generate. Then test the storage and software path with representative traffic. A high-speed port can be valuable, but it cannot make a receiver or a slow application consume data faster than they are able. ### Keep the storage specification in view Transit 100 lists SSD storage in its base configuration. Choose additional capacity where the project requires it and define how the data is organised and recovered. Do not infer NVMe storage or a particular disk layout from the network tier; read the actual hardware and selected options. ### Separate public delivery from private operations A distribution service can have a public data path and a tightly controlled management path. Restrict administrator interfaces, protect publishing credentials and review what your applications log. Keep backups for content and configuration so the service can be rebuilt without exposing private access. ### Define the network terms before scheduling a move The Transit 100 plan lists a physical server, unmetered traffic and five IPs in a /29 allocation. Confirm any IPv6 subnet, baseline protection and recovery console before delivery. Dedicated-capacity commitments, burst use and traffic telemetry need separate operating terms. Keep your monitoring and application benchmark requirements part of the technical brief. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Transit 100 01 A dedicated configuration built around a 100 Gbps port and unmetered traffic. Dual Xeon Gold 6134 processors, 128 GB of DDR4 memory and a 1 TB SSD provide the compute and storage allocation. Configuration ID: transit-100-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 7343.00. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 7343.00; displayed effective monthly base: USD 7343.00. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Xeon ® Gold 6134 | | RAM | 128 GB DDR4 | | STORAGE | 1 TB SSD | | PORT SPEED | 100 Gbps | | BANDWIDTH | UNMETERED | | IPS | 5 IP /29 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 7343.00 | USD 7343.00 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 137.70 | No | | Upgrade to 256 GB DDR4 | USD 275.40 | No | | Upgrade to 512 GB DDR4 | USD 550.79 | No | | Upgrade to 1024 GB DDR4 | USD 917.99 | No | ##### Primary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 1 TB SSD | USD 13.77 | No | | Upgrade to 2 TB SSD | USD 22.95 | No | | Upgrade to 4 TB SSD | USD 36.72 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 36.72 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 36.72 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 36.72 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 36.72 | No | ##### Sixth Drive Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 22.95 | No | | Add 4 TB SSD | USD 36.72 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 32.13 | No | | Upgrade to /26 (62 IPs) | USD 64.26 | No | | Upgrade to /25 (126 IPs) | USD 128.52 | No | | Upgrade to /24 (254 IPs) | USD 201.96 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 59.67 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Debian 10.X Minimal stable (64 Bit) | USD 0.00 | Yes | | Debian 10.X Stable (64 Bit) | USD 0.00 | No | | Debian 9.X Minimal stable (64 Bit) | USD 0.00 | No | | Debian 9.X Stable (64 Bit) | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 18.04 LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 16.04 LTS (64 Bit) | USD 0.00 | No | | Centos 8.X (64 Bit) | USD 0.00 | No | | Centos 7.X (64 Bit) | USD 0.00 | No | | Centos 6.X (64 Bit) | USD 0.00 | No | | Proxmox 7.0 Stable (64 Bit) | USD 0.00 | No | | Proxmox 6.0 Stable (64 Bit) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Custom (Please Open Ticket) | Operator quote required; not assumed free | No | ## Service questions ### Does the 100 Gbps label describe guaranteed application throughput? It describes the listed port specification. Actual throughput depends on storage, CPU, application behaviour, protocol, route and the receiving side. ### Does the base server use NVMe storage? The Transit 100 base specification lists SSD storage. Review the plan and option labels directly rather than assuming a technology from the network tier. ### Can I increase RAM and disk capacity? The configurator includes RAM and disk choices. Check the resulting capacity and price in the final summary and choose them for a measured workload. ### Do I need a large IPv4 block? Only if your network design requires it. Additional address allocations are optional and should be selected separately from port speed. ### What should I validate before moving a distribution service? Test representative transfers, monitor resource limits, verify receiver performance and keep a rollback plan. Confirm content rights and protect administrative access. ### Does the catalogue guarantee dedicated bandwidth or bursting? It lists a 100 Gbps port and unmetered traffic. Dedicated-throughput commitments, fair use and burst handling require operator confirmation and documented terms. ### Which IP addresses are included? The plan lists five IPs in a /29 allocation, with optional additional blocks. Confirm IPv6 and usable allocation before designing the network. ### Is real-time traffic monitoring available? Confirm the monitoring interface, available metrics and retention for the selected service. Include application-side measurements in your monitoring plan. ### How are server administration and network protection delivered? Confirm root or administrator credentials, secure IPMI or equivalent recovery access, and the baseline protection scope before a real order. ## Relevant guides - [Bandwidth, port speed and transfer: read the full picture](https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/index.txt): Estimate the data your project moves and understand why a larger port is only one part of network performance. - [Size a transfer with latency, concurrency and throughput measurements](https://swissoctet.com/insights/size-throughput-with-bandwidth-delay/index.txt): Build a repeatable transfer model using payload volume, delivery windows and round-trip time, then test it without confusing a port label with useful throughput. - [Plan a 40, 100 or 200 Gbps origin as a complete system](https://swissoctet.com/insights/plan-40-100-200-gbps/index.txt): Translate large port classes into storage, CPU, concurrency and operational questions before selecting a high-volume distribution configuration. --- # Transit 200 > A dedicated Swiss configuration for a different scale of data movement. Transit 200 combines a listed 200 Gbps port with a dual Gold 6430 foundation, primary NVMe storage and configurable server resources. Canonical human page: https://swissoctet.com/services/transit-200/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. 200 Gbps port configurations for projects operating at a different network scale. ## Starting configuration Starting configuration: Transit 200 01 (transit-200-01); USD 13768.93 effective monthly base on the shortest available 1-month term; USD 13768.93 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Gold 6430 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 200 GBPS | | BANDWIDTH | UNMETERED | | IPS | 5 | ## Service capabilities ### A listed 200 Gbps interface Start from the highest port class in the SwissOctet catalogue. Validate the complete data path before treating the interface capacity as usable application throughput. ### Compute around the network The dual Gold 6430 foundation supports a physical application environment. Review memory and CPU requirements for the processing attached to each transfer. ### Primary NVMe and extra capacity The base plan lists NVMe storage. Additional SSD-drive options can expand the data layout, with their technology and capacity described separately. ### Configuration beyond the headline Review unmetered traffic, IPv4 allocation, operating-system choices and optional software. The final server specification matters as much as its port class. ## Example workloads ### Large-scale content origins Design an authorised distribution environment with enough compute, storage and receiver capacity for substantial concurrent traffic. ### High-volume dataset workflows Prepare bulk movement of your own data where the network design and receiving systems justify a very large port. ### Specialised network applications Evaluate the configuration for a measured workload whose application pipeline can make practical use of this interface class. ## A closer look ### At this scale, the whole path matters The port is only one stage in the delivery chain. Data may need to be read, transformed, encrypted and sent to receivers across several networks. Measure those stages, identify the slowest one and design for realistic concurrency. No universal throughput or latency result is implied by the port specification. ### Build the server around actual data behaviour Choose memory for the active working set and storage for the content or dataset. The base NVMe specification and additional SSD options are distinct, so confirm the layout you intend to use. Plan independent recovery for data and configuration before introducing a high-volume service. ### Give a large deployment clear operating boundaries Define who can publish data, administer the server and change the application. Restrict management access, monitor resource use and document acceptable usage for your customers. Swiss offshore hosting supports a specific location choice; privacy also depends on those operational decisions and the data your software exposes. ### Turn the port class into an agreed deployment Transit 200 lists bare-metal hardware, unmetered traffic and five IPs. Confirm address usability, IPv6, protection and a secured recovery console before delivery. A dedicated-network agreement, burst handling and a traffic-monitoring interface are operational details requiring validation. Keep the application test, management boundary and migration window in the same deployment brief. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Transit 200 01 The 200 Gbps network configuration combines unmetered traffic with dual Intel Gold 6430 processors, 64 GB of DDR4 memory and a 1 TB NVMe drive. The listed allocation includes five IP addresses. Configuration ID: transit-200-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 13768.93. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 13768.93; displayed effective monthly base: USD 13768.93. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | SYSTEM | BARE METAL | | CPU | Dual Intel Gold 6430 | | RAM | 64GB DDR4 | | STORAGE | 1TB NVMe | | PORT SPEED | 200 GBPS | | BANDWIDTH | UNMETERED | | IPS | 5 | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 13768.93 | USD 13768.93 | | 3 months | USD 13768.93 | USD 41306.80 | | 6 months | USD 13768.93 | USD 82613.59 | | 12 months | USD 12392.04 | USD 148704.47 | | 18 months | USD 12392.04 | USD 223056.70 | #### Plan-specific available choices ##### Memory configuration | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Upgrade to 128 GB DDR4 | USD 137.70 | No | | Upgrade to 256 GB DDR4 | USD 275.40 | No | | Upgrade to 512 GB DDR4 | USD 504.89 | No | | Upgrade to 1024 GB DDR4 | USD 872.09 | No | ##### Secondary Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 27.54 | No | | Add 4 TB SSD | USD 41.31 | No | | Add 8 TB SSD | USD 55.08 | No | ##### Third Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 27.54 | No | | Add 4 TB SSD | USD 41.31 | No | | Add 8 TB SSD | USD 55.08 | No | ##### Fourth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 27.54 | No | | Add 4 TB SSD | USD 41.31 | No | | Add 8 TB SSD | USD 55.08 | No | ##### Fifth Disk Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 27.54 | No | | Add 4 TB SSD | USD 41.31 | No | | Add 8 TB SSD | USD 55.08 | No | ##### Sixth Drive Upgrade | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Keep the base configuration | USD 0.00 | Yes | | Add 1 TB SSD | USD 13.77 | No | | Add 2 TB SSD | USD 27.54 | No | | Add 4 TB SSD | USD 41.31 | No | | Add 8 TB SSD | USD 55.08 | No | ##### IPv4 allocation | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Base IPv4 allocation | USD 0.00 | Yes | | Upgrade to /28 (14 IPs) | USD 20.20 | No | | Upgrade to /27 (30 IPs) | USD 40.39 | No | | Upgrade to /26 (62 IPs) | USD 80.78 | No | | Upgrade to /25 (126 IPs) | USD 143.21 | No | | Upgrade to /24 (254 IPs) | USD 286.41 | No | ##### Software | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | No additional software | USD 0.00 | Yes | | Windows Server 2016 license | USD 36.72 | No | | cPanel/WHM (100 Domains) | USD 82.62 | No | ##### Operating system image | Choice | Listed monthly add-on price | Default for this plan | | --- | --- | --- | | Alma Linux 9 | USD 0.00 | Yes | | Alma Linux 8 | USD 0.00 | No | | Debian 12.X Minimal stable (64 Bit) | USD 0.00 | No | | Debian 11.X Minimal stable (64 Bit) | USD 0.00 | No | | FreeBSD 14 | USD 0.00 | No | | FreeBSD 13 | USD 0.00 | No | | Kali Linux 2024 | USD 0.00 | No | | Microsoft Windows 10 PRO (Trial) | USD 0.00 | No | | Microsoft Windows 11 PRO (Trial) | USD 0.00 | No | | Microsoft Windows 2016 (Trial) | USD 0.00 | No | | Microsoft Windows 2019 (Trial) | USD 0.00 | No | | Microsoft Windows 2022 (Trial) | USD 0.00 | No | | Microsoft Windows 2025 (Trial) | USD 0.00 | No | | Proxmox 8 | USD 0.00 | No | | Ubuntu 20.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 22.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 23.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Ubuntu 24.04 Minimal LTS (64 Bit) | USD 0.00 | No | | Rocky Linux 8 | USD 0.00 | No | | Rocky Linux 9 | USD 0.00 | No | | Fedora Server | USD 0.00 | No | ## Service questions ### When should I consider Transit 200? When measured network requirements justify this port class and the storage, application and receiving systems can support it. Compare smaller Transit configurations as well. ### Is 200 Gbps guaranteed for each transfer? No. The catalogue lists a server-port specification. Individual and aggregate transfer rates depend on the complete hardware, software and network path. ### Are extra drives also NVMe? The base plan lists NVMe; additional-drive labels describe SSD choices separately. Review the selected storage rather than applying the base-disk description to every drive. ### Does the port class include a particular uptime commitment? No uptime or service-level commitment is established by the port label. Availability and support terms must be confirmed separately for the actual service. ### What is the priority before production use? Validate a representative workload, secure management access and test recovery. Plan monitoring and a rollback path before sending production traffic to the environment. ### Are dedicated bandwidth and traffic bursts part of the quote? The listed specification is a 200 Gbps port with unmetered traffic. Confirm dedicated-capacity commitments, fair-use terms and burst policy separately; no additional throughput is implied. ### What addressing can I plan around? The plan lists five IPs. Additional blocks are optional; usable allocation and an IPv6 subnet require confirmation for the actual deployment. ### Will I be able to inspect live bandwidth statistics? Confirm available telemetry, dashboard access and metric retention for the selected service. Include the measurements needed to validate application behaviour and network use. ### How do I manage and recover the physical server? Confirm root or administrator credentials, secured IPMI or equivalent access and baseline network protection. Test the agreed recovery path before depending on the environment. ## Relevant guides - [Bandwidth, port speed and transfer: read the full picture](https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/index.txt): Estimate the data your project moves and understand why a larger port is only one part of network performance. - [Plan a 40, 100 or 200 Gbps origin as a complete system](https://swissoctet.com/insights/plan-40-100-200-gbps/index.txt): Translate large port classes into storage, CPU, concurrency and operational questions before selecting a high-volume distribution configuration. --- # Shield VPN > A Swiss VPN connection for one device. Shield lists OpenVPN, AES-256 encryption and unlimited traffic for users who want a defined Swiss connection point with a simple configuration. Canonical human page: https://swissoctet.com/services/shield/ SwissOctet public catalogue. Currency: USD. Location: Switzerland / CH. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. A Swiss OpenVPN configuration for one device, with AES-256 encryption and unlimited traffic. ## Starting configuration Starting configuration: Shield VPN 01 (shield-01); USD 4.59 effective monthly base on the shortest available 1-month term; USD 4.59 base charge for that term. Add-ons and applicable tax are separate. | Starting-plan specification | Listed value | | --- | --- | | Devices | 1 | | Traffic | Unlimited | | VPN Type | OpenVPN | | Encryption | AES-256 Encryption | ## Service capabilities ### A Swiss connection point This catalogue offers Shield only in Switzerland. The location is explicit rather than one choice hidden inside a broad list of regions. ### OpenVPN as the protocol The plan specifies OpenVPN. Use a compatible client and keep its configuration and connection credentials in a private place. ### Listed AES-256 encryption The encryption specification applies to the VPN connection. Applications, account access and the device itself still need their own security controls. ### A clear one-device allowance The plan lists one device and unlimited traffic. Check that allowance against how you intend to use the connection before ordering. ## Example workloads ### A Swiss browsing connection Use a compatible device with a defined Swiss VPN connection point, while keeping browser and account privacy settings under your control. ### Connectivity while travelling Prepare a consistent VPN configuration for your device and verify the applications you need through the connection. ### An encrypted network path Add a VPN connection to your own device-security plan without relying on it to secure every application or account. ## A closer look ### Know what the connection covers Shield provides a VPN configuration, not a complete privacy system. The listed protocol and encryption describe the connection. Websites can still recognise signed-in accounts, applications can disclose data and a compromised device remains a problem. Keep the device updated and use encrypted application connections. ### Make sure the client fits your device Check that your device supports a compatible OpenVPN client before purchasing. Protect the configuration, review the client's routing settings and test the applications you use. The plan's one-device allowance should be part of the decision if you want simultaneous access from several devices. ### No-KYC is a collection choice, not an invisibility claim The SwissOctet order flow is designed without identity-document verification. This limits what is requested at purchase, but it does not establish a zero-logs policy or absolute anonymity. Crypto transactions and account activity can carry identifying traces; choose and operate the service with a realistic privacy model. ### Check routing and application behaviour The OpenVPN profile determines which traffic enters the tunnel. Review full or split routing, DNS and client reconnect behaviour, then test the applications you use. Encryption and routing add overhead, while the route to each destination affects performance. Streaming access, P2P permission, inbound ports, firewall rules and data-retention practices require their own documented operating terms. ## Configurations and billing Base prices exclude separately selected add-ons. The actual configuration total, availability, delivery, licences and any applicable tax are confirmed before a real order. ### Shield VPN 01 An OpenVPN configuration for one device, using AES-256 encryption and a Swiss location. The catalogue lists unlimited traffic and a one-month billing period. Configuration ID: shield-01. Location: Switzerland / CH. Availability: confirm availability on the final quote. Nominal monthly base rate before billing-period pricing: USD 4.59. This rate is not a separate payable invoice total. Shortest available billing term: 1 month. Base charge for this term: USD 4.59; displayed effective monthly base: USD 4.59. Selected add-ons and applicable tax are separate. | Specification | Listed value | | --- | --- | | Devices | 1 | | Traffic | Unlimited | | VPN Type | OpenVPN | | Encryption | AES-256 Encryption | #### Available billing periods | Duration | Displayed effective monthly base | Total base for period | | --- | --- | --- | | 1 month | USD 4.59 | USD 4.59 | No paid add-on groups are listed for this family. ## Service questions ### How many devices does Shield include? The listed plan allowance is one device. Do not assume unlimited simultaneous connections from the unlimited-traffic specification. ### Which VPN protocol is listed? Shield specifies OpenVPN. Check that a compatible client is available for your device and keep its configuration private. ### Does a VPN make every activity anonymous? No. Accounts, cookies, applications, payments and device behaviour can reveal information. A VPN connection is one component of a privacy approach. ### Does SwissOctet claim a zero-logs VPN? No zero-logs guarantee is made here. Logging practices, retention and operational terms require a documented policy for the actual service. ### Is this the same as hosting a server or website? No. Shield is a VPN configuration for device connectivity. Compare the compute or hosting families if you need an environment to run applications. ### Are WireGuard, IKEv2 or several countries included? The current Shield catalogue lists OpenVPN in Switzerland. It does not include alternative protocols or additional locations. ### Can I rely on the VPN to unblock a streaming service? No access guarantee is made. Destination services can apply their own region and VPN rules, and connection performance depends on the route and device. ### What should I confirm for P2P or inbound connections? Confirm acceptable use, NAT or firewall behaviour and any port-forwarding support with the operator. Unlimited traffic does not establish unrestricted P2P permission or inbound access. ### What payment and cancellation terms apply? Confirm the operator’s identity, availability, delivery timeframe, applicable tax, renewal, cancellation and refund terms before sending funds. The fixed-address checkout provides a browser quote with complete transfer instructions; it does not issue a server invoice or confirm an accepted order. Payment verification and service delivery remain separate backend operations. ## Relevant guides - [Crypto checkout and the limits of payment privacy](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/index.txt): Understand the asset, network and confirmation journey, and protect the information that connects your project to a payment. - [No KYC and privacy: understand the difference](https://swissoctet.com/insights/no-kyc-is-not-anonymity/index.txt): Document-free onboarding addresses one collection point. Understand the other records, access paths and payment traces around a hosted project. - [Choose the asset and network before preparing a crypto payment](https://swissoctet.com/insights/choose-crypto-asset-network/index.txt): Read a payment route as a complete asset-and-network pair, then verify invoice instructions, token identity and the amount delivered before authorising a transfer. - [Choose a traffic path: server, tunnel or proxy](https://swissoctet.com/insights/choose-a-server-tunnel-or-proxy/index.txt): Understand what a VPS, VPN and proxy each change, then select routing, protocols and operating responsibilities from the connection you actually need. - [Plan addresses and DNS as parts of your deployment](https://swissoctet.com/insights/plan-addresses-and-dns-for-deployment/index.txt): Separate public, private, static and dedicated addresses, then map forward DNS, reverse DNS and TLS to the parties that can configure them. --- # How to choose a VPS without guessing > Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. Canonical human page: https://swissoctet.com/insights/choose-a-vps-by-workload/ SwissOctet Editorial. Topic: compute. Level: Foundation. Reading time: 4 minutes. ## Direct answer Choose a VPS from the resources your application actually needs: memory for persistent services and concurrency, CPU for the work it can execute, and storage and transfer for its data. Keep enough headroom and measure the delivered environment. ## Start with the work the machine will do A VPS purchase gets easier when you describe the application before choosing the plan. List the processes you expect to run: a web application, a database, background workers, monitoring and perhaps a control panel. Note which are always active and which only run occasionally. A quiet static website and a database with many simultaneous users can have very different needs even when their visitor counts look similar. If you already run the project, record normal usage and busy periods. CPU load, memory pressure, disk growth and transfer volume give you a starting point. For a new project, begin with an explicit estimate and plan to measure it after launch. An estimate you can revise is more useful than a large machine chosen without a reason. ## Memory often decides the practical starting point Count the memory required by the operating system and every persistent service, then leave room for real traffic. A database cache or a build process can change the picture quickly. If the machine spends time swapping or terminating processes under pressure, adding more CPU will not resolve the underlying shortage. CPU specifications deserve a separate reading. A virtual core is a resource presented to the guest environment; the processor model and the provider's allocation policy influence the result. KVM provides a virtual machine with its own virtual hardware, but the word KVM by itself is not a guaranteed benchmark. Compare the actual configuration and test your own application when the service becomes available. ## Budget the data that accumulates quietly Storage includes more than the application directory. Operating system packages, logs, database indexes, uploaded files, temporary exports and deployment artefacts all consume capacity. Leave headroom for updates and maintenance tasks, and decide how long each kind of data should remain. Logs that grow without a retention policy can fill even a generous disk. Separate capacity from responsiveness. An NVMe configuration may be relevant when disk access is a bottleneck, while a storage-oriented product fits large archives. Neither label replaces a backup plan. Confirm whether an optional backup includes the data you need and keep an independent recovery route for important services. ## Read the network and the extras as part of the machine A port rate and a monthly transfer allowance are different constraints. Include downloads, API traffic, replication and backups in your estimate. An optional faster port may help a bursty workload but does not automatically change the included transfer. Read the configuration after selecting extras, rather than relying only on the starting price. Choose an operating system you can maintain. Add management, extra addresses, software licences or backups only when they answer a real requirement. Record the recurring total and billing period so the decision remains clear when the initial setup is forgotten. ## A practical scenario: a website with background exports Imagine a small site with a database, two web workers and an export job. Normal page requests are light, but exports create temporary files and use more memory. The owner lists those processes separately, measures their behaviour with representative data and includes the export directory in the capacity estimate. The first shortlist is based on that combined workload, not on the visitor count or the cheapest starting price. During testing, allowing several exports to overlap delays ordinary requests. The owner limits export concurrency, observes the queue and repeats the test before buying more CPU. On a supported Linux setup, resource-control mechanisms can also help organise processes, but their settings must match the environment. If the constrained workload still needs more memory, an upgrade now answers a measured requirement rather than masking an unbounded task. The owner then adds an independent backup and checks restoration. This exercise illustrates a selection method, not a performance claim for a SwissOctet plan. Record the assumptions with the selected configuration and revisit them when the site adds a feature, a larger dataset or a different maintenance job. | Workload part | What to measure | Selection implication | | --- | --- | --- | | Web requests | Worker memory and response times | Allow room for normal concurrency | | Export job | Peak memory and temporary storage | Bound overlap and reserve capacity | | Recovery | Backup size and restore time | Plan independent storage and transfer | ## Prepare the first week before the first login After delivery, verify access, update the system and expose only the ports the project needs. Deploy a small working version before moving all data. Observe the resource use under representative traffic and compare it with your estimate. Keep the previous environment until you have checked the application and tested a restoration. The best starting VPS is the one that meets your measured needs with sensible headroom and a clear next step. Use the SwissOctet comparison to shortlist specifications, then prepare questions about availability, upgrades and operational responsibility before committing. ## Checklist - List all persistent services. - Estimate memory and busy-period CPU. - Include logs, exports and growth in storage. - Read port speed and monthly transfer separately. - Plan updates, backups and a migration rollback. ## Frequently asked questions ### Can I choose a VPS from visitor count alone? No. Request complexity, concurrent processes, data size and maintenance work can create very different resource demands. ### Does KVM describe a guaranteed performance level? No. It identifies the virtualisation technology. The processor, allocation and actual workload still matter. ### Which optional upgrade should I choose first? Choose the option that addresses the measured constraint. More CPU will not necessarily resolve memory pressure or storage waits. ## Primary sources - [KVM project: Kernel Virtual Machine](https://www.linux-kvm.org/page/Main_Page) - [Linux kernel: Control Group v2](https://docs.kernel.org/admin-guide/cgroup-v2.html) - [Linux kernel: Pressure Stall Information](https://docs.kernel.org/accounting/psi.html) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [DeskLink RDP](https://swissoctet.com/services/desklink/index.txt): A Windows workspace that follows you. Remote desktop access, configurable resources and a Swiss location. ## Related guides - [Size VPS CPU and memory from a real workload](https://swissoctet.com/insights/size-vps-cpu-and-memory/index.txt): Build a memory budget, inspect contention and separate one busy thread from work that can use several virtual cores. - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. --- # VPS or dedicated: choose the boundary that fits > Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. Canonical human page: https://swissoctet.com/insights/vps-or-dedicated-server/ SwissOctet Editorial. Topic: dedicated. Level: Foundation. Reading time: 4 minutes. ## Direct answer A VPS supplies a virtual environment; a dedicated server supplies a physical machine for the project. Choose dedicated hardware when its resource layout or physical boundary answers a real requirement, while budgeting administration and recovery separately. ## Begin with the isolation you actually need A VPS is a guest system running on a virtualisation platform. A dedicated server gives your project a physical machine rather than one virtual guest on a shared host. Both can provide administrative control inside your environment, and both require thoughtful maintenance. The useful question is not which sounds more powerful, but which boundary matches your application and responsibilities. A small application, development environment or independent service may fit comfortably in a VPS. A workload that needs substantial sustained compute, a particular hardware layout or several large guests may justify a dedicated system. Write down the requirement that changes the decision. If there is no clear requirement, the larger option may simply add cost and work. ## Compare the whole configuration Two servers with the same memory capacity can behave differently. Processor generation, core count, storage interface, disk layout and network profile all matter. A workload that depends on one busy thread may benefit from a different CPU choice than a renderer or parallel batch job. More cores alone do not ensure that every application becomes faster. On a dedicated configuration, also consider how the resources are arranged. Multiple drives may support separation between application data and local recovery tools, but local copies are still exposed to a machine-level incident. If you plan virtualisation, reserve capacity for the host and its maintenance operations rather than allocating every advertised gigabyte to guests. ## Account for administration and recovery A physical server does not make the software managed. Confirm who handles operating system updates, application troubleshooting, hardware incidents and recovery. The presence of a software option or a control panel is not a complete management agreement. Read the selected options and clarify the division of work before moving a production service. Ask how you regain access if a firewall change or system update goes wrong. Keep a private record of the authorised recovery path, the configuration and the information support needs. Avoid including credentials in ordinary tickets. An order reference, incident time and a careful symptom description usually make a more useful first report. ## Plan capacity and money over the same period Compare the recurring cost after adding the memory, storage, addresses and licences you need. Check the billing period and any minimum term on the specific plan. A plan that looks attractive per month can be a different decision when you need a short-lived environment or expect the workload to change soon. Dedicated capacity can make sense when you consistently use a substantial part of the machine. It may also simplify a particular architecture. It does not automatically create redundancy: one large server can still be a single point of failure. Where availability matters, decide whether you need a second environment and how traffic will move to it. ## A practical scenario: an application and a batch worker Consider a team running an interactive application beside a nightly data-processing job. They first measure the two workloads separately and together. If a VPS meets both needs with controlled job scheduling, a physical server may add little value. If the team needs a particular disk layout or enough capacity for several substantial guests, it can investigate a dedicated configuration with a clear reason for the move. The comparison includes the host's own memory needs, application storage, operating-system maintenance and an independent recovery copy. The team also asks how access is restored after a failed update and who handles hardware incidents. A larger machine changes available capacity, but it does not automatically make the application managed or create a second failure boundary. One physical machine remains one place where multiple services can fail together. Before cutover, the team restores representative data on the proposed destination and tests the application and batch job. It retains the previous environment until the new service and recovery process work. The example does not certify a configuration: it shows how a documented requirement, a complete recurring cost and a tested migration turn a product comparison into an operational decision. | Decision factor | VPS question | Dedicated question | | --- | --- | --- | | Workload fit | Do the virtual resources cover measured demand? | Does the physical layout answer a requirement? | | Administration | Which tasks are managed? | Who maintains the host and handles incidents? | | Recovery | Where is the independent copy? | What happens if the whole machine is unavailable? | ## Make the move a measured migration Deploy a representative test, check application response and verify your backup process before migrating real users. Estimate how long it takes to copy the dataset, and account for new changes written while the transfer runs. Keep a defined rollback point and communicate the maintenance window to the people affected. Choose a VPS when it is a clear fit; choose dedicated hardware when its physical boundary or resource layout answers a requirement. SwissOctet's dedicated ranges let you compare those details directly. Confirm availability and the delivery process before scheduling the final move. ## Checklist - Name the requirement for physical hardware. - Compare processor and disk layout, not memory alone. - Confirm management and recovery responsibilities. - Read the full recurring cost and minimum term. - Test the migration and retain a rollback route. ## Frequently asked questions ### Is dedicated hardware automatically redundant? No. One physical machine can still be a single point of failure. Redundancy needs a separate architecture and recovery plan. ### Does a control panel mean the whole server is managed? No. Confirm the exact management responsibilities, update process and recovery arrangements. ### When should I move beyond a VPS? When measured capacity, a hardware requirement or the desired resource layout justifies the move, and you can operate the destination. ## Primary sources - [KVM project: Kernel Virtual Machine](https://www.linux-kvm.org/page/Main_Page) - [PostgreSQL: Backup and Restore](https://www.postgresql.org/docs/current/backup.html) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. - [Metal EPYC](https://swissoctet.com/services/metal-epyc/index.txt): AMD-powered dedicated hardware for parallel workloads and serious compute. ## Related guides - [Build a GPU VRAM budget before choosing hardware](https://swissoctet.com/insights/gpu-vram-budget-for-real-workloads/index.txt): Account for weights, activations, caches and temporary buffers, then test the peak workload rather than the model file alone. - [A dedicated-server migration runbook that protects the data](https://swissoctet.com/insights/dedicated-server-migration-runbook/index.txt): Rehearse the move, establish a consistent data boundary and define what rollback means after the new system accepts writes. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. --- # When NVMe makes a difference to your application > Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. Canonical human page: https://swissoctet.com/insights/nvme-storage-when-it-matters/ SwissOctet Editorial. Topic: storage. Level: Foundation. Reading time: 4 minutes. ## Direct answer NVMe can help an I/O-sensitive workload, but first confirm that the application is waiting on storage. Compare representative latency, concurrency and application timings; a faster protocol label does not resolve every bottleneck. ## Storage performance is more than a transfer number When an application feels slow, it is tempting to buy faster storage immediately. First find out what the application is waiting for. A database looking up many small records has a different access pattern from a service reading one large archive. The useful measures include response time for individual operations, the number of operations completed and the sustained amount of data moved. NVMe is a storage protocol designed around solid-state media and efficient parallel I/O. It can offer advantages over older storage interfaces, especially where many operations happen at once. The protocol name describes a capability of the storage path; it is not a promise that every application request will finish faster. ## Find the work that reaches the disk Look at database queries, cache misses, upload processing, search indexes and build artefacts. If the application repeatedly waits for disk reads or durable writes, storage may be a meaningful constraint. If it waits on a remote API or spends most of its time doing CPU work, changing the storage medium may have little effect on the visible delay. Memory can change storage demand too. A working dataset that fits in an appropriate cache may avoid many reads. Better indexing or removing repeated queries may reduce I/O more effectively than a hardware upgrade. Treat software changes and resource choices as parts of the same investigation. ## Measure a representative workload A sequential copy test is useful for large files, but it does not describe every database workload. Capture the operation size, read-to-write mix and concurrency that represent the project. Keep datasets and test conditions comparable. A result from a mostly empty machine can differ from one produced during a busy deployment or backup window. Measure the application as well as the device. Request response times, background job duration and database wait metrics connect an infrastructure change with the user experience. Keep the test non-destructive and within your own authorised environment. Do not generate uncontrolled load against third-party services to create a comparison. ## Leave space for the maintenance work Choose enough capacity for growth and temporary operations. Database migrations, package updates, imports and compression tasks can need space beyond the final dataset size. An application that fills its disk during maintenance can fail even when the storage is fast. Establish limits and retention for logs and temporary files before they become the largest directories. Separate a boot disk from the capacity of a storage-oriented service when reading a specification. A small NVMe boot volume does not make a much larger storage area identical in performance. Read the description of each storage component and ask for clarification when the intended layout is unclear. ## A practical scenario: a report that reads many records Suppose a reporting application is slow when it reads a large set of small records. The team checks query plans, cache behaviour and I/O waits before choosing a different storage profile. It discovers repeated reads that can be reduced through indexing, then measures the remaining work. This separates a software improvement from the question of whether the storage path still limits the report. For a comparison, the team uses a representative dataset and records the read pattern, operation size and concurrency. It compares application completion time alongside storage latency rather than relying on one large-file copy. A synthetic test can help isolate a constraint, but the real report confirms whether the change benefits the workflow. Test conditions and background activity remain documented so another run is meaningful. The team also reserves space for temporary exports and verifies its independent backup. NVMe responsiveness does not replace those capacity and recovery decisions. If the report remains limited by an external service or one compute-heavy step, the storage upgrade may not change its duration. This scenario illustrates a method; it provides no benchmark or guaranteed speed for a SwissOctet configuration. | Question | Useful observation | Avoid this conclusion | | --- | --- | --- | | Is storage the constraint? | Application waits and I/O activity | Every slow request needs NVMe | | Does the change help? | Comparable report completion times | Sequential speed equals database speed | | Is the system recoverable? | A successful independent restore | Fast storage is a backup | ## Keep durability separate from speed Fast storage is not a backup, and multiple local drives are not an independent recovery location. Define which data must survive an accidental deletion, a bad deployment or loss of the machine. Store the required recovery keys separately and test the restore into an isolated environment. Use Pulse NVMe when its resources fit an I/O-sensitive project, or compare dedicated NVMe configurations when you also need a physical machine. For large archives, evaluate Vault Storage by its capacity and transfer profile. Choose from evidence about the workload, then verify the result after deployment rather than assuming a label resolves every bottleneck. ## Checklist - Identify disk waits in the application. - Separate latency, operations and throughput. - Test representative concurrency and data. - Reserve free space for migrations and exports. - Keep an independent, tested backup. ## Frequently asked questions ### Is NVMe always the best storage choice? Choose it when its capacity and performance profile fit the workload. Large archives and compute-bound applications may have other priorities. ### Can a copy test predict database response time? Not by itself. Databases may use different operation sizes, access patterns and synchronisation behaviour. ### Does NVMe make backups less important? No. Storage speed does not protect against deletion, a faulty deployment or loss of the environment. ## Primary sources - [NVM Express: Specification FAQ](https://nvmexpress.org/faq_category/specifications/) - [fio: Flexible I/O tester documentation](https://fio.readthedocs.io/en/latest/fio_doc.html) ## Related infrastructure - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [Vault Storage](https://swissoctet.com/services/vault/index.txt): Room for media, archives and growing datasets. A storage-focused Linux configuration. - [Metal Hyper](https://swissoctet.com/services/metal-hyper/index.txt): High-capacity dedicated configurations for intensive applications and larger deployments. ## Related guides - [Measure NVMe performance without misleading yourself](https://swissoctet.com/insights/nvme-benchmark-methodology/index.txt): Define the I/O pattern, control cache effects and inspect latency distributions before drawing an application conclusion from a disk test. - [Snapshots and backups: choose the failure you need to survive](https://swissoctet.com/insights/snapshots-backups-consistency/index.txt): Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection. - [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/index.txt): Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. --- # Crypto checkout and the limits of payment privacy > Understand the asset, network and confirmation journey, and protect the information that connects your project to a payment. Canonical human page: https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/ SwissOctet Editorial. Topic: crypto. Level: Foundation. Reading time: 4 minutes. ## Direct answer Match the invoice's asset, network, amount and receiving address, then check verified payment status and separate service-delivery confirmation. Crypto and no-document onboarding do not establish absolute anonymity. ## Treat the invoice as a complete set of instructions A crypto invoice needs more than an address. The asset, blockchain network, amount, receiving address and validity period belong together. A token with the same name can exist on several networks, and a wallet may display similar-looking options. Select the exact network named in a live invoice before preparing a transfer. Compare the wallet's final confirmation with the invoice, including the address and any fees. Copying an address reduces typing errors, but it does not verify that the rest of the transfer is correct. A QR code is a convenience for carrying information; it is not evidence that an invoice is genuine or that funds have arrived. ## Separate sending, confirmation and delivery Pressing send in a wallet begins a transaction process. A transaction must be observed and assessed by the receiving service, then associated with the correct order. Only that service can confirm the payment status for the purchase. A customer declaration or a local interface animation cannot establish receipt. Payment acceptance and server provisioning are also separate events. A confirmed payment does not necessarily mean that access is ready. Preserve the order reference and follow the actual status returned by the billing system. If a live invoice expires or the transfer amount differs, ask for the defined resolution process before sending an additional payment. ## A public ledger is still public Using crypto does not make a payment invisible. On public blockchains, transaction information can be visible to other observers. Bitcoin in particular records transfers publicly, and information shared elsewhere can link an address or transaction with a person. A fixed public receiving address also exposes a history of transfers to that destination. No-document KYC at a hosting service describes what that service asks you to provide. It does not determine what a wallet, exchange or other service already knows about you. Think about the complete path and the information you intentionally publish, rather than assuming one payment method protects every part of the relationship. ## Protect access, not just personal details An order's private access token can be more sensitive than its display reference. Keep recovery phrases, private keys, exchange credentials and server access outside support messages and screenshots. If you need help, start with the order reference, the selected asset and network, and a concise description of the issue. A transaction identifier can be useful for investigating a transfer, but it can also reveal payment information when shared publicly. Use the designated private support route for order details. Redact unrelated balances, names and other transactions from images before sharing them. ## A practical scenario: the same token on two networks Imagine a customer reviewing a USDT purchase while their wallet supports both TRON and Ethereum. The token name alone does not select the route. Before a live transfer, the customer compares the invoice's network and receiving address with the wallet's final screen, along with the amount and fee. A familiar ticker or a previously used address is not enough to verify the whole instruction set. The customer keeps the order reference privately and waits for the billing service to associate a verified transaction with that order. A transaction appearing in a wallet and a service becoming ready are different events. If the network, asset or amount differs from the invoice, the customer follows the operator's reconciliation process rather than assuming that the interface can resolve the mismatch or sending another payment automatically. Review the complete checkout instructions: asset, network, exact amount, receiving address and expiry. Keep the client reference and exported record privately. A receiving address alone does not specify a payment, and a browser record does not prove receipt of funds. | Stage | What it establishes | What still needs confirmation | | --- | --- | --- | | Invoice review | Intended asset, network and amount | Whether the invoice is live and valid | | Wallet submission | A transfer was initiated | Verified receipt and order attribution | | Payment accepted | Backend payment evidence | Provisioning and delivery of access | ## Know the boundary of the current checkout The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. The fixed-address crypto checkout uses a public USD rate to calculate the exact amount for the selected asset and network, with a 25-minute payment window. This browser quote is not a server-issued invoice. Transaction attribution, payment confirmation and provisioning require the operator’s backend. ## Checklist - Review the complete payment instructions and expiry. - Match asset, network, amount and address. - Keep fees and expiry in view. - Wait for verified payment and provisioning statuses. - Never share a seed phrase, private key or order access token. ## Frequently asked questions ### What do I need before sending a crypto payment? Review the complete checkout instructions: asset, network, exact amount, receiving address and expiry. Keep the client reference and exported record privately. A receiving address alone does not specify a payment, and a browser record does not prove receipt of funds. ### Is a token name enough to select its network? No. Match the exact network and address specified by the live invoice. ### Does an on-chain transaction prove my server is ready? No. Payment verification, order attribution and provisioning are separate steps. ## Primary sources - [Bitcoin: Protect your privacy](https://bitcoin.org/en/protect-your-privacy) - [Ethereum: Transactions](https://ethereum.org/en/developers/docs/transactions/) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Shield VPN](https://swissoctet.com/services/shield/index.txt): A Swiss OpenVPN configuration for one device, with AES-256 encryption and unlimited traffic. - [Veil Onion](https://swissoctet.com/services/veil/index.txt): A hosting configuration built around onion services, with capacity adapted to your project. ## Related guides - [Choose the asset and network before preparing a crypto payment](https://swissoctet.com/insights/choose-crypto-asset-network/index.txt): Read a payment route as a complete asset-and-network pair, then verify invoice instructions, token identity and the amount delivered before authorising a transfer. - [From detected transaction to reconciled order: confirmations and reorgs](https://swissoctet.com/insights/confirmations-reorgs-order-reconciliation/index.txt): Design payment states around verified chain evidence, explicit acceptance rules and unambiguous order association rather than a browser claim that funds were sent. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. --- # Build a backup you can actually restore > Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. Canonical human page: https://swissoctet.com/insights/build-a-backup-you-can-restore/ SwissOctet Editorial. Topic: operations. Level: Applied. Reading time: 4 minutes. ## Direct answer Define acceptable data loss and recovery time, keep a consistent independent copy and test restoring the actual application in isolation. A completed backup job or integrity check alone does not prove that every dependency needed for recovery is present. ## Start with the recovery you need A backup plan starts with two practical questions: how much recent work could you lose, and how long could the service remain unavailable? Those answers determine the schedule, the data to include and the restoration method. A daily copy may fit a rarely changed website while leaving too large a gap for a busy application. List what makes the service work, not only its largest folder. Application data, database contents, configuration, uploaded files and the information needed to rebuild the environment may all matter. Keep a private inventory of dependencies and recovery keys. The backup should support a working system, not just produce an archive whose purpose is forgotten. ## Keep a copy outside the failure boundary A second directory on the same machine can help recover a mistaken edit, but it remains exposed to loss of that machine. Local snapshots can be valuable for quick rollback and still require an independent copy for broader incidents. Choose a separate recovery destination and decide which access should be able to read, write or remove the backup. If production credentials can delete every recovery copy, a compromised application account may defeat the whole strategy. Separate access where possible and protect the storage credentials. Encryption helps protect the stored content, but the recovery process also depends on retaining its key safely outside the damaged environment. ## Capture a consistent application state Copying open database files without an appropriate method can capture an unusable state. Use a backup approach supported by the application or database, and understand whether it requires a consistent snapshot, a logical export or a brief pause in writes. Coordinate related data so that an upload directory and its database references describe the same point in the workflow. Document exclusions deliberately. Caches and temporary build files may be reproducible; customer uploads usually are not. Review the list after adding a feature or moving a directory. A successful backup job cannot preserve a path that was never included. ## Test restoration in an isolated environment Restore representative data into a separate location and verify that it opens correctly. For an application, test the recovered service as well as the files. Disable outgoing email, scheduled jobs and external integrations in the test environment so the rehearsal does not act on real users or duplicate production tasks. Repository integrity checks and a restore test answer different questions. A tool can check stored structures and data while the application still needs missing configuration or a forgotten key. Record how long recovery takes, what manual steps are required and where the procedure needs improvement. Repeat the exercise after significant changes. ## A practical scenario: rehearse recovery before launch Consider an application with a database, user uploads and a small set of private configuration files. The owner creates a recovery inventory and chooses a database-supported consistency method. A separate backup destination stores the required copies, while the recovery key is kept outside the production machine. The first test begins with an empty isolated environment, so hidden dependencies cannot be borrowed from the working server. The owner restores the data and configuration, then checks login, a representative record and an uploaded file. Outgoing email, scheduled jobs and external actions remain disabled during the rehearsal. If the database starts but an upload path or secret is missing, the test has found a gap that a successful archive job would not reveal. The owner corrects the inventory and repeats the affected recovery check. Finally, the owner records the restoration time and the manual steps. The schedule and retention policy are compared with how much recent work could be lost and how long the service could remain unavailable. These are project-specific decisions rather than guarantees supplied by a storage label. A tested procedure makes an optional backup or a storage product useful as part of a broader recovery strategy. | Recovery evidence | What it checks | Remaining question | | --- | --- | --- | | Backup job completed | The job reported success | Were all required paths included? | | Repository integrity check | Stored structures or data checks | Does the application have every dependency? | | Isolated application restore | A representative recovery works | Does the observed time meet your objective? | ## Make failure visible and retention intentional A backup that stops silently is a future surprise. Monitor job completion, available capacity and the age of the latest usable recovery point. Keep enough history to recover from a problem discovered later, and understand how pruning affects that history. Review deletion operations carefully because retention mistakes can remove the only useful version. Read the scope of any backup option on your chosen SwissOctet service and confirm the restoration process. Vault Storage can be considered as a capacity component, but a storage product alone is not a complete recovery policy. Decide what you need to restore, keep the copy independent and prove the procedure before the service becomes critical. ## Checklist - Set acceptable data loss and recovery time. - Include databases, uploads and rebuild information. - Keep an independent copy and separate recovery keys. - Restore in isolation and test the application. - Monitor backup age, capacity and retention. ## Frequently asked questions ### Is a second directory on the same server an independent backup? No. It remains exposed to loss of that server, although it may help recover a local mistake. ### Does an integrity check replace a restore rehearsal? No. A valid repository may still omit configuration, keys or data required by the application. ### Why disable integrations during a restore test? To prevent the test environment from emailing real users, repeating jobs or triggering production actions. ## Primary sources - [restic: Restoring from backup](https://restic.readthedocs.io/en/stable/050_restore.html) - [restic: Working with repositories](https://restic.readthedocs.io/en/stable/045_working_with_repos.html) - [PostgreSQL: Backup and Restore](https://www.postgresql.org/docs/current/backup.html) ## Related infrastructure - [Vault Storage](https://swissoctet.com/services/vault/index.txt): Room for media, archives and growing datasets. A storage-focused Linux configuration. - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. ## Related guides - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. - [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/index.txt): Secure administration, expose only required services and establish updates and recovery without locking yourself out. --- # Bandwidth, port speed and transfer: read the full picture > Estimate the data your project moves and understand why a larger port is only one part of network performance. Canonical human page: https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/ SwissOctet Editorial. Topic: network. Level: Foundation. Reading time: 4 minutes. ## Direct answer Port speed is a connection rate; a transfer allowance is a volume over time. Estimate your traffic pattern, include replication and backups, and measure the complete route before assuming a larger port will improve the application. ## Distinguish the rate from the volume Network specifications often place two different measurements close together. A port rate in Mbps or Gbps describes how quickly data can move across that connection. A transfer allowance in GB or TB describes the amount included over a period. A large port and a large allowance solve different requirements, and you should compare both. Be careful with units when estimating downloads. Network rates are commonly expressed in bits per second; file sizes are commonly expressed in bytes. Eight bits make one byte. A simple conversion gives a theoretical starting point, while protocol overhead and the actual route reduce useful application throughput. Keep the estimate explicit rather than reading both numbers as equivalent. ## Estimate your workload before choosing a port For a file distribution service, begin with average file size and the number of downloads. For a web application, measure the data transferred per session or request. Include images, API responses and background work where relevant. Add replication, backups, software updates and administrative exports so the total reflects what the machine actually does. Then describe the timing. A steady workload and a short launch-day burst can move the same monthly volume while needing different peak rates. Track concurrency and expected destinations. A network profile should support the normal pattern with sensible headroom, not only a rare maximum that you cannot explain. ## Understand where throughput can be limited The server port is one component in an end-to-end path. A remote connection, storage read speed, encryption work or application worker limit can prevent the service from using its full rate. Network delay and packet loss can also affect TCP throughput. Adding port capacity will not automatically resolve a constraint elsewhere in that path. Test from representative destinations under controlled conditions. Record whether you used one connection or several, the duration and the size of the transfer. A single result without that context can be misleading. Use authorised endpoints and avoid saturation tests that disrupt other services. ## Read unmetered with the rest of the specification An unmetered plan presents no fixed monthly transfer quota in its listed specification. It still has a port profile, an operational policy and practical performance limits. It should not be interpreted as infinite speed or a guaranteed sustained rate to every receiving system. Ask about the actual service conditions when your workload depends on continuous high transfer. SwissOctet's Transit ranges present 40, 100 and 200 Gbps port profiles with unmetered transfer listed. Other ranges can use stated allowances or different port speeds. Compare the exact configuration and the selected options rather than assuming that every server in the catalogue has the same network terms. ## A practical scenario: distributing a large release Imagine a project distributing a twenty-gigabyte release to five hundred clients. Using decimal units, the downloads alone represent about ten terabytes before retries, other traffic and backups are considered. That volume says little about the peak rate unless the team also knows when clients download. A gradual rollout and a short simultaneous launch can move the same data while demanding very different connection capacity. The team measures how quickly its storage can supply the file and how the application handles concurrent transfers. It then tests from authorised endpoints in representative regions, recording duration, connection count and the route conditions. An iperf3 test can investigate the network path without measuring the file-serving application, while an application download checks the wider pipeline. Neither result should be presented without its conditions. If remote clients are the limiting component, a larger server port will not make those individual connections faster. If the existing server is genuinely constrained during the launch window, the team can compare higher-capacity profiles and their transfer terms. This is a hypothetical planning example, not a SwissOctet throughput promise. Keep the calculation, measured bottleneck and selected plan together so the decision can be reviewed as demand changes. | Measurement | What it describes | What it does not establish | | --- | --- | --- | | Monthly transfer estimate | Expected data volume | Required peak connection rate | | Network-path test | Throughput under stated conditions | Application file-serving performance | | Real download test | The complete serving pipeline | A universal future speed guarantee | ## Balance the machine and plan the operation A high-throughput service needs enough CPU, memory and storage performance to keep the network fed. Plan for concurrent connections, request processing and the security checks your application needs. Review address requirements and backup traffic together with the main workload so there are fewer surprises during deployment. Prepare a concise network brief with expected transfer, peak demand, audience locations and your preferred range. Confirm availability and any service commitments before arranging a migration. The useful goal is a balanced system that serves real users well, supported by measurements you can repeat as the project grows. ## Checklist - Read port rate and transfer allowance separately. - Convert bits and bytes carefully. - Include backups and replication in your estimate. - Measure representative routes and concurrency. - Balance CPU, storage and network before upgrading. ## Frequently asked questions ### Does a faster port increase a monthly transfer allowance? Not necessarily. Read the selected plan and upgrade terms; connection rate and included volume are separate. ### Does unmetered mean infinite speed? No. The port, application, receiving system and operating conditions still impose practical limits. ### Can an iperf3 result predict every user's download speed? No. It measures a particular path and test configuration. Real users and the application can introduce other constraints. ## Primary sources - [ESnet: Invoking iperf3](https://software.es.net/iperf/invoking.html) - [IETF RFC 6349: TCP Throughput Testing](https://www.rfc-editor.org/info/rfc6349/) ## Related infrastructure - [Transit 40](https://swissoctet.com/services/transit-40/index.txt): Dedicated configurations with a 40 Gbps port for bandwidth-intensive applications. - [Transit 100](https://swissoctet.com/services/transit-100/index.txt): 100 Gbps port configurations for demanding content distribution and network workloads. - [Transit 200](https://swissoctet.com/services/transit-200/index.txt): 200 Gbps port configurations for projects operating at a different network scale. ## Related guides - [Size a transfer with latency, concurrency and throughput measurements](https://swissoctet.com/insights/size-throughput-with-bandwidth-delay/index.txt): Build a repeatable transfer model using payload volume, delivery windows and round-trip time, then test it without confusing a port label with useful throughput. - [Plan a 40, 100 or 200 Gbps origin as a complete system](https://swissoctet.com/insights/plan-40-100-200-gbps/index.txt): Translate large port classes into storage, CPU, concurrency and operational questions before selecting a high-volume distribution configuration. - [Build monitoring that leads to a useful incident response](https://swissoctet.com/insights/monitoring-incident-response-playbook/index.txt): Connect application symptoms, actionable alerts and a small response playbook so that an operator can make clear decisions when a service degrades. --- # Swiss data residency: map the whole service > A Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment. Canonical human page: https://swissoctet.com/insights/swiss-data-residency-map/ SwissOctet Editorial. Topic: privacy. Level: Foundation. Reading time: 6 minutes. ## Direct answer Data residency describes where data is stored or processed. A Swiss server does not establish the location of backups, support systems, external integrations or every person with access; assess those components separately. ## Separate the machine location from the data journey A country label on a hosting plan answers a narrow question: where the listed configuration is located. Your application can still send information elsewhere. Error reporting, email delivery, payment processing, off-site backups and administrator access are part of the service even when they are absent from the infrastructure diagram. Treat the Swiss destination as one entry in a data map, rather than a conclusion about the complete project. Begin by naming the information you handle. A public documentation site, a customer portal and a private archive need different controls. Distinguish published content, personal information, authentication secrets and internal operational records. Record why each category exists and what would happen if it were disclosed, altered or lost. This makes later location decisions concrete instead of relying on the general appeal of a jurisdiction. ## Build a small processing register Follow one representative user action from the browser to storage. Note which system receives the request, what it writes and which other services are notified. Repeat the exercise for account creation, password recovery, uploads and support. You will often discover secondary copies in logs, email queues and diagnostic exports. Record these while the architecture is still simple enough to change. Use a register with a purpose, destination, access owner and retention decision for each component. You do not need an elaborate compliance tool to start. The useful property is that someone can explain every row and update it after a new integration. A diagram without backup locations or administrative access is incomplete for a residency decision. | Component | What to establish | Useful evidence | | --- | --- | --- | | Primary database | Hosting location and permitted access | Service specification and access policy | | Recovery copy | Destination, retention and deletion | Backup configuration and restore procedure | | Support export | Content and recipients | Redacted sample and support policy | | External integration | Information sent and processing terms | Integration configuration and provider documentation | ## Understand the responsibility that remains with you The Swiss Federal Data Protection and Information Commissioner explains that outsourcing processing does not remove the controller's responsibility for data protection. Its guidance covers selecting processors, issuing instructions and checking the handling of personal data. This is a reason to inspect the service relationship as well as the rack location. The exact obligations for your organisation depend on the applicable framework and the information involved. Where information may be disclosed across borders, use the relevant official guidance and obtain advice for decisions that need a legal assessment. Avoid declaring that a country name automatically makes the application compliant. Ask who the processors and sub-processors are, where processing occurs and what arrangements apply. Keep the answers with the project's operational documentation so the decision can be reviewed later. ## Reduce the information that needs a location decision Collect only what serves a defined purpose. A newsletter does not necessarily need a full postal address, and a troubleshooting report rarely needs an entire customer database. Removing unnecessary fields reduces exposure and simplifies retention. Keep secrets out of diagnostic tools, and consider whether aggregate measurements answer the operational question without reproducing individual records. Encryption can help protect particular copies, but identify who controls the keys and where decryption occurs. An application that must process readable data cannot be treated as if nobody can ever access it. Likewise, a pseudonymous identifier may still link records over time. Describe the implemented control precisely instead of using an encryption badge as a substitute for the processing map. ## A practical scenario: a small customer portal Imagine a portal hosted on a Swiss VPS, with an independent recovery copy and a third-party email service. The customer database stays on the VPS during normal operation, but password-reset messages and support notifications leave that machine. The team should record the minimum fields in those messages, the destination used for backups and the people allowed to export records. A sensible review might replace a full record in an error report with a random incident reference, shorten diagnostic retention and restrict backup access. These changes are useful regardless of the selected country. The example is a planning exercise, not a statement that SwissOctet includes these integrations or has verified a particular residency arrangement. ## Verify the map before making a public commitment Before promising a location to your users, compare the register with actual configuration and confirmed service terms. Test whether backup and deletion procedures work as expected. Review exports, monitoring agents and scheduled jobs, because they can introduce copies that nobody remembers during the initial purchase. Assign someone to approve new destinations and update the register when the architecture changes. SwissOctet presents Swiss configurations in its catalogue. The live operator's processing arrangements, support access and retention rules must be confirmed separately before a real order. Choose the infrastructure with that boundary in view: a clear Swiss location can support your architecture, while a complete and maintained data map supports the claims you make about it. ## Checklist - Classify the information handled by the project. - Map primary storage, backups, logs and integrations. - Identify processors, access owners and retention decisions. - Review official guidance for applicable cross-border questions. - Verify actual configuration before promising residency. ## Frequently asked questions ### Does a Swiss server mean every copy stays in Switzerland? No. Backup destinations, exports, support systems and integrations have their own data paths and must be checked separately. ### Does encryption remove the need to map processing? No. You still need to know where data and keys exist, who can decrypt it and what processing takes place. ### Does this guide certify a SwissOctet deployment? No. It provides a planning method. Live processing terms and implemented controls need confirmation for the specific service. ## Primary sources - [FDPIC: Data processing in the cloud](https://www.edoeb.admin.ch/en/data-processing-in-the-cloud) - [FDPIC: Outsourcing of data processing](https://www.edoeb.admin.ch/en/outsourcing-of-data-processing) - [FDPIC: Cross-border transfer of personal data](https://www.edoeb.admin.ch/en/cross-border-transfer-of-personal-data) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Vault Storage](https://swissoctet.com/services/vault/index.txt): Room for media, archives and growing datasets. A storage-focused Linux configuration. - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. ## Related guides - [No KYC and privacy: understand the difference](https://swissoctet.com/insights/no-kyc-is-not-anonymity/index.txt): Document-free onboarding addresses one collection point. Understand the other records, access paths and payment traces around a hosted project. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. --- # No KYC and privacy: understand the difference > Document-free onboarding addresses one collection point. Understand the other records, access paths and payment traces around a hosted project. Canonical human page: https://swissoctet.com/insights/no-kyc-is-not-anonymity/ SwissOctet Editorial. Topic: privacy. Level: Foundation. Reading time: 6 minutes. ## Direct answer No-document KYC means a service does not request identity documents in the described process. It does not establish absolute anonymity, zero logging or the absence of payment and operational records. ## Name the collection point precisely An identity-document requirement is one part of onboarding. Removing it means you do not hand over a passport scan or proof of address through that process. That can reduce a meaningful category of information, particularly when a document contains details unrelated to running a server. It does not tell you what other records the service needs or what other organisations know about the relationship. Ask a specific question instead of treating a label as a complete policy: which fields are required, why are they needed and how long are they kept? Distinguish browsing, preparing a selection, placing an order and requesting support. A service can require little information at one stage while creating operational records at another. Clear descriptions should preserve those differences. ## Privacy concerns the complete information lifecycle The NIST Privacy Framework considers privacy risk across the lifecycle of data, from collection to disposal. For a hosted project, this invites a wider view than an identity upload screen. Think about order records, contact messages, technical labels, access events and recovery copies. Each has a purpose and a retention decision, and each can create exposure if handled carelessly. Privacy and security overlap without being identical. A well-protected database can still contain unnecessary information or be retained longer than needed. Conversely, collecting less information does not make a weak administration password safe. Build a policy that reduces needless collection and an operational setup that protects the information that remains. Neither task is completed by choosing a single payment method. ## Look at the trail around the order A purchase may involve a wallet, an exchange, a receiving address and a transaction record. On public blockchains, observers can inspect transaction information. Bitcoin's official privacy guidance explains that addresses and transfers can be linked with information revealed elsewhere. A payment without a card form therefore should not be described as an invisible payment. Operational details matter too. A hostname can reveal a project name, a support screenshot can expose other accounts, and a copied log can include identifiers. Keep the distinction between public references and private access tokens clear. Share what is necessary to resolve an issue through the intended support channel, rather than posting a complete account or payment record publicly. | Statement | What it addresses | What it does not prove | | --- | --- | --- | | No identity-document upload | Document collection in the stated process | No other records exist | | Swiss location | The listed hosting destination | Absolute secrecy or legal immunity | | Crypto payment route | Supported asset and network | Untraceable payment | | Local shortlist | Storage of interface selections | Protection against access to your device | ## Use the current interface without over-reading it Public blockchains record transfers, and wallet or exchange providers can have their own records and identity checks. Fixed-address quotes and configuration details stay in this browser and can be exported. They are not authenticated account records. Crypto payments alone do not guarantee anonymity. A shared device changes the practical privacy boundary. Someone with access to that browser may see its saved choices or downloads. Clear selections when appropriate and manage exported files in a private location. Local storage should not be treated as a secure vault merely because it is outside a customer account. Protecting your endpoint remains part of protecting the project. ## A useful scenario: an independent developer Consider a developer choosing a VPS for a private prototype. They can compare resources without an identity upload, use a neutral technical hostname and keep credentials out of the project brief. They can also avoid including a real customer dataset in the initial deployment. These choices reduce unnecessary disclosure while preserving enough detail to obtain useful technical assistance. Before opening a live account or order, the developer should read the actual retention and support policies, confirm how access recovery works and understand the payment trail. This is more effective than requesting an absolute anonymity promise that has no implemented scope. The scenario is about deliberate information handling, not hiding unlawful activity or bypassing applicable responsibilities. ## Prefer bounded commitments you can evaluate A meaningful privacy statement identifies the data, purpose, access and retention involved. It should distinguish what is implemented today from what is planned. Claims about zero logs, encryption at rest or independently audited systems require their own evidence; the absence of a document upload does not establish them. The handling of official requests also needs a defined policy rather than an unconditional slogan. Choose infrastructure that fits the workload and evaluate its privacy arrangements with the same care as its specifications. Ask for less information where possible, explain what remains and keep sensitive access separate from ordinary correspondence. That approach gives you practical control over your choices while avoiding promises that a location or onboarding label cannot support. ## Checklist - Separate browsing, ordering and support data. - Read required fields and retention purposes. - Understand the public payment trail. - Keep credentials and access tokens out of messages. - Evaluate specific commitments rather than absolute labels. ## Frequently asked questions ### Does no KYC mean no data is stored? No. Document collection and operational records are separate matters. Ask what is stored at each stage and why. ### Are crypto payments automatically anonymous? No. Public transaction records and information held by wallets, exchanges or other services can create identifiable links. ### Can a country label guarantee non-disclosure? No. Hosting location does not prove an absolute confidentiality guarantee or determine every access and disclosure circumstance. ## Primary sources - [NIST Privacy Framework: Getting started](https://www.nist.gov/privacy-framework/getting-started-0) - [Bitcoin: Protect your privacy](https://bitcoin.org/en/protect-your-privacy) - [FDPIC: Data processing in the cloud](https://www.edoeb.admin.ch/en/data-processing-in-the-cloud) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Shield VPN](https://swissoctet.com/services/shield/index.txt): A Swiss OpenVPN configuration for one device, with AES-256 encryption and unlimited traffic. - [Veil Onion](https://swissoctet.com/services/veil/index.txt): A hosting configuration built around onion services, with capacity adapted to your project. ## Related guides - [Swiss data residency: map the whole service](https://swissoctet.com/insights/swiss-data-residency-map/index.txt): A Swiss server location is a starting point. Map application data, backups, support access and external services before making a residency commitment. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. --- # A practical threat model for your hosted project > Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. Canonical human page: https://swissoctet.com/insights/threat-model-a-hosted-project/ SwissOctet Editorial. Topic: operations. Level: Applied. Reading time: 6 minutes. ## Direct answer A useful threat model explains what you protect, who or what can affect it, where trust changes and how you will reduce and test the most important risks. Start with the actual project rather than a generic list of tools. ## Define a scope small enough to reason about Start with one working service: a customer portal, publishing site or internal application. Write down the components you operate and the external systems you rely on. A threat model should make assumptions visible, not suggest that every possible attack has been solved. Keep the first version small enough that the people deploying the application can explain it without a separate consultant interpreting the diagram. List the valuable outcomes and assets. These may include customer data, administration access, payment state, published content and the ability to restore service. Availability can be an asset even when the information is public. Decide which failures would be inconvenient and which would damage people or the organisation. That distinction helps you prioritise controls instead of treating every warning equally. ## Draw the places where trust changes OWASP's threat-model guidance uses data flows and trust boundaries to make a design understandable. For a small hosted application, draw the browser, web process, database, administrator, backup destination and external integrations. Mark the information moving between them. A request crossing from an untrusted client into a privileged server operation deserves explicit validation and authorisation. Do not assume that being inside the same machine makes every component equally trusted. A public upload process should not have the same permissions as database administration. A backup job may need read access without the ability to modify live application records. Separating those roles makes the effect of a compromised component easier to contain and the required permissions easier to review. ## Choose concrete failure scenarios Use a handful of plausible events to challenge the design. An attacker steals an administrator password; a user requests another user's record; an upload fills the disk; a deployment exposes a configuration file; a recovery copy cannot be restored. Describe the starting condition, the affected component and the consequence. A specific scenario is easier to test than a broad instruction to improve security. Include mistakes and legitimate workflow abuse as well as external intrusion. A retry may create two valuable operations, or two requests may race to change the same object. OWASP's business-logic guidance highlights these process assumptions. Check who is allowed to move a workflow into its next state and whether repeating or reordering a request changes the result unexpectedly. | Scenario | Control to investigate | Evidence to collect | | --- | --- | --- | | Stolen administration credential | Restricted access and a second factor where supported | An unauthorised login cannot complete | | Another user's object requested | Server-side object authorisation | An isolated test returns a denied result | | Disk exhausted by uploads | Size, quota and retention controls | A limit is enforced before service failure | | Duplicate workflow request | Idempotency and transaction boundaries | A repeated request creates one outcome | ## Prioritise by impact and a credible path For each scenario, record its potential impact and the conditions required for it to occur. Avoid pretending that a guessed numerical score is a precise probability. You can still distinguish an internet-exposed weak password from a highly conditional local event. Assign an owner and a practical next step to the important risks so the model creates work that someone can actually complete. Consider the information lifecycle as well as application compromise. A diagnostic export can disclose unnecessary data during otherwise normal operation. A retained account field may create exposure long after its purpose ends. Privacy review can therefore remove information or shorten retention, while security review restricts access to what remains. Both changes belong in the model when they protect the project. ## Test the controls in an authorised environment Create a staging environment with representative permissions and fabricated records. Test denied access, request limits, workflow retries and recovery. Do not use real customer data when synthetic data can demonstrate the behaviour. The objective is to verify the control, not to generate impressive attack traffic. Stay within systems you own or are explicitly authorised to assess. Record what passed, what failed and what remains unknown. A scanner result can contribute evidence but does not replace a test of the application's business rules. Likewise, a network protection option does not verify object authorisation or secret-file handling. Attach the useful results to the scenario so future maintainers understand why a particular control exists. ## Keep the model connected to change Review the relevant parts when you add an integration, expose a new endpoint, change a privilege or move data to another destination. You do not need to redraw the entire architecture for a minor text edit. The trigger is a changed assumption about access, information or system behaviour. Keep the model beside deployment and recovery documentation rather than leaving it as a one-time workshop output. SwissOctet supplies a catalogue of infrastructure choices, not a completed application threat model. Choose the configuration and options that support your controls, then verify the deployment you build. A small, maintained model with tested actions is more useful than a large collection of security products with no clear explanation of the risks they address. ## Checklist - List assets and consequences of failure. - Draw data flows and trust boundaries. - Choose specific intrusion, mistake and workflow scenarios. - Assign controls and owners to the important risks. - Test with synthetic data in an authorised environment. - Review the model when a relevant assumption changes. ## Frequently asked questions ### Do I need a formal framework to start? No. A small diagram and a documented set of scenarios can be useful. A framework helps ensure you review risks consistently. ### Does a vulnerability scanner replace threat modelling? No. Scanners may find technical weaknesses, while a threat model also examines design assumptions, permissions and business workflows. ### How often should I update the model? Update the affected parts when data flows, integrations, privileges or exposed functionality change, and review unresolved risks regularly. ## Primary sources - [OWASP: Threat Modeling Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Threat_Modeling_Cheat_Sheet.html) - [OWASP: Threat modelling in practice](https://devguide.owasp.org/en/04-design/01-threat-modeling/07-practical-threat-modeling/) - [OWASP: Business Logic Security](https://cheatsheetseries.owasp.org/cheatsheets/Business_Logic_Security_Cheat_Sheet.html) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. - [Canvas Web](https://swissoctet.com/services/canvas/index.txt): A clean foundation for websites and publishing. Pick your storage, domains and hosting options. ## Related guides - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. - [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/index.txt): Secure administration, expose only required services and establish updates and recovery without locking yourself out. --- # Size VPS CPU and memory from a real workload > Build a memory budget, inspect contention and separate one busy thread from work that can use several virtual cores. Canonical human page: https://swissoctet.com/insights/size-vps-cpu-and-memory/ SwissOctet Editorial. Topic: compute. Level: Applied. Reading time: 6 minutes. ## Direct answer Choose memory for the operating system, persistent services and realistic concurrency with headroom. Choose CPU after measuring which tasks are busy, whether they run in parallel and what delays users actually experience. ## Describe normal work and busy work separately Visitor count alone is a weak sizing input. One request may serve a cached file while another generates a report or queries many tables. List the web workers, database, cache, queue consumers and maintenance tasks that will share the VPS. Describe normal concurrency and the busiest expected operation. Include scheduled exports, package updates and deployments rather than treating them as invisible background activity. For an existing project, collect a representative period that includes a busy window. Record response times and errors alongside resource usage. For a new project, create a small test with realistic request shapes and data sizes. Your initial estimate will be imperfect; the useful goal is a documented starting point that you can compare with measured behaviour after delivery. ## Build the memory budget before adding processes Memory demand comes from the system, persistent application services, per-worker usage and temporary operations. Multiplying a worker's footprint by a planned concurrency is a rough planning tool, not a guarantee, because shared memory and caches complicate the total. Observe the actual processes under load. Leave enough room that a maintenance task does not force the application to compete for every remaining page. Database settings can multiply memory use unexpectedly. PostgreSQL documents that work_mem applies to query operations, and several operations or sessions can run concurrently. A setting that looks modest in isolation can therefore have a larger system effect. Read your database's own guidance, test realistic concurrency and avoid assigning every advertised gigabyte to a single cache. ## Distinguish CPU utilisation from useful parallelism A processor count tells you how many execution resources are presented to the guest, not how efficiently your software can use them. One busy thread may limit an application while other cores remain quiet. Adding workers can help independent requests, but it can also increase database contention and memory demand. Check the application's concurrency model before assuming that twice the core count produces twice the throughput. KVM provides virtual machines with their own virtual hardware. It does not turn every vCPU label into an identical benchmark across hosts and processor generations. Compare the listed CPU model and allocation terms where available, then evaluate the service with your own workload. Avoid drawing a purchasing conclusion from a short synthetic score that does not resemble the application. ## Look for pressure and waiting, not just averages A system can feel slow without maintaining a high average CPU percentage. Processes may wait on storage, memory reclamation or another service. The Linux kernel's Pressure Stall Information exposes CPU, memory and I/O stall information on supported systems. These signals can help identify resource contention alongside normal utilisation metrics and application timings. Read metrics together. Sustained memory pressure, swapping, failed allocations and slow requests point toward a different intervention from a single busy compute worker. Storage waits may justify query changes or a different disk profile. An external API delay will not be repaired by adding local RAM. Explain the observed constraint before choosing which resource to increase. | Observed behaviour | Question to investigate | Possible next step | | --- | --- | --- | | One thread busy, spare cores quiet | Can this work run in parallel? | Improve the task or change worker design | | Memory pressure during a report | How many operations overlap? | Bound concurrency or add tested headroom | | Slow requests with I/O waits | Which reads or writes are delayed? | Inspect queries and storage behaviour | | CPU and memory low, requests slow | Is a dependency delaying responses? | Measure downstream calls | ## A planning example with explicit assumptions Imagine a small application with two web workers, a database and one queue consumer. The team measures those services during ordinary requests and a report-generation task. It discovers that allowing four reports at once raises memory demand sharply while delaying normal traffic. Instead of immediately buying the largest plan, it limits report concurrency and measures the result again. If the adjusted workload still needs more memory, the upgrade now answers an observed requirement. If the queue remains CPU-bound and independent jobs can run concurrently, more execution resources may be appropriate. These are example decisions, not performance figures for SwissOctet plans. Keep your own measurements and constraints with the chosen configuration. ## Leave a clear path for the next measurement Define the signs that will trigger a review: response-time deterioration, repeated memory pressure, growing queues or a changed workload. Keep monitoring lightweight enough that it does not become a new bottleneck. Reassess after adding a feature or a major dataset, and avoid repeated upgrades when the real problem is an unbounded process or a slow query. SwissOctet's VPS families expose CPU and memory specifications and selected resource options. Read the final configuration after adding extras, including the billing period and total. Confirm upgrade arrangements with the live operator before relying on them. A useful VPS size is one that runs the measured workload with sensible headroom and an understandable next step. ## Checklist - Inventory services and maintenance work. - Measure normal and busy-period concurrency. - Budget persistent and temporary memory. - Check whether CPU work can run in parallel. - Compare pressure, utilisation and application timings. - Define when to review the configuration. ## Frequently asked questions ### Should I size a VPS by monthly visitors? Use visitor count as context, then measure request complexity, concurrency, data size and background work. Equal visitor counts can create different loads. ### Does more RAM always make a service faster? No. It helps when memory is a constraint or enables useful caching, but does not resolve every CPU, storage or external dependency delay. ### Does twice the vCPU count double performance? No. Parallelism, processor characteristics, contention and the application's design determine how much extra capacity is useful. ## Primary sources - [Linux kernel: Pressure Stall Information](https://docs.kernel.org/accounting/psi.html) - [PostgreSQL: Resource Consumption](https://www.postgresql.org/docs/current/runtime-config-resource.html) - [KVM project: Kernel Virtual Machine](https://www.linux-kvm.org/page/Main_Page) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [DeskLink RDP](https://swissoctet.com/services/desklink/index.txt): A Windows workspace that follows you. Remote desktop access, configurable resources and a Swiss location. ## Related guides - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. --- # Secure Windows RDP administration without losing access > Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. Canonical human page: https://swissoctet.com/insights/secure-windows-rdp-administration/ SwissOctet Editorial. Topic: operations. Level: Applied. Reading time: 6 minutes. ## Direct answer Restrict who can reach RDP, keep Network Level Authentication enabled where supported, use individual strong credentials and minimise administrative privilege. Test a second session and recovery access before closing the current connection. ## Treat the desktop as an administration boundary An RDP session provides interactive access to a remote system, so the account used for it can become a valuable target. Begin by deciding who needs access and what work they must perform. A shared administrator login is convenient until you need to remove one person's access or understand a configuration change. Individual accounts make those operational tasks clearer. Separate routine activity from privileged changes where the software permits it. A user who needs a business application does not necessarily need unrestricted system administration. Keep the administrator's endpoint maintained too: securing the remote machine does not protect credentials entered from an infected or shared local device. Consider both ends of the session in the access design. ## Limit reachability before relying on login protection Decide which networks or authorised devices should be able to reach the session host. Where your architecture supports it, use a controlled VPN or Remote Desktop Gateway rather than broadly exposing administration. Microsoft documents RD Gateway as a route to internal resources with connection and resource authorisation policies. Its suitability depends on the environment; it is not an included feature merely because a plan supports RDP. Restrict firewall rules to the intended path, and confirm how dynamic client addresses will be handled. Do not make a restrictive rule that immediately disconnects the only administrator without a recovery option. Keep the existing session open, test the new path from another session and document the authorised recovery mechanism before removing the older access route. ## Keep authentication and trust explicit Microsoft recommends Network Level Authentication for most supported environments. NLA requires authentication before establishing a full remote session, adding protection at that stage. It does not replace a firewall, account policy or system updates. Check client compatibility and troubleshoot authentication problems rather than permanently weakening the configuration as the first response. Use unique credentials and a second factor through a supported access architecture where possible. Verify the expected remote identity and certificate behaviour, especially after a rebuild or hostname change. A certificate warning deserves investigation; repeatedly accepting unexpected identities turns a useful trust check into an ignored dialog. Keep recovery credentials in an approved private store. | Layer | Decision | Verification | | --- | --- | --- | | Network | Which clients may reach the host? | Unexpected sources cannot connect | | Authentication | Which account and factors are required? | A permitted second session succeeds | | Privilege | Which tasks require administration? | Routine users cannot change system settings | | Recovery | How is access restored after a mistake? | The documented recovery path is available | ## Reduce what the session can carry Review clipboard, drive, printer and other redirection features against the actual workflow. An administrator may not need every local resource exposed to the remote host. Conversely, disabling a required transfer path without an alternative can encourage unsafe workarounds. Document the allowed method for moving files, and keep secrets out of ordinary desktop notes or shared download directories. For suitable domain-based environments, Microsoft provides Remote Credential Guard to reduce credential exposure during RDP connections. It requires compatible clients and Kerberos authentication and supports direct connections to the target machine; connections through Remote Desktop Gateway or Connection Broker are not supported. Check the requirements for your actual access path rather than treating it as a universal protection for standalone hosted Windows machines. ## Maintain the machine and the evidence you need Schedule operating system and application updates, including a deliberate restart process. Check whether an update requires a reboot and verify the service afterwards. Set sensible session policies for unattended or disconnected work, but consider applications that must continue running. A timeout policy should answer a security or operational need rather than simply copying an arbitrary number from another environment. Retain useful access and incident information under a documented policy. Monitor repeated authentication failures and unexpected administration activity without collecting unnecessary content. Restrict who can read diagnostic records and decide how long they are needed. A precise logging policy is more meaningful than either keeping everything indefinitely or promising that no operational record can ever exist. ## A safe first-session sequence On delivery, verify the expected system, change temporary credentials through the approved process and establish individual access. Confirm the firewall and recovery route, then test a second connection. Apply updates, review redirection and install the required application. Create a backup and practise recovering the settings that matter before depending on the desktop for daily work. DeskLink RDP and selected dedicated configurations offer Windows-related choices in the SwissOctet catalogue. Confirm the operating system, licensing, account privileges and management responsibilities for your order. A supported desktop connection is the beginning of an administration plan; the controls you configure and verify determine how that access is used. ## Checklist - Use individual accounts and appropriate privilege. - Restrict the intended RDP access path. - Keep NLA enabled on compatible systems. - Test a second session before closing current access. - Review redirection, updates and session policy. - Confirm licensing and the recovery procedure. ## Frequently asked questions ### Does NLA make an exposed RDP host completely safe? No. NLA is one authentication control. Reachability, credentials, updates and privilege still need attention. ### Can I use Remote Credential Guard on every Windows server? No. The client, host and authentication environment must meet Microsoft's requirements, including the applicable Kerberos arrangement. ### What should I do before tightening the firewall? Verify a recovery route, preserve the working session and test the new allowed path through a second connection. ## Primary sources - [Microsoft: Enable Remote Desktop and Network Level Authentication](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/remote-desktop-allow-access) - [Microsoft: Remote Desktop Gateway access](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-plan-access-from-anywhere) - [Microsoft: Remote Credential Guard](https://learn.microsoft.com/en-us/windows/security/identity-protection/remote-credential-guard) ## Related infrastructure - [DeskLink RDP](https://swissoctet.com/services/desklink/index.txt): A Windows workspace that follows you. Remote desktop access, configurable resources and a Swiss location. - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. - [Metal EPYC](https://swissoctet.com/services/metal-epyc/index.txt): AMD-powered dedicated hardware for parallel workloads and serious compute. ## Related guides - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/index.txt): Secure administration, expose only required services and establish updates and recovery without locking yourself out. --- # A Linux VPS hardening baseline you can maintain > Secure administration, expose only required services and establish updates and recovery without locking yourself out. Canonical human page: https://swissoctet.com/insights/linux-vps-hardening-baseline/ SwissOctet Editorial. Topic: operations. Level: Applied. Reading time: 6 minutes. ## Direct answer Start with verified access and a recovery route, then configure individual administration, tested SSH keys, a restrictive firewall, maintained software and independent backups. Apply changes incrementally and verify a new session before closing the old one. ## Establish a trusted starting point Before changing the machine, confirm the expected operating system, access method and recovery route. Verify the SSH host identity through the operator's approved information rather than accepting an unexpected key without investigation. Keep temporary credentials private and replace them through the intended process. Record which person is responsible for maintenance and which recovery options are actually available for this service. Keep a working administration session open while making access changes. A copied hardening recipe can remove the only usable login when it assumes a different distribution or account layout. Take one change at a time, check its effective result and preserve a route back. The goal is a system you can maintain safely, not a configuration that looks strict but cannot be administered. ## Make SSH access deliberate Create individual administrative access with appropriate privilege rather than sharing one permanent root login. Install and test the intended public key, keeping the private key on the authorised endpoint. The Ubuntu OpenSSH documentation explains server configuration and authentication choices. Read the effective configuration for your distribution, including included files, before assuming that editing one setting has changed the entire service. Test key access through a second session before changing password authentication or privileged login rules. Ensure the new account can perform the administration it needs. Review any automation that depends on the previous method and replace its access deliberately. A key is an access credential, so use a private storage location and a rotation process rather than leaving copies inside application directories. ## Expose the application, not the whole machine Inventory the listening services and identify which must be public. A web application may need HTTP and HTTPS, while its database can remain reachable only through the intended internal path. Ubuntu documents UFW as a firewall configuration tool, but the useful policy is independent of the tool: permit the required traffic and restrict administration to the approved sources where practical. Check both host-level and provider-level controls if the service includes them. Before enabling a restrictive rule set, permit the tested administration path and verify access from another session. Do not assume that moving SSH to a different port replaces authentication or patching. Keep firewall rules understandable so future troubleshooting does not lead to opening every port as a workaround. | Change | Check before applying | Check afterwards | | --- | --- | --- | | New SSH key | Correct account and public key | Second key-authenticated session works | | Restricted firewall | Required service and recovery paths | Public app works; unintended ports are closed | | Software update | Backup and restart implications | Services restart and application tests pass | | Service permission change | Required read and write paths | App works without broader system access | ## Plan updates as an operating process Keep the system and application dependencies maintained. Ubuntu's automatic-update guidance describes unattended upgrades, permitted origins and restart behaviour. A third-party repository is not automatically covered just because it was added to the machine. Review what the configured update process actually includes, and give separately installed applications their own maintenance path. Decide how service restarts and reboots will be handled. Applying a package update does not always mean every running process is using the new code. Use a maintenance window where the workload requires one, and perform a simple application check afterwards. If a package needs manual migration steps, document them instead of disabling all updates indefinitely and forgetting the resulting exposure. ## Restrict application access and protect recovery Run services with the permissions they need, and separate public content from secrets and deployment metadata. A web process should not be able to rewrite every system setting. Keep environment secrets outside publicly served directories and avoid including them in logs, support exports or general backups without an intentional protection policy. Remove unused packages and services when they have no operational purpose. Maintain an independent backup and test restoring the application into an isolated environment. Restrict backup credentials so a compromised application cannot automatically delete every recovery copy. Monitor disk capacity, backup age and service failures. Logging should answer defined operational questions, with access and retention controlled; it should not become an unlimited copy of sensitive requests. ## A first-deployment sequence that stays reviewable For a new VPS, first verify access and recovery, then establish the administrative account and tested key. Configure the firewall, apply updates and deploy the application under its intended service account. Confirm public behaviour from another environment, check that private files cannot be retrieved and perform a backup restore. Keep notes about each decision and the path for reversing an access change. Vector VPS, Pulse NVMe and selected dedicated plans present Linux choices in the SwissOctet catalogue. Confirm the chosen image and the division of maintenance work before ordering. No Linux image name proves that hardening, updates or backups are already managed. The baseline is the set of controls you configure, verify and continue to maintain as the project changes. ## Checklist - Verify the SSH host identity and recovery route. - Test individual key access in a second session. - Restrict listening services and firewall rules. - Review update coverage and restart behaviour. - Separate secrets from public files and service permissions. - Test an independent recovery copy. ## Frequently asked questions ### Should I disable password login immediately? First establish and test the replacement key access and recovery route. Then change authentication according to your supported configuration. ### Does an SSH port change replace hardening? No. It does not replace strong authentication, restricted access, updates or appropriate account privilege. ### Are automatic updates enough for every application? No. Check permitted repositories, restart requirements and software installed outside the system's update process. ## Primary sources - [Ubuntu Server: OpenSSH server](https://ubuntu.com/server/docs/how-to/security/openssh-server/) - [Ubuntu Server: Firewalls](https://ubuntu.com/server/docs/how-to/security/firewalls/) - [Ubuntu Server: Automatic updates](https://ubuntu.com/server/docs/how-to/software/automatic-updates/) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [Metal EPYC](https://swissoctet.com/services/metal-epyc/index.txt): AMD-powered dedicated hardware for parallel workloads and serious compute. ## Related guides - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. --- # Measure NVMe performance without misleading yourself > Define the I/O pattern, control cache effects and inspect latency distributions before drawing an application conclusion from a disk test. Canonical human page: https://swissoctet.com/insights/nvme-benchmark-methodology/ SwissOctet Editorial. Topic: storage. Level: Advanced. Reading time: 6 minutes. ## Direct answer A useful storage test matches operation size, access pattern, concurrency and durability requirements to the application. Record the test conditions and latency distribution, then confirm the result with application measurements. ## Begin with a storage question, not a score Decide what you need to know before running a benchmark. You may be investigating slow database commits, file-distribution throughput or a build process that creates many small files. Those workloads do not ask the disk to do the same thing. A large sequential copy can look impressive while saying little about the delay experienced by a service making small random reads. NVMe was designed for non-volatile media and efficient parallel I/O, but its protocol name does not describe every part of a hosted storage path. Virtualisation, the file system, resource contention and the application still matter. Write a test hypothesis such as whether storage latency is slowing a particular operation, rather than trying to produce a number that proves the entire server is fast. ## Describe the workload in reproducible terms Record the operation size, sequential or random pattern, read-to-write mix, number of jobs and queue depth. Include the dataset size and test duration. The fio documentation explains these workload controls and the available I/O engines. An intended depth may not be achieved by every engine or setup, so read the reported behaviour as well as the configuration you requested. Keep a copy of the test description beside the result. Note the operating system, file system, mount options, service activity and available capacity. If you compare configurations, change one relevant condition at a time. A test with a different access pattern or concurrency cannot fairly be presented as if only the storage medium changed. | Application pattern | Test dimension to describe | Result to examine | | --- | --- | --- | | Large file delivery | Sequential reads and concurrent clients | Sustained throughput and CPU use | | Record lookup | Small random reads and representative concurrency | Latency distribution and completed operations | | Durable transaction | Write and synchronisation requirements | Commit-related delay, not buffered write speed alone | | Build or extraction | Mixed small-file operations | End-to-end job duration and I/O waits | ## Control caching without pretending it does not matter A dataset that fits in memory may mostly measure cache behaviour after the first pass. That can be useful if the application normally benefits from the same cache, but it should not be labelled raw device performance. Choose deliberately whether the test examines a warm application path, a colder dataset or an I/O mode intended to reduce the operating system's buffering effect. Direct-I/O support and alignment depend on the platform and engine. It also does not automatically express the application's durability requirements or eliminate every cache in the stack. State the chosen mode clearly, and avoid comparing a buffered test with an unbuffered test as if they represented the same work. Keep warm-up and measured intervals separate where that helps interpretation. ## Read latency tails alongside throughput Average latency can conceal slow operations that affect real requests. Examine reported percentiles and the number of samples behind them. A high percentile describes the boundary below which a stated fraction of observed operations fell during that test; it is not a permanent service guarantee. Short or unrepresentative runs give limited evidence about busy production periods. Higher queue depth can improve completed throughput while increasing waiting time. That trade-off may suit batch processing and harm an interactive service. Compare results at concurrency that resembles the application, and monitor CPU and I/O pressure at the same time. Stop before the test creates unnecessary disruption for another workload sharing the environment. ## Keep the test authorised and non-destructive Use a dedicated test directory or a prepared disposable volume, with enough free space and an explicit cleanup plan. Never point a write benchmark at an unverified raw device or production dataset. Check the tool's target and write behaviour before starting, and begin with a limited run. Synthetic I/O can consume capacity and interfere with services even when it does not overwrite useful files. For a production-like evaluation, agree a maintenance window and retain application monitoring. Use fabricated data when possible. Do not infer storage reliability from a speed test: integrity checks, backups and restoration are separate tasks. A device that completes a benchmark still needs a recovery strategy for deletion, software mistakes or loss of the machine. ## Close the loop with application evidence Suppose a report service spends much of its time waiting for random reads. The team tests a representative read pattern, then repeats the actual report against comparable data. If the report improves while its other work remains stable, the result supports the storage hypothesis. If it does not, investigate query design, memory or another dependency instead of repeating broader synthetic tests. Pulse NVMe and selected dedicated configurations list NVMe storage in the SwissOctet catalogue. Their labels are specifications, not published application benchmarks. Use a controlled method to evaluate the delivered environment and preserve the conditions with the findings. The decision becomes stronger when the storage measurement and the user-visible result answer the same question. ## Checklist - Define the application question first. - Record pattern, block size, concurrency and duration. - State cache and I/O-mode assumptions. - Inspect latency percentiles as well as throughput. - Use a verified disposable target and limited initial load. - Confirm the finding with an application test. ## Frequently asked questions ### Is a sequential copy enough to compare database storage? Usually not. Database access may involve small random reads, writes and synchronisation. Model the relevant pattern and verify the actual application. ### Does direct I/O prove durable writes? No. Buffering and durability are separate concerns. Match the synchronisation behaviour required by the application. ### Can I publish one test as a guaranteed plan speed? No. Publish its conditions and scope. A measured result from one run is not a service-level or future performance guarantee. ## Primary sources - [fio: Flexible I/O tester documentation](https://fio.readthedocs.io/en/latest/fio_doc.html) - [NVM Express: Specification overview and FAQ](https://nvmexpress.org/faq_category/specifications/) - [Linux kernel: Pressure Stall Information](https://docs.kernel.org/accounting/psi.html) ## Related infrastructure - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [Metal Hyper](https://swissoctet.com/services/metal-hyper/index.txt): High-capacity dedicated configurations for intensive applications and larger deployments. - [Metal EPYC](https://swissoctet.com/services/metal-epyc/index.txt): AMD-powered dedicated hardware for parallel workloads and serious compute. ## Related guides - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. - [Snapshots and backups: choose the failure you need to survive](https://swissoctet.com/insights/snapshots-backups-consistency/index.txt): Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection. - [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/index.txt): Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. --- # Build a GPU VRAM budget before choosing hardware > Account for weights, activations, caches and temporary buffers, then test the peak workload rather than the model file alone. Canonical human page: https://swissoctet.com/insights/gpu-vram-budget-for-real-workloads/ SwissOctet Editorial. Topic: dedicated. Level: Advanced. Reading time: 6 minutes. ## Direct answer GPU memory demand includes the data and weights in use, intermediate results, runtime workspaces and workload-dependent caches. Measure peak usage at the intended precision, batch size and concurrency; the saved model size is only one input. ## Choose the workload before choosing the GPU A GPU specification becomes useful when you know the software and the work it will perform. Rendering, image processing, training and inference have different memory and compute patterns. Check the application's supported GPU architecture, drivers and runtime before comparing capacity. A card with enough memory can still be unsuitable if the required software path or feature is not supported. Describe the maximum input size, precision, batch size and simultaneous work you intend to allow. For inference, include the longest supported request and concurrent sessions. For rendering, include the representative scene and textures. A successful tiny demonstration is evidence that the stack can start; it is not evidence that the full production workload fits. ## Separate persistent data from working memory Weights or input assets may remain on the device while intermediate results and temporary buffers appear during execution. Training can additionally require gradients and optimiser state. Inference workloads may maintain caches whose size changes with the request. The exact arrangement depends on the model, framework and implementation. Do not apply one universal multiplier to every task and treat it as a capacity guarantee. As a simple arithmetic example, a hypothetical seven-billion-parameter model represented with two bytes per parameter needs about fourteen billion bytes for those parameters alone. That calculation excludes runtime allocations, activations, caches and format overhead. It is a lower-level planning example, not a statement that such a workload fits on a particular SwissOctet configuration. | Memory component | What changes it | How to investigate | | --- | --- | --- | | Weights or scene assets | Model size, representation and loaded assets | Inspect the deployed format and actual loaded allocation | | Intermediate results | Input shape and batch size | Measure a full representative operation | | Caches | Request length and concurrency | Exercise the supported maximum workload | | Workspaces and runtime | Libraries, kernels and execution strategy | Observe peak device and framework usage | ## Measure peak usage through the right view Framework metrics and device-level metrics can describe different things. PyTorch distinguishes memory allocated to tensors from memory reserved by its caching allocator, and provides peak measures. Its memory visualisation documentation also explains that allocations made outside its allocator may not appear in that view. Compare the framework's report with the wider device state rather than assuming one number covers every allocation. Warm up the actual operation, then measure the full task and realistic overlap between tasks. Record software versions and the exact input conditions. An out-of-memory event may occur at a temporary peak, so a quiet final snapshot can miss the problem. Keep diagnostic captures private when they might contain model details or information about your application's inputs. ## Treat batch size and precision as design choices Larger batches can change both utilisation and memory demand. NVIDIA's performance guidance discusses the interaction between operation shape, arithmetic intensity and hardware capabilities. The useful batch size depends on the workload's latency target as well as throughput. A batch policy that maximises completed work per second may make individual users wait longer than the application permits. Reduced precision or quantisation can reduce some memory requirements, but compatibility and output quality need testing. Keep an evaluation dataset and compare the relevant results after a format change. Do not change a model's representation solely to make it fit without checking the behaviour the project depends on. Memory optimisation should preserve the required outcome, not merely avoid an allocation error. ## Keep the rest of the machine in the budget The CPU, host RAM and storage path prepare and feed GPU work. Slow input decoding or insufficient host memory can leave the accelerator waiting. Large model files and datasets also need enough disk space for installation, temporary conversions and updates. Evaluate the complete pipeline instead of purchasing a GPU and expecting every preceding step to become faster. Multiple GPUs do not automatically behave as one pooled memory device. The application must use an appropriate parallel strategy, and communication overhead can matter. Confirm how many devices are provided, the memory of each and the software's supported arrangement. A list of GPU upgrade names is not a verified description of the memory available to one unmodified process. ## Use a representative acceptance test Define a test with the chosen software stack, expected maximum input and allowed concurrency. Measure peak memory, completion time, errors and the quality of the output. Keep some headroom for normal runtime variation and maintenance, with the amount justified by observations. If the workload does not fit, decide whether to reduce concurrency, change the implementation or choose different hardware. Tensor GPU presents GPU-related choices in the SwissOctet catalogue. Confirm the exact device, per-device VRAM, driver compatibility and selected configuration before relying on it. The site does not provide an application-specific fit guarantee. A documented acceptance test connects those hardware details with the work you need the machine to perform. ## Checklist - Confirm supported GPU architecture and runtime. - Budget weights, intermediates, caches and workspaces. - Measure peaks at maximum intended input and concurrency. - Compare framework and device-level memory views. - Validate output after precision or format changes. - Confirm exact per-device VRAM before ordering. ## Frequently asked questions ### Does the saved model size equal VRAM demand? No. Execution adds intermediate results, workspaces, caches and other allocations, while storage formats can differ from in-memory representations. ### Will adding a second GPU automatically double usable memory? No. The application needs an appropriate parallel strategy. Per-device limits and communication behaviour still matter. ### Can reduced precision always solve an out-of-memory problem? No. It may reduce some allocations, but support, remaining buffers and acceptable output quality must be tested. ## Primary sources - [NVIDIA: Get Started With Deep Learning Performance](https://docs.nvidia.com/deeplearning/performance/dl-performance-getting-started/index.html) - [PyTorch: Understanding CUDA Memory Usage](https://docs.pytorch.org/docs/stable/torch_cuda_memory) - [PyTorch: CUDA memory management](https://docs.pytorch.org/docs/stable/notes/cuda.html) ## Related infrastructure - [Tensor GPU](https://swissoctet.com/services/tensor/index.txt): Dedicated GPU configurations for accelerated compute, rendering and machine-learning workloads. - [Metal Hyper](https://swissoctet.com/services/metal-hyper/index.txt): High-capacity dedicated configurations for intensive applications and larger deployments. ## Related guides - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [A dedicated-server migration runbook that protects the data](https://swissoctet.com/insights/dedicated-server-migration-runbook/index.txt): Rehearse the move, establish a consistent data boundary and define what rollback means after the new system accepts writes. - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. --- # A dedicated-server migration runbook that protects the data > Rehearse the move, establish a consistent data boundary and define what rollback means after the new system accepts writes. Canonical human page: https://swissoctet.com/insights/dedicated-server-migration-runbook/ SwissOctet Editorial. Topic: dedicated. Level: Applied. Reading time: 6 minutes. ## Direct answer Prepare and test the new server first, copy data with an application-supported consistency method, define a cutover window and preserve the old environment. Rollback must account for writes accepted on the new server, not only a DNS change. ## Inventory the service before moving the machine A migration includes more than the application files. List databases, uploads, scheduled jobs, queue workers, certificates, domains, secrets and outbound integrations. Record software versions and the operating assumptions that matter, such as file permissions and storage paths. A fresh dedicated server may expose a forgotten dependency that was quietly installed years earlier on the old environment. Assign an owner for the cutover decision and define what success looks like. Include user-visible checks, data consistency and the ability to recover access. Confirm that the new configuration is delivered and usable before announcing a migration date. An order confirmation or a listed hardware specification is not the same as a working destination ready to receive production data. ## Build the destination as a separate environment Install the required stack, establish administration and configure the intended firewall. Keep secrets private and set service permissions deliberately. Verify the application's expected hostname and certificate behaviour before public traffic moves. Apache's virtual-host documentation illustrates why hostname routing is a separate configuration decision from the server's address. A working default page does not prove that the correct application host is configured. Use a representative restored dataset for rehearsal, with outgoing email, payments and scheduled jobs disabled or redirected to safe test systems. This prevents the test environment from acting on real users. Exercise login, uploads, background work and restoration. Record the procedure and its duration so the real window is based on an observed process rather than optimism. ## Choose a consistent data boundary Use a backup or replication method supported by the database and application. PostgreSQL distinguishes SQL dumps, file-system backups and continuous archiving, each with its own assumptions. Its dump guidance notes that database dumps can be internally consistent while cluster-wide roles and other details need separate handling. Read the requirements for the exact system you run rather than copying open data files indiscriminately. Plan how the database relates to uploads and queue state. If a record points to a file that was copied at a different time, the restored application can be incomplete even when both copies succeeded individually. Decide whether to pause writes briefly, use a tested replication arrangement or perform an application-specific export. Keep that consistency decision explicit in the runbook. | Stage | Evidence required | Decision | | --- | --- | --- | | Rehearsal | Application and restored data pass checks | Destination can be considered for cutover | | Final synchronisation | Defined consistent recovery point | Proceed only with understood remaining changes | | Traffic switch | Correct routing and certificate behaviour | Monitor both destinations | | Rollback | Location of all newly accepted writes | Reconcile data before returning traffic | ## Prepare traffic routing without promising instant changes DNS time-to-live controls how long records may be cached, as explained in Cloudflare's DNS documentation. Review the TTL early if DNS is part of the migration, and allow existing cached records to age under their previous setting. Changing the value at the moment of cutover cannot retroactively shorten every cached answer. Different clients may reach different destinations during the transition. Keep the old environment available while routing changes settle, with a deliberate policy for whether it can still accept writes. Avoid running duplicate queue consumers or scheduled jobs unless the application is designed for it. Monitor requests at both sides and confirm the intended hostname, TLS certificate and application version from independent clients. ## Define rollback after writes begin Before the new system accepts changes, returning traffic may be relatively simple. Afterwards, a DNS reversal alone can lose work or create two conflicting histories. Define how newly created records and uploads would be preserved or reconciled. If the application cannot safely merge them, a controlled maintenance period may be preferable to an improvised return to the old copy. Set the conditions that require pausing the migration, and keep the decision owner reachable. Preserve logs and useful evidence under the project's retention rules. Do not delete the old machine or its independent recovery copy merely because the home page loaded once. The retention period should cover the agreed verification and rollback needs. ## Close the migration with operational checks After cutover, verify backups, alerts, certificate renewal, scheduled work and access recovery. Confirm that the monitored host is the new destination and that no test integrations remain in production. Review application errors and user-visible timings under ordinary traffic. Update the inventory and runbook so the next administrator does not have to infer what changed. SwissOctet's dedicated families offer different physical configurations, but migration work and managed assistance must be confirmed for the chosen service. Use the catalogue to select suitable resources, then build a tested move around your application's data. A migration is complete when the service and its recovery process work on the destination, not simply when files have been transferred. ## Checklist - Inventory data, jobs, secrets and integrations. - Verify the delivered destination before scheduling. - Rehearse with safe external integrations. - Define database and upload consistency. - Plan routing transition and duplicate-job prevention. - Specify rollback for new writes. - Verify backups and monitoring after cutover. ## Frequently asked questions ### Can I migrate by copying the application directory? Only if that captures everything the service needs and preserves consistency. Databases, uploads, jobs, secrets and configuration usually require separate attention. ### Does lowering DNS TTL make cutover instant? No. Previously cached answers can remain until their earlier lifetime ends, and clients may update at different times. ### Is rollback just pointing DNS at the old server? Not after the new server accepts writes. You must account for those records and files before returning traffic. ## Primary sources - [PostgreSQL: Backup and Restore](https://www.postgresql.org/docs/current/backup.html) - [PostgreSQL: SQL Dump consistency and restoration](https://www.postgresql.org/docs/current/backup-dump.html) - [Apache: Virtual Host documentation](https://httpd.apache.org/docs/2.4/vhosts/) - [Cloudflare DNS: Time to Live](https://developers.cloudflare.com/dns/manage-dns-records/reference/ttl/) ## Related infrastructure - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. - [Metal Zenith](https://swissoctet.com/services/metal-zenith/index.txt): A step up in dedicated infrastructure for workloads that demand substantial resources. - [Metal EPYC](https://swissoctet.com/services/metal-epyc/index.txt): AMD-powered dedicated hardware for parallel workloads and serious compute. ## Related guides - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [Build a GPU VRAM budget before choosing hardware](https://swissoctet.com/insights/gpu-vram-budget-for-real-workloads/index.txt): Account for weights, activations, caches and temporary buffers, then test the peak workload rather than the model file alone. - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. --- # Web hosting or a VPS: choose the work you want to own > Compare application requirements, control and maintenance responsibilities rather than treating a VPS as the automatic next step for every website. Canonical human page: https://swissoctet.com/insights/web-hosting-or-your-own-vps/ SwissOctet Editorial. Topic: hosting. Level: Foundation. Reading time: 6 minutes. ## Direct answer Choose web hosting when its supported stack and account features fit the site. Choose a VPS when you need operating-system control, custom services or a different resource layout, and can maintain the resulting environment. ## Start with the application, not the product hierarchy A VPS is not automatically a better home for every website. A publishing site that uses a supported runtime and database may fit an account-oriented web hosting plan comfortably. A custom application with long-running workers or operating-system packages may need more control. Write down the deployment requirements first, including runtime versions, extensions, storage behaviour and background tasks, then compare the service boundaries. Also decide which maintenance work you want to own. More control can be useful, but it introduces choices about the web server, system updates, firewall, service accounts and recovery. A simple site can become harder to operate if it moves to a VPS without anyone assigned to those tasks. Match the product to the team as well as the software. ## Understand what account-level hosting presents A web hosting account commonly presents controls for domains, files, databases and related site features. cPanel's documentation explains how its accounts and virtual hosts relate to hostnames. The exact tools visible depend on what the hosting operator enables. A familiar panel name therefore does not prove that every extension, runtime or feature in the documentation is included in your plan. Read domain, subdomain, storage and transfer limits together with the supported stack. Ask about background processes, scheduled tasks and database access if the application needs them. The catalogue alone may not describe how the host isolates accounts or allocates every resource. Obtain the missing information before relying on an assumption borrowed from another web hosting service. ## Understand what a VPS lets you change A VPS gives you an operating-system environment in which you can configure the stack, subject to the service's permissions and conditions. This can suit custom runtimes, independent services and applications needing a specific deployment arrangement. It also makes you responsible for the choices that an account-level platform would otherwise constrain. Administrative access is a capability, not a maintenance agreement. Apache's virtual-host guidance shows how one web server can route multiple hostnames on a machine. You can build that arrangement on a VPS, but you must verify routing, file permissions and certificate behaviour yourself or agree managed assistance. Keep private configuration and credentials outside publicly served content, and make system changes through a documented deployment process. | Requirement | Web hosting question | VPS question | | --- | --- | --- | | Standard website stack | Is the required version and extension enabled? | Who installs and updates the stack? | | Background worker | Is a persistent process permitted? | How is the worker supervised and limited? | | Multiple domains | What account limits apply? | How are virtual hosts and certificates managed? | | Recovery | What can be restored and by whom? | Where is the independent backup and runbook? | ## Compare resource and security responsibilities Do not compare a hosting storage figure with a VPS memory figure as if they describe the same capacity. Investigate the work your site performs and the limits that affect it. cPanel documents resource information interfaces, with some features conditional on the operator's software and configuration. Confirm which measurements and limits your service actually exposes rather than assuming a dashboard screenshot is universal. Both arrangements still need maintained application code, strong credentials and a backup plan. A panel does not protect an outdated plugin automatically, and a VPS firewall does not validate a web form. Apache's security guidance stresses the wider software and permission context around the server. Define the operator's responsibilities and your own before deciding which boundary gives you useful control. ## Two scenarios that lead to different choices Consider a small editorial site using a conventional supported stack. If the hosting plan supplies the required runtime, domain capacity and deployment access, the team can focus on content and application maintenance. Before choosing, it still checks backups, restoration and the handling of private files. There is no technical reason to add system administration merely because a VPS sounds more advanced. Now consider a custom service with a persistent queue worker, specialised package dependencies and application-specific monitoring. If account-level hosting does not permit that arrangement, a VPS can provide the required environment. The team must then budget resources for every process and assign responsibility for updates and recovery. These scenarios illustrate a decision method; they do not assert unlisted features for SwissOctet services. ## Make the next move easy to test Create a small deployment that exercises the real requirements before moving a full production dataset. Verify the runtime, database connection, uploads, scheduled work and external integrations. Test restoration and confirm how access is recovered after a mistake. Keep the existing environment until those checks pass, and record the requirements that would justify a future change of product. Canvas Web presents cPanel-related web hosting configurations, while Vector VPS and Pulse NVMe present virtual environments in the SwissOctet catalogue. Compare their listed resources and options, then confirm availability and operational scope with the live operator. The right choice is the environment that supports the application and the maintenance work you are prepared to carry out. ## Checklist - List runtimes, extensions and background work. - Confirm the enabled account features and limits. - Assign system and application maintenance duties. - Compare the resources relevant to the workload. - Test private-file handling and restoration. - Choose a change trigger for future growth. ## Frequently asked questions ### Is a VPS always faster than web hosting? No. Performance depends on the application, resources, allocation and configuration. Compare the actual workload and service conditions. ### Does cPanel guarantee every documented feature is available? No. Operators can enable, disable or configure features differently. Confirm the requirements for your selected plan. ### Does root access mean the server is managed? No. It describes administrative capability. Management, updates and recovery responsibilities need a separate clear agreement. ## Primary sources - [cPanel: How domains and virtual hosts are handled](https://docs.cpanel.net/knowledge-base/cpanel-product/how-your-server-handles-domains-and-virtual-hosts/) - [cPanel: CPU and Concurrent Connection Usage](https://docs.cpanel.net/cpanel/metrics/cpu-and-concurrent-connection-usage/) - [Apache: Virtual Host documentation](https://httpd.apache.org/docs/2.4/vhosts/) - [Apache: Security Tips](https://httpd.apache.org/docs/2.4/misc/security_tips.html) ## Related infrastructure - [Canvas Web](https://swissoctet.com/services/canvas/index.txt): A clean foundation for websites and publishing. Pick your storage, domains and hosting options. - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. ## Related guides - [A domain, DNS and TLS cutover runbook for a new server](https://swissoctet.com/insights/dns-tls-cutover-runbook/index.txt): Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections. - [Publish an onion service without overlooking the application](https://swissoctet.com/insights/publish-onion-service-safely/index.txt): Plan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. --- # Turn RPO and RTO into a recovery budget you can test > Translate acceptable data loss and interruption into a timed recovery plan, with dependencies, restore capacity and a measurable exercise. Canonical human page: https://swissoctet.com/insights/rpo-rto-recovery-budget/ SwissOctet Editorial. Topic: operations. Level: Applied. Reading time: 4 minutes. ## Direct answer RPO describes the data-loss window you are prepared to accept; RTO describes the interruption you aim to keep within. Define both for a useful business function, then prove the recovery sequence in an exercise. A backup schedule or a server specification alone establishes neither objective. ## Start with a service people can use Recovery objectives become useful when they describe a business function rather than an isolated machine. A server can boot while customers still cannot sign in, retrieve files or complete a request. Write the end condition in ordinary language: authorised users can access the application and the required data is consistent. This makes the target testable by someone outside the infrastructure team. Ask the application's owner what an interruption would prevent and what missing data would cost. A weekly publication and a transaction-processing application may have different answers. Treat the resulting objectives as planning targets, not promises invented from the hardware catalogue. Record who approved them and which failure scenarios the plan covers. ## Separate the two clocks RPO concerns how far back the recovered data may be relative to the disruption. RTO concerns how long the function may remain unavailable. A recent backup can improve the data-loss window while a slow restore still misses the recovery-time target. Conversely, a fast reboot can restore access to an application whose newest data has not survived. Specify the reference points. Decide when the incident clock starts, what counts as restored operation and how the usable data point will be identified. Keep the targets separate from measured results: an objective is what you seek; an exercise shows what the current process achieved. Revisit either when the application or dataset changes. ## Budget every step of the recovery A practical RTO budget includes detection, assessment, authorisation, access to the recovery environment, restoration, application validation and reopening. The file-copy time is only one component. If the person holding the recovery key is unavailable, a theoretically fast backup can still be unusable. List the dependencies and ensure the recovery team can reach them during the failure being considered. Assign a provisional time to each step, then replace estimates with observations. In this illustrative two-hour budget, restoration receives the largest allowance but validation still has protected time. The numbers describe a planning example, not SwissOctet service delivery. If the total has no margin, the design needs improvement before the objective is credible. | Recovery step | Illustrative allowance | Evidence to collect | | --- | --- | --- | | Detect and assess | 15 minutes | Alert arrival and incident decision | | Prepare recovery environment | 20 minutes | Access and configuration available | | Restore data and service | 50 minutes | Completed restore with consistent data | | Validate and reopen | 25 minutes | User journey succeeds | | Contingency margin | 10 minutes | Unexpected work recorded | ## Check the real data-loss window A job scheduled every hour does not automatically deliver a one-hour RPO. A failed job, delayed upload or unusable copy can make the latest recoverable point much older. Observe successful completion and the state that can actually be restored. For an application with several data stores, confirm that their recovery points are compatible rather than reading each timestamp in isolation. Choose a reference event during an exercise, such as an authorised test record created at a known time. After restoration, identify the newest valid record and measure the gap. Use harmless test data. This gives a practical result and exposes assumptions that a dashboard showing only job success might leave hidden. ## Choose a strategy within the budget Backup-and-restore, prepared standby environments and replicated application designs trade cost and complexity against recovery speed. Replication can reduce some delays but may also reproduce an accidental deletion or application mistake. A standby that has drifted from the working configuration creates its own risk. Select a strategy against the failure scenarios and objectives you documented. Consider a small service with a four-hour target and a larger dataset whose restore alone takes six hours in a rehearsal. Buying a faster network port is only a hypothesis: storage reads, receiving writes and application recovery may dominate. Improve the measured limiting step, reduce the recovery set or change the strategy, then exercise again. ## Rehearse without endangering production Use an isolated recovery environment and a defined exercise window. Make sure restored jobs cannot send real notifications, accept public payments or write into production integrations. Test access, data integrity and representative user journeys before considering the exercise complete. Include a person who did not write the original procedure to expose missing instructions. Keep a timeline of the exercise, the recovery point achieved and every interruption caused by unavailable information. A useful report states the measured result, the gap to the objective and a specific corrective action. Repeat after meaningful changes and at an interval appropriate to the project's importance. ## Keep the plan usable during a failure Store the recovery procedure where the team can access it without relying solely on the failed application. Keep credentials and encryption keys in a protected location with a tested access process. Update contacts, dataset sizes and dependencies as the project evolves. An obsolete plan can consume the time margin before restoration even begins. When comparing SwissOctet configurations, separate your recovery architecture from the catalogue's optional backup choices. Confirm what an option covers, where recovery data is held and who performs restoration. The catalogue does not establish an application RPO or RTO. Your measured process and the actual service terms provide the basis for that decision. ## Checklist - Define the restored business function. - Approve separate RPO and RTO targets. - Budget detection, access, restore and validation. - Measure the latest usable data point. - Rehearse in an isolated environment. - Record gaps and repeat after relevant changes. ## Frequently asked questions ### Is RTO the same as uptime? No. RTO is a recovery target for an interruption scenario. Uptime measures availability over a period; one does not establish the other. ### Does hourly backup guarantee a one-hour RPO? No. Check completed, usable copies and the application's consistency requirements. Failed jobs and delayed transfers can widen the recoverable-data gap. ### Must every project use a standby server? Choose a strategy against the project's recovery objectives and measured restore process. A standby adds cost and operational complexity and is not automatically necessary. ## Primary sources - [NIST SP 800-34 Rev. 1: Contingency Planning Guide](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-34r1.pdf) - [AWS Well-Architected: Define recovery objectives](https://docs.aws.amazon.com/wellarchitected/2022-03-31/framework/rel_planning_for_recovery_objective_defined_recovery.html) - [Microsoft Learn: Business continuity, high availability and disaster recovery](https://learn.microsoft.com/en-us/azure/reliability/concept-business-continuity-high-availability-disaster-recovery) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Vault Storage](https://swissoctet.com/services/vault/index.txt): Room for media, archives and growing datasets. A storage-focused Linux configuration. - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. ## Related guides - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. --- # Snapshots and backups: choose the failure you need to survive > Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection. Canonical human page: https://swissoctet.com/insights/snapshots-backups-consistency/ SwissOctet Editorial. Topic: storage. Level: Applied. Reading time: 4 minutes. ## Direct answer A snapshot is a point-in-time representation with protection determined by its implementation. A backup strategy adds deliberate retention, access separation and tested recovery. Some snapshots are backups; others depend on the original storage. Ask what survives deletion, compromise or loss of the primary environment. ## Describe the copy before naming it The word snapshot tells you that a point in time has been represented, but not where the recoverable data is held or who can delete it. A filesystem snapshot on the original storage and a provider-managed block snapshot can have different failure boundaries. Start with the implementation rather than treating the label as a universal promise. AWS documents EBS snapshots as incremental point-in-time backups of its volumes. That is a specific implementation, not proof that every snapshot option behaves the same way. For any service, ask whether restoration depends on the original volume, whether copies leave the primary failure domain and what happens when the source is removed. ## Compare the failures you expect to survive A quick rollback after an update and recovery after losing an account are different problems. A local snapshot may be convenient for the first while offering little separation for the second. Independent copies can add protection, but only if their storage, access and deletion paths are sufficiently separate from the incident you are preparing for. Write down the failure and the required outcome. This illustrative comparison is a decision aid, not a feature list for SwissOctet. It encourages questions about copies and control rather than a claim that one technology is always superior. The actual outcome depends on configuration and the operator's documented recovery process. | Scenario | Question for a snapshot | Question for a backup | | --- | --- | --- | | Bad application update | Can I return to the intended point? | How long does a usable restore take? | | Primary disk lost | Does the copy depend on that disk? | Can I restore onto fresh storage? | | Administrative account compromised | Can this account delete every copy? | Are deletion rights separated? | | Error discovered weeks later | Is that point still retained? | Does retention cover the discovery delay? | ## Check application consistency A disk can capture files while an application is still changing them. Depending on the software and snapshot process, the result may represent a crash-consistent state rather than a coordinated application state. Do not assume that readable files mean a database and its related uploads agree. Use the backup method documented by the application or database. PostgreSQL's continuous-archiving design illustrates the difference: recovery needs a suitable base backup and a continuous sequence of the required write-ahead log files. A directory copied casually while the database runs is not an equivalent procedure. If the application also stores files outside the database, plan how those two datasets are recovered together. ## Treat retention as a recovery window Retention should account for how long an error can remain unnoticed. A ten-day window does not help an accidental deletion discovered after a month. Keeping every copy indefinitely creates a different problem: cost, growing sensitive-data exposure and an unclear deletion policy. Choose retention from concrete operational and data-handling requirements. Label recovery points with useful context, such as application version and completed job time, without embedding secrets. Keep enough history to distinguish a good state from a damaged one. Before pruning, confirm how the chosen system handles shared or incremental data; deleting a labelled point may not correspond to deleting a simple standalone file. ## Separate successful jobs from verified data A backup tool reporting success establishes that its process completed under its rules. It does not automatically prove that all important application data was selected, every stored byte remains intact or a new server can use the result. Those are different checks. Include repository health, selection review and representative restoration in the operational plan. Restic documents a distinction between its default repository check and verification that reads stored pack data. The full data-reading check can consume more time and bandwidth. That example makes the planning point concrete: decide what verification actually reads and budget the work. Use tool documentation rather than assuming every command named check has the same coverage. ## Test a small, complete recovery Imagine a publication with a database, uploaded images and configuration. Restore all three into a private test environment, then open an article and verify its attachments. Keep scheduled mail, payment and publishing integrations disabled during the exercise. Testing only a random text file would miss the relationships that make the application useful. Measure the time required and record which credentials, package versions or external dependencies were missing. Review permissions on the recovered files, not only their contents. A recovery exercise often discovers that the data exists but the instructions or access needed to use it have never been preserved alongside the operating plan. ## Read optional backups as a specific service When configuring SwissOctet, look at the exact backup option and retention period for the family. Ask which volumes and application data it covers, whether recovery is self-service and what happens when the primary configuration changes. The option label alone does not establish an independent copy, an immutable repository or a database-consistent recovery point. Use snapshots where they fit the workload and keep a broader backup strategy for failures they do not cover. Record an independent recovery route for important data, protect the credentials that can erase copies and test the procedure. The strongest choice is the one that survives your defined scenario, not the one with the most reassuring name. ## Checklist - Identify where the recoverable data lives. - List failures the copy must survive. - Use an application-supported consistency method. - Choose retention for the discovery window. - Protect deletion rights separately. - Restore a complete application in isolation. ## Frequently asked questions ### Is a snapshot never a backup? Some snapshot implementations are backups. The useful distinction is their storage dependency, retention, access model and tested recovery, not the label alone. ### Does a successful integrity check prove the application will work? It proves only what that check covers. Test application restoration, configuration, permissions and data relationships separately. ### Should I keep the backup on the same server? A same-server copy may help with limited mistakes but shares important failures. Important data needs a recovery route outside the failure boundary you intend to survive. ## Primary sources - [Amazon EBS: Snapshots](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshots.html) - [PostgreSQL: Continuous archiving and point-in-time recovery](https://www.postgresql.org/docs/current/continuous-archiving.html) - [Restic: Working with repositories and integrity checks](https://restic.readthedocs.io/en/stable/045_working_with_repos.html) ## Related infrastructure - [Vault Storage](https://swissoctet.com/services/vault/index.txt): Room for media, archives and growing datasets. A storage-focused Linux configuration. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [Metal Zenith](https://swissoctet.com/services/metal-zenith/index.txt): A step up in dedicated infrastructure for workloads that demand substantial resources. ## Related guides - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. - [Measure NVMe performance without misleading yourself](https://swissoctet.com/insights/nvme-benchmark-methodology/index.txt): Define the I/O pattern, control cache effects and inspect latency distributions before drawing an application conclusion from a disk test. - [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/index.txt): Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. --- # Object, file or block storage: choose the interface your application needs > Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. Canonical human page: https://swissoctet.com/insights/object-file-block-storage/ SwissOctet Editorial. Topic: storage. Level: Foundation. Reading time: 4 minutes. ## Direct answer Block storage presents a volume, file storage presents a filesystem interface, and object storage presents objects addressed through an API. Choose the interface your software expects, then compare consistency, access, performance and recovery. None of these labels by itself establishes a backup or an unlimited capacity promise. ## Start with the application's interface Before comparing terabytes, identify how the application reads and changes data. Does it expect a locally mounted volume, a shared path with file permissions or an API that retrieves an object by key? Those interfaces are different. A product with plenty of capacity can still require significant application changes if it exposes the wrong access model. Write down concrete operations: append to a file, update part of a database, list a directory, serve a large image or let several machines edit the same document. The storage choice should support those operations deliberately. Treat convenient client tools as adaptations to investigate, rather than assuming they make every backend interchangeable. ## Understand block storage responsibilities Block storage provides a volume-like interface on which a system can build a filesystem or another data layout. The operating system and application usually manage the meaning of the data written into those blocks. It is a common foundation for system disks and applications that expect a mounted volume, but its exact attachment and sharing rules depend on the implementation. Plan partitions, formatting, filesystem capacity and recovery before using the volume. A block allocation does not automatically create a database-consistent backup or safely allow several unrelated machines to write at once. Verify the product's attachment model and any software coordination it requires. The right access pattern is as important as the capacity number. ## Understand file storage semantics File storage gives applications names and paths through a filesystem interface. A shared service may expose a protocol such as NFS, with implementation-specific permissions, locking and consistency behaviour. Amazon EFS is one documented example of an NFS-based service; its capabilities describe EFS, not every shared filesystem or a SwissOctet storage option. For a team workspace, ask how identities map to permissions and what happens when two clients update the same file. For an application, verify the operations it depends on rather than testing only a directory listing. Network reachability and client configuration are part of the operating system design when the files are accessed remotely. ## Understand object storage as an API Object storage addresses stored content through keys and associated metadata. Amazon S3 documents this model with buckets, object keys and version identifiers. An object interface suits software designed to upload and retrieve content through that API. It is a different abstraction from a disk mounted by the operating system or a shared directory with ordinary file operations. Do not assume a folder-like browser establishes filesystem semantics. Prefixes can help organise names while the API still controls how objects are created and changed. Verify the chosen service's consistency, versioning and access-control behaviour. These details determine whether an upload workflow, media catalogue or export repository can use the interface safely and efficiently. ## Map a practical project to the interfaces Consider an illustrative application with a relational database, user-uploaded images and a directory shared by batch workers. The database may expect a suitable volume, images may fit an object-aware application design, and the workers may require a shared filesystem. Combining interfaces can be sensible when each serves a clear role rather than forcing every dataset into one storage product. The table below is a starting point for questions, not a product recommendation or a claim about currently available SwissOctet object services. The catalogue lists storage resources for its actual configurations. If you want to expose a file or object service yourself, verify the software, resource needs and administrative work required to build it. | Application requirement | Interface to evaluate | Question before deployment | | --- | --- | --- | | Mounted system or database volume | Block | Does the application support the volume and recovery method? | | Shared paths between clients | File | Are permissions, locking and consistency suitable? | | API-based media uploads | Object | Does the application support the API and access rules? | | Independent backup repository | Any supported target | Does the recovery tool verify and restore this format? | ## Compare performance without mixing metrics Capacity, operation latency and sustained transfer are different characteristics. A workload reading large media objects differs from one updating many small files or database pages. Build a representative test with realistic data size and concurrency. Include client processing and network transfer where they belong instead of attributing the whole result to the storage backend. Also examine how the system behaves near its practical limits. Growing files, object-list operations, metadata activity and simultaneous clients can change the resource picture. Measure normal and busy periods, leave capacity for maintenance and define alerts before the environment fills. A label such as NVMe identifies a storage technology, not every application outcome. ## Keep security and recovery across every interface Use an access model appropriate to each dataset. Keep administrative credentials separate from application access and protect any keys required to decrypt retained data. Review public exposure explicitly: a privately intended file share or object collection should not become accessible merely because its application was deployed with convenient defaults. Finally, plan a restore that covers all related stores. A database recovery point and the uploaded files it references must work together. Document ownership, backup format and the recovery order. When comparing SwissOctet Vault or server storage, read the exact allocation and options; do not infer a managed object API, replication policy or backup guarantee from a broad storage label. ## Checklist - List the operations the application needs. - Identify its expected storage interface. - Check sharing, locking and access semantics. - Test realistic data and concurrency. - Keep application and administrative access separate. - Restore all related datasets together. ## Frequently asked questions ### Can object storage be used like an ordinary disk? Adaptation tools exist, but the underlying API and semantics differ. Validate the application's required operations rather than assuming a mounted interface makes them equivalent. ### Is SAN automatically object storage? No. A SAN label does not establish an object API. Read the actual volume and access specification and confirm what the configuration exposes. ### Which interface is best for backups? Choose a target supported by your backup tool and verify access separation, retention and restoration. The interface alone does not determine backup quality. ## Primary sources - [AWS: Block, file and object storage compared](https://aws.amazon.com/compare/the-difference-between-block-file-object-storage/) - [Amazon S3: Objects overview](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingObjects.html) - [Amazon EFS: File-system interface and access semantics](https://docs.aws.amazon.com/efs/latest/ug/whatisefs.html) ## Related infrastructure - [Vault Storage](https://swissoctet.com/services/vault/index.txt): Room for media, archives and growing datasets. A storage-focused Linux configuration. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [Metal EPYC](https://swissoctet.com/services/metal-epyc/index.txt): AMD-powered dedicated hardware for parallel workloads and serious compute. ## Related guides - [When NVMe makes a difference to your application](https://swissoctet.com/insights/nvme-storage-when-it-matters/index.txt): Distinguish capacity, latency and throughput so that a faster storage label answers a real application problem. - [Measure NVMe performance without misleading yourself](https://swissoctet.com/insights/nvme-benchmark-methodology/index.txt): Define the I/O pattern, control cache effects and inspect latency distributions before drawing an application conclusion from a disk test. - [Snapshots and backups: choose the failure you need to survive](https://swissoctet.com/insights/snapshots-backups-consistency/index.txt): Compare recovery points, failure boundaries and application consistency instead of assuming a snapshot and an independent backup provide the same protection. --- # Size a transfer with latency, concurrency and throughput measurements > Build a repeatable transfer model using payload volume, delivery windows and round-trip time, then test it without confusing a port label with useful throughput. Canonical human page: https://swissoctet.com/insights/size-throughput-with-bandwidth-delay/ SwissOctet Editorial. Topic: network. Level: Advanced. Reading time: 4 minutes. ## Direct answer Calculate the useful transfer rate your delivery window requires, then measure the complete path. Port capacity, round-trip time, TCP behaviour, storage and application processing all affect the result. Use controlled tests with realistic concurrency and repeat them through the actual application before selecting a network tier. ## Turn the delivery window into a rate Begin with an amount of useful application data and the time available to deliver it. Using decimal units, transferring 2 TB in two hours requires roughly 278 MB per second of payload, or 2.22 Gbps, before allowing for protocol overhead and interruptions. The arithmetic is a planning example, not a measured service result. Include the transfers that overlap. A scheduled export, customer downloads and backup uploads can share resources even if their monthly totals look modest. Write a busy-period model, not only a monthly average. Specify which direction matters and whether a failed transfer must restart or can resume; that behaviour affects the amount of work the system performs. ## Keep port capacity separate from useful throughput A server port describes a link capacity. Useful throughput describes the data delivered by your application during an observed interval. Encryption, protocol framing, retransmission, storage activity and work at the receiver occupy parts of that path. A listed 10 Gbps port therefore does not establish that an application will continuously deliver 10 Gbps of payload. IETF RFC 6349 specifically distinguishes testing the network path from examining TCP performance. Use this separation in your own diagnosis. First confirm that the endpoints and route are appropriate, then investigate the transport and application. Increasing the purchased port does not correct a receiver that writes data slowly or an application that processes one request at a time. ## Understand why round-trip time matters TCP controls how much data can remain in flight before acknowledgements return. The bandwidth-delay product gives a useful scale for this: rate multiplied by round-trip time. A hypothetical 10 Gbps path with 40 milliseconds of round-trip delay represents about 50 MB in flight. This calculation explains why latency and transport behaviour belong in high-speed planning. The result is not an instruction to apply an arbitrary socket setting. Operating systems, congestion control, negotiated windows and the actual path influence behaviour. Verify current software documentation and inspect measurements before tuning. More parallel connections may improve aggregate throughput in some circumstances, but they can also conceal the behaviour of the individual transfer your application depends on. ## Build a controlled test matrix Use only endpoints you own or are authorised to test. Agree the test window and rate so the exercise does not disrupt normal service. Tools such as iperf3 provide configurable direction, duration and parallel streams; the official documentation defines those controls. Record the version, endpoints, route context and settings with the result so another operator can reproduce it. Begin with a single flow, then add representative concurrency. Run both directions if the application depends on both. This illustrative matrix separates questions that a single headline result would mix together. Keep raw results privately when they reveal internal addresses or operational details, and publish only the measurements needed for the decision. | Test | What it investigates | What it does not prove | | --- | --- | --- | | One transport flow | Single-flow path behaviour | Aggregate application delivery | | Several parallel flows | Concurrency and aggregate limits | One customer's transfer rate | | Application transfer | Storage, protocol and software together | Performance for every dataset | | Busy-period repeat | Variation under realistic activity | A permanent throughput guarantee | ## Look at the endpoints during the test Record CPU use, memory pressure, storage activity and error counters at both ends. A transfer result without endpoint observations may leave the real constraint invisible. Check whether one process or CPU is saturated while others are idle. Avoid changing several settings at once, because that makes it difficult to identify which adjustment helped. Separate a memory-backed test from one that reads and writes real data. The former can help investigate the transport path; the latter reflects more of the application's job. If the results differ sharply, inspect storage and processing rather than treating the memory-backed figure as a delivery promise. Both measurements can be useful when their scope is clear. ## Test the application with realistic payloads An HTTP export, encrypted replication stream and file-transfer session have different processing patterns. Use representative file sizes, request rates and encryption settings. Include the time spent preparing data before the first byte is sent when the user waits for that step. Distinguish first-response latency from completion time instead of reporting one as the other. Repeat the test across enough intervals to see variation, and keep a baseline before changing the configuration. For the hypothetical 2 TB export, compare the actual completion time with the two-hour window and leave margin for interruptions. Choose an improvement against the observed bottleneck rather than multiplying the port capacity without a reason. ## Use the result to select a configuration The useful output is a resource requirement with evidence: a measured payload rate, acceptable completion time, expected concurrency and a known limiting stage. Compare SwissOctet network variants against that requirement, including traffic allowance and the CPU and storage specifications. The location alone does not determine the route or end-to-end latency to every receiver. Keep the test procedure after deployment. Reuse it when datasets grow, software changes or users move to different networks. A repeatable baseline makes a performance incident easier to diagnose and provides a sounder reason for changing a configuration than an isolated speed test or an advertised maximum. ## Checklist - Calculate payload rate from volume and deadline. - Model overlapping transfers and direction. - Agree authorised test endpoints and limits. - Compare one flow, concurrency and application tests. - Observe both endpoints while testing. - Preserve a repeatable baseline and useful margin. ## Frequently asked questions ### Does a larger TCP window always fix a slow transfer? No. Diagnose the path and endpoints first. Storage, CPU, loss and application behaviour can dominate, and transport tuning must suit the actual system. ### Why test a single flow and several flows? They answer different questions. Aggregate capacity can be higher than one transfer's rate; the application's concurrency determines which result matters. ### Can I run a capacity test against any public server? Use endpoints you control or have permission to test. Agree duration, rate and timing so the measurement does not disrupt unrelated services. ## Primary sources - [IETF RFC 6349: Framework for TCP throughput testing](https://datatracker.ietf.org/doc/html/rfc6349) - [ESnet: Invoking iperf3](https://software.es.net/iperf/invoking.html) ## Related infrastructure - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. - [Transit 40](https://swissoctet.com/services/transit-40/index.txt): Dedicated configurations with a 40 Gbps port for bandwidth-intensive applications. - [Transit 100](https://swissoctet.com/services/transit-100/index.txt): 100 Gbps port configurations for demanding content distribution and network workloads. ## Related guides - [Bandwidth, port speed and transfer: read the full picture](https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/index.txt): Estimate the data your project moves and understand why a larger port is only one part of network performance. - [Plan a 40, 100 or 200 Gbps origin as a complete system](https://swissoctet.com/insights/plan-40-100-200-gbps/index.txt): Translate large port classes into storage, CPU, concurrency and operational questions before selecting a high-volume distribution configuration. - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. --- # Plan a 40, 100 or 200 Gbps origin as a complete system > Translate large port classes into storage, CPU, concurrency and operational questions before selecting a high-volume distribution configuration. Canonical human page: https://swissoctet.com/insights/plan-40-100-200-gbps/ SwissOctet Editorial. Topic: network. Level: Advanced. Reading time: 4 minutes. ## Direct answer A large port is valuable only when the application, storage, processor, network path and receivers can use it. Plan the working set and concurrency, benchmark each limiting stage and define operational boundaries. The 40, 100 and 200 Gbps catalogue labels are port classes, not universal transfer or availability guarantees. ## Translate the port into a data scale With decimal units, 40, 100 and 200 Gbps correspond to line-rate arithmetic of 5, 12.5 and 25 GB per second. These are reference conversions before protocol and implementation effects. They describe the scale of the surrounding design, not a measured rate or a promise that an origin will deliver that amount of application content. For a distribution project, estimate concurrent requests, object sizes and the working set. A service repeatedly delivering a small popular set differs from one streaming uncached archives. Make the assumptions explicit. A large port purchased without those assumptions can leave storage, application or receiver limits untouched while increasing the project's recurring cost. | Listed port class | Raw decimal conversion | Planning implication | | --- | --- | --- | | 40 Gbps | 5 GB/s before overhead | Measure the content and application path | | 100 Gbps | 12.5 GB/s before overhead | Examine storage, concurrency and processing | | 200 Gbps | 25 GB/s before overhead | Validate every stage and receiving capacity | ## Model the working set and cache behaviour Identify which content is requested frequently and which must be read from storage on demand. A warm cache can produce a result that a cold start cannot sustain. Test both conditions when they matter to the project. Keep the dataset large enough and realistic enough that the measurement answers the question you actually need to resolve. Imagine a lawful software-download origin with popular releases and an older archive. Compare the busy release window with normal archive access. Reserve capacity for publishing, checksum generation and backup traffic where those operations overlap. This original scenario provides a planning framework; it does not establish any particular hardware or caching service as included in SwissOctet. ## Measure storage independently Start by measuring the storage operations the application performs. Sequential reads of large files and many small random reads can expose different limits. The fio documentation describes workload parameters that can represent those patterns. Use controlled test files and settings that fit the system, and avoid destructive tests on production data. Record the storage layout, dataset size and test conditions. A benchmark involving cached data is not equivalent to sustained reads from the underlying devices. Repeat with the application's real content path afterwards. More capacity does not automatically increase delivery rate, and several selected drives do not establish a specific array layout or measured throughput. ## Observe processor and queue limits At high transfer rates, processing and interrupt handling can matter alongside application CPU use. Linux documents receive-side scaling and related mechanisms for distributing network work across queues and processors. Their presence and behaviour depend on hardware and configuration. Use those documents to interpret measurements rather than applying a generic tuning recipe to every server. Watch whether one CPU, worker or receive queue becomes busy before the aggregate system does. Include encryption, compression and request handling in the test when the production service uses them. An idle average CPU number can hide a saturated component. Change one factor at a time and retain the baseline so the effect is understandable. ## Validate the serving application The server must do more than move bytes through a network benchmark. Validate connections, request parsing, authorisation, content reads and response completion with your intended software. Nginx documents file-transfer and connection controls for its own implementation; other software has different settings. Read the documentation for the actual version you will operate. Test realistic concurrency and observe tail completion times as well as aggregate output. A large aggregate number can coexist with individual requests that time out. Establish a limit at which the service still behaves acceptably, then leave operating margin rather than aiming to run every component at its theoretical maximum throughout the day. ## Compare the actual Transit specifications SwissOctet's Transit families keep the country Swiss while listing different processor, memory and storage foundations. Read the exact plan: Transit 100 lists SSD storage, while other Transit base specifications list NVMe. Additional disk options have their own labels. Do not let the port class substitute for reviewing the rest of the configuration. Also confirm availability, traffic terms, administrative responsibilities and the recovery process with the actual service. Unmetered traffic describes a traffic model, not permission for arbitrary activity or an uptime commitment. High-volume workloads need clear operating terms and rights to distribute the content, just as smaller ones do. ## Prepare operations before opening traffic Define who can publish content, change configuration and administer the origin. Protect those interfaces, collect useful operational measurements and set thresholds for overload. Keep a way to reduce traffic or roll back a release if the application behaves unexpectedly. A large interface can amplify the consequences of an ordinary software or access mistake. Run a staged exercise using authorised receivers and agreed limits, then increase toward the planned workload. Keep the results, unanswered questions and resource headroom in the deployment record. Select a larger port only when this evidence supports it; a complete, measured design is more useful than the largest number available in the catalogue. ## Checklist - Convert the port class without treating it as payload delivery. - Model cache hits, cold reads and concurrent requests. - Benchmark storage with harmless test data. - Observe CPU, workers and network queues. - Test the serving application and receiver capacity. - Stage traffic and retain a rollback procedure. ## Frequently asked questions ### Is the largest port always the safest choice? No. Choose from measured demand and the complete system's limits. A larger port does not resolve insufficient storage, processor or application capacity. ### Does every Transit family use NVMe? No. Read the actual plan. Transit 100's base specification lists SSD; other base plans and additional-drive options have their own descriptions. ### Why test with cold data as well as cached data? They expose different operating conditions. A release, restart or changing working set may produce storage activity that a warm-cache benchmark avoids. ## Primary sources - [Linux kernel: Scaling in the networking stack](https://docs.kernel.org/networking/scaling.html) - [fio: Workload and measurement documentation](https://fio.readthedocs.io/en/latest/fio_doc.html) - [Nginx: HTTP core module](https://nginx.org/en/docs/http/ngx_http_core_module.html) ## Related infrastructure - [Transit 40](https://swissoctet.com/services/transit-40/index.txt): Dedicated configurations with a 40 Gbps port for bandwidth-intensive applications. - [Transit 100](https://swissoctet.com/services/transit-100/index.txt): 100 Gbps port configurations for demanding content distribution and network workloads. - [Transit 200](https://swissoctet.com/services/transit-200/index.txt): 200 Gbps port configurations for projects operating at a different network scale. ## Related guides - [Bandwidth, port speed and transfer: read the full picture](https://swissoctet.com/insights/bandwidth-port-speed-and-transfer/index.txt): Estimate the data your project moves and understand why a larger port is only one part of network performance. - [Size a transfer with latency, concurrency and throughput measurements](https://swissoctet.com/insights/size-throughput-with-bandwidth-delay/index.txt): Build a repeatable transfer model using payload volume, delivery windows and round-trip time, then test it without confusing a port label with useful throughput. - [Build monitoring that leads to a useful incident response](https://swissoctet.com/insights/monitoring-incident-response-playbook/index.txt): Connect application symptoms, actionable alerts and a small response playbook so that an operator can make clear decisions when a service degrades. --- # A domain, DNS and TLS cutover runbook for a new server > Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections. Canonical human page: https://swissoctet.com/insights/dns-tls-cutover-runbook/ SwissOctet Editorial. Topic: hosting. Level: Applied. Reading time: 4 minutes. ## Direct answer Prepare the server and certificate for the intended hostname, test the application before changing public DNS, and keep the old environment available during the transition. Verify authoritative records, cached answers and TLS independently. A DNS update alone does not establish that the correct application and certificate are being served. ## Inventory the names and dependencies List every hostname the site uses, including the main domain, aliases, API endpoints and application callbacks. Record who controls registration and authoritative DNS. Hosting an application does not automatically register its domain or give the server operator control of its records. Keep access to the existing environment until the new one has been validated. Also identify email and third-party verification records that the move should preserve. A website migration should not casually replace an entire DNS zone. Make a record-level change plan with the intended addresses and a rollback value. Store credentials privately; the runbook needs owners and procedures rather than actual passwords or API tokens. ## Prepare hostname routing on the new server A machine receiving a connection must serve the intended application for its hostname. Configure the web server or hosting panel accordingly, with the public document root separated from private configuration and credentials. Test all required names and redirects, not only a generic welcome page reached through the server's address. Use a controlled test method that sends the intended hostname to the new endpoint before the public change. Check login, uploads and application-generated links where applicable. Disable jobs that could duplicate production actions during testing. The test should prove application behaviour without sending real mail, taking payments or modifying the old live database unintentionally. ## Choose a certificate validation method Certificate issuance requires proof of control for the requested names. Let's Encrypt documents HTTP-01 and DNS-01 among its validation methods. HTTP validation depends on serving the required challenge correctly; DNS validation uses a specified DNS record and can support wildcard issuance. Select a method that fits the actual deployment and can be maintained safely. Keep validation credentials narrowly scoped where possible. DNS automation is especially sensitive because broad DNS credentials can affect more than one website. Plan certificate renewal and how the renewed files reach the serving process. Successful first issuance is useful, but a site also needs a working renewal process and monitoring of the certificate it actually presents. ## Plan the cache window before changing DNS DNS records carry a time-to-live used by resolvers when caching answers. A record change does not instantaneously replace every cached result. If a transition benefits from a shorter TTL, plan the adjustment early enough that previously cached answers can expire. Keep both old and new environments able to handle the transition you designed. This illustrative sequence separates preparation from the public cutover. Its timing must be adapted to the domain, resolver behaviour and application. It is not a universal propagation schedule. A migration involving live writes also needs an application-specific data cutover, because two functioning web servers can otherwise accept changes into different datasets. | Stage | Action | Condition before proceeding | | --- | --- | --- | | Preparation | Inventory records and configure new endpoint | Application works for intended names | | Certificate | Issue and install certificate | Correct chain and hostname validate | | Transition | Update only planned DNS records | Data cutover and rollback are defined | | Observation | Check authoritative and client results | User journeys succeed through new endpoint | | Completion | Retire old service after validation | Residual traffic and recovery needs reviewed | ## Verify DNS and TLS separately Check the authoritative record first, then compare answers from clients or resolvers involved in the transition. A correct authoritative value and an older cached value can coexist. Inspect the endpoint reached by the browser rather than assuming every connection already uses the new address. Keep observations timestamped so the transition is understandable. For TLS, validate the intended hostname, certificate validity and chain through an actual client connection. Inspect every required alias and redirect path. Mozilla's TLS documentation explains server authentication and mixed-content concerns: the page and its subresources should be delivered securely. A certificate on one hostname does not automatically cover another application endpoint. ## Make rollback a data decision too A DNS rollback can redirect traffic, but it does not reverse writes made on the new application. Define how you will handle that data before the cutover. For a static publication, rollback may be straightforward; for a service accepting uploads or orders, the application state needs a clear owner and reconciliation procedure. Imagine migrating a small publishing site with comments. You can prepare a maintenance interval or a controlled read-only transition while the final data is copied. Test the reopen procedure and keep the old deployment ready. Choose the approach that fits the application rather than using a DNS change as a substitute for consistency planning. ## Observe the site after the switch Verify real user journeys, error rates, certificate presentation and background tasks after the new endpoint receives traffic. Confirm that backups now cover the intended application and data. Review old-server access before retirement and remove obsolete credentials when the recovery and rollback needs have been resolved. Record the final DNS and certificate configuration. When selecting SwissOctet web hosting or compute, confirm the actual domain, certificate and administration responsibilities for the configuration. The catalogue provides a hosting destination and resources; it does not establish that your domain has already been connected or that certificate renewal has been configured. Keep those steps concrete and verifiable in the deployment plan. ## Checklist - Inventory every hostname and preserve unrelated DNS records. - Test hostname routing before public cutover. - Choose and automate a suitable certificate challenge. - Plan TTL changes and the data transition. - Verify DNS and TLS through separate checks. - Retain rollback access and resolve new writes before reverting. ## Frequently asked questions ### Does changing an A record activate HTTPS? No. DNS chooses an endpoint; that endpoint still needs the correct hostname routing and a valid, installed certificate. ### Can I revert only the DNS record if something breaks? Traffic can be redirected, but application writes need separate handling. Define a data rollback or reconciliation plan before the migration. ### Is a wildcard certificate always necessary? No. Choose certificate names and validation according to the actual hostnames. A wildcard has specific coverage and validation requirements; it is not a universal migration shortcut. ## Primary sources - [Let's Encrypt: Challenge types](https://letsencrypt.org/docs/challenge-types/) - [IETF RFC 1034: DNS concepts and facilities](https://datatracker.ietf.org/doc/html/rfc1034) - [Mozilla MDN: Transport Layer Security](https://developer.mozilla.org/en-US/docs/Web/Security/Defenses/Transport_Layer_Security) ## Related infrastructure - [Canvas Web](https://swissoctet.com/services/canvas/index.txt): A clean foundation for websites and publishing. Pick your storage, domains and hosting options. - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. ## Related guides - [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/index.txt): Compare application requirements, control and maintenance responsibilities rather than treating a VPS as the automatic next step for every website. - [Publish an onion service without overlooking the application](https://swissoctet.com/insights/publish-onion-service-safely/index.txt): Plan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. --- # Publish an onion service without overlooking the application > Plan a legitimate onion publication with controlled backend exposure, careful content review, service-key recovery and an explicit audience-access model. Canonical human page: https://swissoctet.com/insights/publish-onion-service-safely/ SwissOctet Editorial. Topic: hosting. Level: Applied. Reading time: 4 minutes. ## Direct answer Secure the application and its administrative access, limit the backend listener, protect onion-service keys and test the publication through a compatible client. Onion routing is one layer of the design. It does not remove application vulnerabilities, mistakes in published content or the need to define who should have access. ## Define the publication and its audience Begin with a lawful publishing purpose and a description of the audience. A public research publication and a restricted project portal have different access requirements. Decide which content is intended to be public, which needs application authentication and which should never reach the web root. Keep those decisions separate from the transport used to reach the site. Write a small data inventory before deployment: pages, uploads, database content, administrator accounts and service configuration. Assign an owner for updates and incident handling. The fact that a site uses an onion address does not settle retention, content rights or security responsibilities. Those remain practical application decisions that need an explicit operating plan. ## Keep the backend listener deliberate An onion service maps a connection to a local application endpoint. Review where that endpoint listens and what other networks can reach it. The Tor Project's setup guide describes Unix sockets as a useful way to avoid exposing the backend to a local network. Choose an approach supported by your server and verify its actual reachability. A connection that works through Tor can coexist with an unintended public listener. Test both the intended access path and the boundaries around the backend. Avoid generic configuration assumptions; read the application's listening settings and the web server's virtual-host routing. Keep management interfaces distinct from the publicly intended service and restrict who may change those settings. ## Review what the application publishes Inspect pages, uploaded files, error output and embedded resources as a reader would encounter them. An application can reveal operational details through debugging messages or link to external assets without that being obvious in its main design. Review generated URLs and content metadata. Serve only the resources the publication requires and understand any third-party request it initiates. For an illustrative research site, review a sample article, attachment and contact page before launch. Verify that a private editorial document and an environment file are outside the public directory. Use non-sensitive test material when checking uploads. A successful onion connection proves reachability; this content review checks what the service actually discloses to its audience. ## Treat the service identity as protected material The onion-service configuration includes key material that must remain private. Keep it outside public website files and limit access to the operators who need it. Plan how a legitimate recovery preserves the intended service identity and how a compromise would be handled. Do not place service keys into a public archive, support message or shared project repository. Include the application, data and required service configuration in the recovery design, with appropriate protection for each. A backup of site content alone may not restore the intended address, while a copy containing private keys creates a sensitive backup. Document who can decrypt and restore it and test that access without exposing the keys in exercise reports. ## Choose public or restricted access explicitly Application login and Tor client authorisation are different layers. The Tor Project documents client authorisation for making access to a v3 onion service depend on a client credential. Decide whether that model fits the audience and operational process. It is not automatically needed for a public publication and does not replace the application's permissions once a client connects. Consider a project portal with a small approved group. You need a way to distribute, replace and revoke access material privately, as well as manage application accounts. Test the removal of an authorised client and an application user separately. The following table keeps these controls distinct instead of promising that one setting solves every access problem. | Control | Question it answers | Separate responsibility | | --- | --- | --- | | Backend listener | Who can reach the local application endpoint? | Web server and network configuration | | Client authorisation | Which clients may connect to the onion service? | Private credential distribution and revocation | | Application permissions | What may a connected user do? | Account roles and data access | | Publishing review | What does the site disclose? | Content, uploads and error handling | ## Test through the reader's connection Use a compatible client to test pages, navigation, forms and downloads through the intended onion access path. Observe errors and application resource use with harmless test traffic. Avoid measuring only a local backend request, because it does not exercise the reader's full connection. Keep test accounts and any restricted-access credentials private. Check recovery and maintenance procedures as well. An application update should have a rollback point and a way to validate the onion route afterwards. Define useful operational logs and retention without assuming that a distribution or transport label creates a zero-logs policy. Preserve enough evidence to diagnose faults while avoiding unnecessary collection. ## Read hosting options as parts of the design SwissOctet Veil lists application-stack, onion-address and backup choices. Select the stack your software expects and enough CPU, memory and storage for the workload. Confirm how the actual service handles deployment, service identity and restoration before depending on it. The catalogue's Swiss location is separate from the privacy behaviour of your application. Keep the service intended for legitimate publishing and authorised users. Plan administrator updates, access reviews and a response to compromised application credentials. An onion publication works best when content, backend exposure and recovery are understandable; the transport should support that plan rather than become an excuse to skip ordinary software security. ## Checklist - Define public and restricted content before deployment. - Verify the backend listener's actual exposure. - Review pages, uploads and external resource requests. - Protect and test recovery of service-key material. - Separate client authorisation from application roles. - Test maintenance and reader journeys through the onion path. ## Frequently asked questions ### Does onion hosting make an application anonymous by itself? No. Published content, configuration, accounts and operational practices can reveal information. Review the entire service rather than relying on the connection method. ### Should every onion site use client authorisation? No. Decide from the intended audience. Client authorisation restricts connection access and adds a credential lifecycle; application permissions remain separate. ### What must I protect in a recovery copy? Site data and configuration need appropriate access controls. Any included service-key material is especially sensitive and must remain private during storage and restoration. ## Primary sources - [Tor Project: Set up your onion service](https://community.torproject.org/onion-services/setup/) - [Tor Project: Advanced onion-service settings](https://community.torproject.org/onion-services/advanced/) - [Tor Project: Client authorisation](https://community.torproject.org/onion-services/advanced/client-auth/) ## Related infrastructure - [Veil Onion](https://swissoctet.com/services/veil/index.txt): A hosting configuration built around onion services, with capacity adapted to your project. - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Vault Storage](https://swissoctet.com/services/vault/index.txt): Room for media, archives and growing datasets. A storage-focused Linux configuration. ## Related guides - [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/index.txt): Compare application requirements, control and maintenance responsibilities rather than treating a VPS as the automatic next step for every website. - [A domain, DNS and TLS cutover runbook for a new server](https://swissoctet.com/insights/dns-tls-cutover-runbook/index.txt): Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. --- # Choose the asset and network before preparing a crypto payment > Read a payment route as a complete asset-and-network pair, then verify invoice instructions, token identity and the amount delivered before authorising a transfer. Canonical human page: https://swissoctet.com/insights/choose-crypto-asset-network/ SwissOctet Editorial. Topic: crypto. Level: Foundation. Reading time: 4 minutes. ## Direct answer Match the invoice's asset, network, receiving address and amount as one instruction. A token symbol or familiar address format is insufficient. Check the sending wallet's network and fee behaviour before authorising a transfer, and use only a payable invoice from a verified, connected order service. ## Treat the network as part of the asset choice The same token name can appear on more than one blockchain. That does not make every route interchangeable. USDT on Ethereum and USDT on TRON are separate payment instructions, even when a wallet displays the same asset symbol. The receiving service must explicitly support the selected network and the actual token used on that network. Start from the invoice, not from the cheapest network offered by a withdrawal screen. If the sending service uses a different label or provides several versions of an asset, resolve that difference before sending. An unsupported network is not corrected merely because the address looks familiar or the token has the intended name. ## Read the catalogue's routes precisely SwissOctet lists six assets across seven routes because USDT has two network choices. Use the complete invoice instructions for the actual order and verify the selected route before sending funds. A catalogue or receiving address alone does not authorise a transfer. The table preserves the route distinction without displaying a receiving address out of an invoice context. A live invoice must provide the exact network and destination for the selected order. Other networks offered by a wallet or exchange are not automatically supported just because the asset also exists there. | Asset | Network in the checkout design | Selection to keep distinct | | --- | --- | --- | | BTC | Bitcoin | Native BTC route | | ETH | Ethereum | Native ETH route | | USDT | TRON | TRC-20 token route | | USDT | Ethereum | ERC-20 token route | | USDC | Ethereum | ERC-20 token route | | SOL | Solana | Native SOL route | | LTC | Litecoin | Native LTC route | ## Verify token identity, not only its ticker Ethereum's ERC-20 documentation describes an interface for fungible tokens, while TRON documents its TRC-20 standard. A standard defines how a token can behave; it does not establish that a particular token with a familiar symbol is the intended asset. The issuer's official information and the invoice's configured token identity matter to an integration. Tether publishes supported protocols and contract information for its tokens. If your wallet identifies a token through a contract or offers several similarly named assets, compare that information with the official issuer and the invoice's required asset. Investigate any warning before proceeding. Do not replace the payment instructions with a contract address copied from a search result or message. ## Read fees from the sending side The amount entered in a wallet or exchange can differ from the amount delivered when fees are deducted from a withdrawal. Review the final confirmation screen and the service's fee handling. A real invoice states the required receiving amount; the sender must make sure that amount, rather than only the entered amount, will arrive under the specified route. For self-custody token transfers, network fees may require the network's native asset. Ethereum documents gas as the mechanism for paying computational work on its network. Do not confuse the token being sent with the asset used to pay a network fee. Check current wallet instructions and available balances rather than assuming a token balance alone is sufficient. ## Verify the complete instruction before approval Read the asset, network, destination, amount and invoice expiry together. Verify the destination in a way appropriate to the wallet, because copied text can be altered or mistaken. A QR code is a convenient representation, not independent proof that an invoice is legitimate. Keep your order reference and access token private while checking the details. Use an illustrative USDT order to practise the review without moving funds. The invoice specifies Ethereum, but the withdrawal screen initially defaults to TRON. The correct response is to select and verify the invoice's route or stop to resolve the mismatch. Sending on the default network and hoping for recovery is not a payment procedure. ## Handle expiry and uncertainty deliberately A quote can have an expiry and a policy for late or partial transfers. If you have not sent the payment, obtain a current invoice when the instructions expire. If you have already sent it, preserve the transaction reference and request reconciliation through the order process. Do not start repeated transfers simply because a screen has not updated. Differentiate the wallet's local status from the receiving service's verified state. A broadcast transfer, an included transaction and an accepted order are different events. Keep the transaction reference, asset and network available for a technical inquiry, but never share seed phrases, private keys or a wallet recovery file. Those are not required to identify a public transfer. ## Keep the payment decision bounded This process is about matching a transfer to a valid invoice, not selecting assets as investments or promising privacy from a public ledger. A no-KYC order flow limits identity-document collection; it does not erase transaction history or information disclosed through account use. Keep personal and technical information proportionate to the actual order need. Review the invoice's complete instructions and follow verified order status. Keep the transaction reference if you need assistance. Do not send a second transfer simply because a confirmation screen is taking time to update. ## Checklist - Use a payable invoice from the connected order service. - Match asset and network as one route. - Check token identity through official issuer information. - Verify the amount delivered after sending-side fees. - Review address, amount and expiry together. - Preserve the public transaction reference without sharing wallet secrets. ## Frequently asked questions ### Can I send USDT on any network if the symbol is the same? No. Use the exact network and token route specified by the invoice. Similar names do not make different blockchain transfers interchangeable. ### Does a QR code prove that the payment instructions are valid? No. It encodes information. Verify the invoice, asset, network, destination and amount before authorising a transfer. ### Should I resend if the order screen remains pending? Preserve the transaction reference and use the reconciliation process first. A delayed display is not proof that the transfer failed or needs duplication. ## Primary sources - [Ethereum: ERC-20 token standard](https://ethereum.org/developers/docs/standards/tokens/erc-20/) - [TRON: TRC-20 standard](https://developers.tron.network/docs/trc20) - [Tether: Supported protocols](https://tether.to/en/supported-protocols/) - [Ethereum: Gas and fees](https://ethereum.org/developers/docs/gas/) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Canvas Web](https://swissoctet.com/services/canvas/index.txt): A clean foundation for websites and publishing. Pick your storage, domains and hosting options. - [Shield VPN](https://swissoctet.com/services/shield/index.txt): A Swiss OpenVPN configuration for one device, with AES-256 encryption and unlimited traffic. ## Related guides - [Crypto checkout and the limits of payment privacy](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/index.txt): Understand the asset, network and confirmation journey, and protect the information that connects your project to a payment. - [From detected transaction to reconciled order: confirmations and reorgs](https://swissoctet.com/insights/confirmations-reorgs-order-reconciliation/index.txt): Design payment states around verified chain evidence, explicit acceptance rules and unambiguous order association rather than a browser claim that funds were sent. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. --- # From detected transaction to reconciled order: confirmations and reorgs > Design payment states around verified chain evidence, explicit acceptance rules and unambiguous order association rather than a browser claim that funds were sent. Canonical human page: https://swissoctet.com/insights/confirmations-reorgs-order-reconciliation/ SwissOctet Editorial. Topic: crypto. Level: Advanced. Reading time: 4 minutes. ## Direct answer Transaction detection, chain confirmation, order association and service delivery are separate steps. Verify the correct chain, asset, recipient and amount; apply a documented acceptance policy; and make reconciliation idempotent. A transaction reference, screenshot or browser button alone cannot establish that a specific order has been paid. ## Separate the chain event from the order event A wallet reporting that a transfer was sent is evidence about its own action, not a complete payment decision. The receiving backend must observe the intended network, verify the actual transfer and associate it with an order. Only then can the order apply its acceptance policy. Infrastructure delivery is another operational step after payment acceptance. Keep these transitions explicit in both code and customer language. A screen can show waiting, detected or confirming without calling the order paid. Do not let the browser supply the accepted amount or overwrite an authoritative status. Store the server-created quote and its instructions so later reconciliation can be assessed against the original order rather than a changing cart. ## Use chain-specific confidence rules Different networks describe transaction confidence differently. Bitcoin's developer guide explains how nodes select the chain with the most accumulated proof of work and how competing blocks can occur. A transaction seen recently therefore needs a policy for confirmation depth and possible chain changes. There is no single confirmation count appropriate to every asset and commercial risk. Ethereum's proof-of-stake documentation explains checkpoint finality, while Solana documents processed, confirmed and finalized commitment states. Do not translate those terms casually into one universal block count. Record the network-specific rule, information source and behaviour during uncertainty. The operator should determine acceptance thresholds against the payment and delivery risk, not copy a number from an unrelated checkout. ## Verify the actual transfer payload Identify the recipient, asset and amount on the correct chain. Token payments need the intended token identity, not merely a successful transaction to an address. Verify relevant execution success and transfer evidence according to the chain's model. Parse integer amounts at the asset's proper precision instead of trusting a formatted decimal supplied by the browser. A payment instruction must remain bound to its original route. A transfer on another network, a different token with the same symbol or an unrelated transaction reference should not satisfy it. The verification record should explain what was checked and preserve the evidence needed to review the decision. This guide describes general payment-reconciliation principles rather than a particular service implementation. ## Make order association unambiguous Fixed receiving addresses can receive several orders with similar amounts. The existence of a matching transfer does not prove which customer or order should receive credit. Define the association method before accepting live payments and include handling for collisions. A user-supplied transaction reference still requires validation that the same transfer has not already been assigned elsewhere. Imagine two invoices for the same amount on the same route during an overlapping window. A watcher sees one transfer. Automatically marking both paid is wrong; choosing one without enough evidence is also unsafe. Keep the transfer unallocated or in review until the operator's policy can establish a valid association. An ambiguous match is a state to handle, not a reason to fabricate certainty. ## Define states that tolerate late and changing evidence A payment process benefits from a small set of clear states, with chain evidence separate from the decision to accept an order. This illustrative table explains possible stages rather than describing a particular service's status names. Each transition should have a verified reason, and payment acceptance should remain distinct from infrastructure delivery. Include late, partial and excess transfers, quote expiry and temporarily unavailable chain data. Expiry does not make a real transfer disappear. A late payment may require review rather than automatic acceptance or rejection. If a previously observed chain event changes, re-evaluate the state under the documented policy instead of treating every watcher notification as irreversible truth. | Illustrative state | Meaning | Next decision | | --- | --- | --- | | Awaiting | No verified qualifying transfer | Continue observing valid invoice | | Detected | Relevant transfer observed | Check chain confidence and association | | Confirming | Acceptance rule not yet met | Observe until policy permits decision | | Review | Late, partial or ambiguous evidence | Resolve under operator policy | | Accepted | Verified and reconciled payment | Proceed to separate delivery workflow | ## Make retries safe and observable Watchers and reconciliation jobs will retry after interrupted connections or process restarts. Use a stable transfer identity, such as the chain and the appropriate transaction or transfer identifier, to prevent duplicate credits. Persist progress and decisions so the same event can be processed again without provisioning a second service or changing an accepted quote. Distinguish an unknown result from a failed operation. If a downstream request times out, inspect its authoritative result before resubmitting. Keep durable records of accepted and uncertain actions. Restrict access to order tokens and internal evidence while retaining enough information to investigate a disputed payment. Reliability here is about repeatable decisions, not a smooth animation in the checkout. ## Know what a pending order still needs An order may remain pending because the transfer has not been observed, the required chain confidence has not been reached or its association with the invoice needs review. Preserve the invoice and public transaction reference, check the stated acceptance rules and use the order's intended assistance process. A delayed status update is not, by itself, a reason to send another payment. Follow the instructions and verified status for the actual order. Payment confirmation should identify acceptance of the reconciled transfer, while service delivery has a separate status. Keep private access tokens and wallet secrets out of requests for help. ## Checklist - Persist an immutable server-created quote. - Verify chain, recipient, asset and integer amount. - Document chain-specific acceptance rules. - Handle fixed-address collisions without guessing. - Prevent duplicate credits and unsafe retry submissions. - Test late, partial, wrong-route and changed-evidence cases. ## Frequently asked questions ### Is a transaction hash enough to confirm payment? No. Verify the transfer on the intended chain, its payload and confidence, then establish that it belongs to the order and has not already been credited. ### Can every network use the same confirmation threshold? No. Networks expose different confidence and finality models. The operator must define and test an acceptance policy appropriate to each route. ### Does confirmed payment mean the server is provisioned? No. Payment acceptance and delivery are separate workflow events. Communicate provisioning status from its own authoritative process. ## Primary sources - [Bitcoin developer guide: Blockchain behaviour](https://developer.bitcoin.org/devguide/block_chain.html) - [Ethereum: Proof of stake and finality](https://ethereum.org/developers/docs/consensus-mechanisms/pos/) - [Solana: RPC state commitment](https://solana.com/docs/rpc) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Metal Hyper](https://swissoctet.com/services/metal-hyper/index.txt): High-capacity dedicated configurations for intensive applications and larger deployments. - [Veil Onion](https://swissoctet.com/services/veil/index.txt): A hosting configuration built around onion services, with capacity adapted to your project. ## Related guides - [Crypto checkout and the limits of payment privacy](https://swissoctet.com/insights/crypto-checkout-and-operational-privacy/index.txt): Understand the asset, network and confirmation journey, and protect the information that connects your project to a payment. - [Choose the asset and network before preparing a crypto payment](https://swissoctet.com/insights/choose-crypto-asset-network/index.txt): Read a payment route as a complete asset-and-network pair, then verify invoice instructions, token identity and the amount delivered before authorising a transfer. - [How to choose a VPS without guessing](https://swissoctet.com/insights/choose-a-vps-by-workload/index.txt): Turn an application idea into a useful resource budget, then compare CPU, memory, storage and transfer together. --- # Build monitoring that leads to a useful incident response > Connect application symptoms, actionable alerts and a small response playbook so that an operator can make clear decisions when a service degrades. Canonical human page: https://swissoctet.com/insights/monitoring-incident-response-playbook/ SwissOctet Editorial. Topic: operations. Level: Applied. Reading time: 4 minutes. ## Direct answer Monitor the user-visible function, add enough resource and application evidence to diagnose it, and page only for conditions that require timely human action. Pair each alert with an owner, a first step and escalation. During an incident, coordinate mitigation, protect evidence and verify recovery through the actual user journey. ## Begin with the function that matters A server responding to a ping does not establish that its application works. Choose a representative, harmless user journey, such as retrieving a public page or accessing a controlled test endpoint. Define what success looks like and avoid synthetic checks that create real orders, publish content or send customer notifications during every run. Monitor from an appropriate outside perspective as well as inside the application. External observation can reveal access or routing problems the server does not see. Internal measurements can explain why the journey failed. Keep both views connected to the function rather than collecting a large dashboard simply because every metric is available. ## Choose signals with diagnostic value Google's SRE guidance highlights latency, traffic, errors and saturation as useful signals for user-facing systems. Use them to describe behaviour: response time, request volume, unsuccessful requests and pressure on constrained resources. Select measurements appropriate to the application rather than assuming one metric definition works for a website, a transfer service and a background worker. Separate successful and failed request behaviour where it matters, and examine slow-tail results rather than averages alone. Add memory pressure, disk space, queue depth or application-specific limits when they explain the service. A high CPU reading can be normal during useful batch work; the user-visible effect determines whether immediate action is needed. ## Give every alert an action and an owner An alert should state the affected function, observed condition and useful first check. Assign an owner and an escalation path before deploying it. Distinguish conditions requiring a prompt interruption from items suitable for a scheduled review. Repeated low-value pages train operators to ignore the system and make important signals harder to recognise. Use a small alert review to remove ambiguity. This illustrative table describes potential monitoring decisions, not SwissOctet support coverage or an availability commitment. Thresholds need to be tested against the actual application's baseline. Include a recovery condition so the operator knows when the alert has cleared and what still needs validation. | Observed condition | Useful response | Context to include | | --- | --- | --- | | Representative user journey fails | Assess impact and mitigate | Affected endpoint, duration and recent change | | Disk approaching a planned limit | Review growth and retention | Volume, growth rate and safe headroom | | Backup verification fails | Protect the recovery route | Job, last usable point and error | | Latency rises during a release | Inspect or roll back the change | Baseline, release time and affected requests | ## Prepare a small incident structure A response process should be understandable under pressure. Name a coordinator, someone handling technical work and someone responsible for updates when the incident is large enough to need distinct roles. A small project may combine roles, but it still benefits from one clear decision point. Agree a communication channel before the service fails. Google's incident-response material stresses coordination and a mitigation-first approach. Apply that at a scale that fits the project: establish the impact, choose safe actions and avoid several operators making conflicting changes. Record a timeline and decisions. Searching for a perfect explanation should not delay a safe measure that restores the affected function. ## Walk through a concrete degradation Imagine a site becoming slow after a release. An external check shows increased completion time, while internal measurements show application errors and growing database work. The coordinator declares a bounded incident, protects the evidence and assigns one person to compare the release with the baseline. Another prepares the tested rollback path rather than making unrelated infrastructure changes. If rollback is safe for the application's data state, use it and observe the result. If it is not safe, choose a narrower mitigation supported by the operating plan. Document what changed and when. A larger VPS or port may be worth evaluating later, but the immediate decision should address the evidence instead of assuming the infrastructure size is the cause. ## Protect evidence and verify recovery Operational logs and incident notes may contain addresses, identifiers and customer information. Collect what the investigation needs, limit access and keep credentials or private order tokens out of shared reports. For a suspected security incident, preserve appropriate evidence and follow the project's response policy rather than destroying information through hurried cleanup. NIST's incident-response guidance places response within broader cybersecurity risk management. Recovery includes checking the intended function and resolving the condition that made the incident possible. Test the user journey, review resource behaviour and check background work before closing the response. A cleared alert or restarted process alone may not demonstrate a complete return to useful service. ## Turn the incident into a measurable improvement Write a short review of impact, timeline, contributing conditions and the actions taken. Focus on changes that can be verified: improve a check, correct a permission, rehearse rollback or add a missing recovery dependency. Assign owners and completion criteria. Avoid a long list of vague intentions that no one can later confirm were implemented. When deploying on SwissOctet, plan monitoring and response as part of the application's operation, separate from the selected hardware and any confirmed management arrangement. The catalogue does not establish a staffed incident team or continuous support hours. Decide who receives alerts, who can act and what the actual service terms cover before relying on a production environment. ## Checklist - Monitor a harmless representative user journey. - Choose signals that explain application behaviour. - Give alerts an action, owner and recovery condition. - Agree coordination and escalation before an incident. - Protect evidence and verify the complete recovery. - Assign testable improvements after the review. ## Frequently asked questions ### Is server uptime monitoring sufficient? No. A reachable machine can host a broken application. Monitor the function users depend on and add resource evidence to diagnose failures. ### Should every metric threshold page someone immediately? No. Reserve urgent interruptions for actionable conditions requiring timely attention. Route lower-priority work into a review process with a clear owner. ### When is an incident finished? After the affected function and relevant background work are verified, immediate risks are handled and follow-up actions are recorded. A process restart alone is insufficient. ## Primary sources - [Google SRE: Monitoring distributed systems](https://sre.google/sre-book/monitoring-distributed-systems/) - [Google SRE Workbook: Incident response](https://sre.google/workbook/incident-response/) - [NIST SP 800-61 Rev. 3: Incident response](https://csrc.nist.gov/pubs/sp/800/61/r3/final) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Metal Atlas](https://swissoctet.com/services/metal-atlas/index.txt): Dedicated compute with more memory and storage headroom for established workloads. - [Transit 40](https://swissoctet.com/services/transit-40/index.txt): Dedicated configurations with a 40 Gbps port for bandwidth-intensive applications. ## Related guides - [Build a backup you can actually restore](https://swissoctet.com/insights/build-a-backup-you-can-restore/index.txt): Choose a recovery target, protect an independent copy and practise the restoration before an incident forces the issue. - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. --- # Give your AI workers a bounded place to run > Separate model inference from orchestration, size the actual worker and limit what its tools can change before putting an AI workflow on a server. Canonical human page: https://swissoctet.com/insights/give-ai-workers-a-bounded-runtime/ SwissOctet Editorial. Topic: compute. Level: Applied. Reading time: 4 minutes. ## Direct answer An AI workflow needs resources for its actual tools and concurrency, and permissions that remain enforceable outside the model. Remote inference and local inference lead to different CPU, memory, storage and GPU decisions. ## Name the job before choosing a machine An AI worker combines a model with software that receives tasks, gathers context and calls tools. A scheduled document classifier, an internal search assistant and a browser-driven workflow have different operating needs. Write down the input, the expected output, the systems it may contact and the point where a person approves a consequential action. This small specification tells you more about the host than the label agent. Start with one repeatable job and a narrow account. A worker that drafts a response needs less authority than one that sends it. Keep those stages separate in the application. The server should support the approved workflow without turning every generated instruction into an executable operation. Completion means a verified result or a clear failure state, rather than an indefinitely running loop. ## Separate a remote model from a local model When the model runs behind an external API, the VPS mainly hosts the queue, application, tools and persistent state. Its memory demand comes from those processes, including any browsers or document parsers. A GPU on this machine does not accelerate a model running elsewhere. Record which content crosses the API boundary and evaluate that provider independently from the location of the worker. Local inference adds model storage, model memory and runtime compatibility to the budget. Inference tools such as Ollama expose information about CPU or GPU placement and concurrent requests. Test the chosen model, context length and concurrency together. A larger context or more simultaneous jobs can raise memory demand; a model file size alone is an incomplete sizing method. Check the runtime's supported hardware before selecting a GPU configuration. | Worker pattern | Main resource question | Boundary to review | | --- | --- | --- | | Remote model API | Application and tool memory | Content sent to the model provider | | Local model | Model, context and working memory | Runtime and device compatibility | | Browser workflow | Peak browser processes and temporary files | Web content and permitted actions | ## Measure a representative queue Prepare a small set of tasks with normal and unusually large inputs. Measure peak memory, elapsed processing time, temporary storage and the number of external calls. Include failure cases: an unavailable API, a malformed document and a tool timeout. These measurements are a planning exercise for your software, not a benchmark or performance promise for a SwissOctet plan. Set a maximum number of active jobs and a maximum execution time. Queue work that cannot start safely and reject overload in a predictable way. Retrying every failure immediately can multiply both server pressure and API spending. Use a bounded retry policy and an identifier that prevents the same completed action being applied twice. Reserve capacity for the operating system, monitoring and maintenance while jobs are active. ## Give tools less authority than the worker's ambition Documents and web pages supplied to a model can contain instructions intended to redirect it. Treat retrieved content as input, not as a source of operating permission. OWASP's guidance on prompt injection recommends several layers of control, including restricted tools and checks around sensitive actions. Put permissions in the tool implementation and the operating environment, where the model cannot rewrite them through a response. Use separate credentials for separate jobs, with access only to the records or directories each needs. Prefer structured parameters over model-generated shell commands. Validate file destinations and outbound targets. Require a deliberate approval boundary for sending messages, publishing changes or modifying important records. A read-only research worker and a production administrator should never inherit the same credentials merely because both run on one host. ## Keep resource controls and recovery explicit Containers can organise dependencies and process boundaries, but they need deliberate configuration. Docker documents that containers have no resource limits by default. Set appropriate memory and CPU limits, use an unprivileged process where supported and mount only the required data. Keep model endpoints and administration interfaces restricted rather than exposing them simply to make initial testing convenient. Persist the task state separately from temporary working files. Record enough information to recognise completed work after a restart without storing every prompt forever. Protect credentials from logs and generated artifacts. Define retention for inputs, outputs and diagnostic data. A recovery test should restart the worker and verify that unfinished jobs resume safely, completed jobs remain completed and failures remain visible to the operator. ## Make the first deployment an acceptance test Run the narrow workflow with synthetic or approved sample data before granting wider access. Check useful output, permissions, queue behaviour and recovery from a failed dependency. Observe the whole process, including browser children and data downloads. If the model is local, include a cold start and the intended number of concurrent requests in the test. Use Vector or Pulse as a specification shortlist for ordinary workers, and compare Tensor only when the inference runtime needs suitable GPU resources. Confirm compatibility and availability before a real order. Expand the worker's permissions only after its behaviour can be reviewed. The aim is a service with a clear operating envelope, a measurable resource budget and a straightforward way to stop and recover work. ## Checklist - Describe one job and its approval boundary. - Separate remote API processing from local inference. - Measure tools, browsers and peak concurrency. - Apply time, resource and permission limits. - Test restarts without duplicating completed actions. ## Frequently asked questions ### Does every AI worker need a GPU? No. A worker calling a remote model API usually needs resources for orchestration and tools. Local inference has separate hardware and runtime requirements. ### Does a container make an autonomous workflow safe? No. Configure its permissions, mounts, network access and resource limits, and check consequential tool actions outside the model. ### Does hosting the worker in Switzerland keep every prompt there? No. Remote model APIs and other integrations may process content elsewhere. Map those dependencies explicitly. ## Primary sources - [Docker: Resource constraints](https://docs.docker.com/engine/containers/resource_constraints/) - [OWASP: LLM Prompt Injection Prevention](https://cheatsheetseries.owasp.org/cheatsheets/LLM_Prompt_Injection_Prevention_Cheat_Sheet.html) - [Ollama: Runtime and concurrency FAQ](https://docs.ollama.com/faq) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [Tensor GPU](https://swissoctet.com/services/tensor/index.txt): Dedicated GPU configurations for accelerated compute, rendering and machine-learning workloads. ## Related guides - [Size VPS CPU and memory from a real workload](https://swissoctet.com/insights/size-vps-cpu-and-memory/index.txt): Build a memory budget, inspect contention and separate one busy thread from work that can use several virtual cores. - [Build a GPU VRAM budget before choosing hardware](https://swissoctet.com/insights/gpu-vram-budget-for-real-workloads/index.txt): Account for weights, activations, caches and temporary buffers, then test the peak workload rather than the model file alone. - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. --- # Choose a hosting operating model before choosing a cloud > Compare shared hosting, a VPS, dedicated hardware and large cloud platforms through responsibility, recovery, dependencies and the complete operating budget. Canonical human page: https://swissoctet.com/insights/choose-a-hosting-operating-model/ SwissOctet Editorial. Topic: hosting. Level: Applied. Reading time: 4 minutes. ## Direct answer Compare hosting models through the operational responsibilities they assign and the architecture they enable. Cloud scale, a virtual machine and dedicated hardware describe different aspects of a system; none alone proves privacy, cost or recovery behaviour. ## Start with the work you need someone to own A hosting decision assigns operational work as well as computing resources. One project needs an account that runs a conventional website; another needs control over operating-system packages and background processes. A third needs a database platform whose maintenance is handled under a specific service contract. List those responsibilities first, along with the people available to maintain them. Shared hosting typically exposes an account-level environment. A VPS exposes a guest operating system, while dedicated hardware moves the machine boundary to a physical server. Managed is a separate question: a product label does not tell you who applies patches, restores data or investigates an incident. Ask for the scope of management and a recovery procedure instead of treating it as a universal feature. ## Understand what cloud adds to the comparison NIST describes cloud computing through characteristics such as on-demand access, resource pooling, elasticity and measured service. A virtual machine can be one component of a cloud platform, so VPS and cloud are not mutually exclusive technologies. The useful comparison is between the particular services offered: a fixed virtual machine, an elastic fleet or an application built around managed services. Hyperscaler is an industry term for a provider operating infrastructure and service platforms at very large scale. That scale can offer a wide range of deployment tools and geographic choices; it does not tell you whether a particular architecture meets your needs. Evaluate the region, service dependencies, identity model and contract of each component. A smaller provider and a large platform both require a clear account of where data goes. | Operating model | Control available to the project | Question before choosing | | --- | --- | --- | | Shared hosting account | Site settings within the account scope | Does the runtime fit the application? | | Virtual machine | Guest OS and installed services | Who maintains and restores the guest? | | Dedicated machine | A physical server boundary | Does the workload justify this boundary? | | Managed cloud service | The service API and supported settings | What remains the customer's responsibility? | ## Choose an architecture that can recover A single machine can be a sensible starting point for a small application when its recovery requirements allow restoration or a planned maintenance window. Adding a second application node changes the design only if traffic routing, sessions and persistent data work correctly across both. Two servers running the same incomplete recovery plan are still an incomplete recovery plan. Distributed storage illustrates this distinction. Software such as Ceph spreads storage work across a cluster and offers object, block and file interfaces. Replication or erasure coding may help tolerate particular hardware failures, but the cluster also needs capacity for recovery and rebalancing. A distributed live copy does not replace an independent backup. Decide how writes behave during a network partition and test the failure cases relevant to your chosen implementation. ## Compare the full operating budget Write the budget as a workload: normal traffic, a busy interval, stored data, backup retention and transfer needed for recovery. Include paid software, external APIs, administration time and the cost of moving the data again. A starting monthly figure and a usage-based estimate answer different questions. Compare them over the same period and keep the assumptions alongside the result. For a large cloud platform, identify every service required to keep the application running. For a VPS, include the work that managed services would otherwise absorb. Neither approach is automatically cheaper. Begin with a small representative deployment or a documented quote, then review the actual bill against the model. Reserve room for recovery traffic and temporary migration capacity rather than budgeting only the steady state. ## Treat privacy as a dependency map The machine's region is one entry in a broader map. Authentication, monitoring, support tools, backups and model APIs may operate through separate services. Record what each receives, who can access it and how long it is retained. AWS's shared-responsibility model is one example of a provider explicitly separating its infrastructure duties from customer duties; the scope changes with the service. Use that distinction when comparing providers without importing one provider's obligations into another contract. A SwissOctet configuration describes a hosting location and listed resources. It does not establish the location of integrations you add later. Minimise the data each dependency receives, secure administration and verify the backup destinations before making a statement about your own application's data journey. ## Use the migration path as part of the decision Check how you can export application data, configuration and identities. A conventional application on a virtual machine may be straightforward to move, while a service-specific database or event system may require an adaptation. Portability also depends on operational knowledge: a backup nobody knows how to restore is a weak exit plan even if its format is open. For a first SwissOctet shortlist, compare Canvas when an account-level web environment fits, Vector for guest OS control and Metal ranges when the physical boundary matters. Storage-oriented options support a different capacity question and should not be described as a managed distributed cluster. Keep the architecture small enough to operate, and add platform complexity when it addresses a tested requirement rather than an imagined future scale. ## Checklist - Assign administration and recovery ownership. - Distinguish a VM from the wider cloud platform. - Budget dependencies, transfer and maintenance. - Test a failure boundary before adding nodes. - Record a workable data export and migration path. ## Frequently asked questions ### Can a VPS be part of a cloud platform? Yes. A virtual machine can be a cloud service. Compare the actual resource, scaling and management model rather than assuming the names describe exclusive technologies. ### Does distributed storage replace backups? No. Live redundancy addresses selected component failures. An independent backup and a restoration test address other failures such as deletion and damaged application data. ### Is a large cloud always a poor privacy choice? No. Assess the specific services, data flows and contractual controls. Provider size alone does not establish the suitability of the architecture. ## Primary sources - [NIST SP 800-145: The Definition of Cloud Computing](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf) - [AWS: Shared Responsibility Model](https://aws.amazon.com/compliance/shared-responsibility-model/) - [Ceph: Storage Architecture](https://docs.ceph.com/en/latest/architecture/) - [Ceph: Erasure coding](https://docs.ceph.com/en/latest/rados/operations/erasure-code/) ## Related infrastructure - [Canvas Web](https://swissoctet.com/services/canvas/index.txt): A clean foundation for websites and publishing. Pick your storage, domains and hosting options. - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Metal Origin](https://swissoctet.com/services/metal-origin/index.txt): A practical entry to dedicated hardware. Your workload, on its own physical machine. - [Vault Storage](https://swissoctet.com/services/vault/index.txt): Room for media, archives and growing datasets. A storage-focused Linux configuration. ## Related guides - [Web hosting or a VPS: choose the work you want to own](https://swissoctet.com/insights/web-hosting-or-your-own-vps/index.txt): Compare application requirements, control and maintenance responsibilities rather than treating a VPS as the automatic next step for every website. - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [Object, file or block storage: choose the interface your application needs](https://swissoctet.com/insights/object-file-block-storage/index.txt): Distinguish storage interfaces, access semantics and operational responsibilities before turning a capacity requirement into an application architecture. --- # Choose a traffic path: server, tunnel or proxy > Understand what a VPS, VPN and proxy each change, then select routing, protocols and operating responsibilities from the connection you actually need. Canonical human page: https://swissoctet.com/insights/choose-a-server-tunnel-or-proxy/ SwissOctet Editorial. Topic: network. Level: Foundation. Reading time: 4 minutes. ## Direct answer A VPS supplies a machine; a VPN supplies a configured tunnel; a proxy relays selected traffic. Match the role to the requirement and verify routing, trust and failure behaviour rather than treating the labels as privacy guarantees. ## Draw the connection you want to change A VPS is a machine you can use to run software. A VPN creates a protected network path between participating endpoints. A proxy handles traffic on behalf of a client or service. These roles can coexist: a VPS may host a VPN or proxy, but buying a server does not configure either one. Start with a simple diagram of the client, destination and intermediate systems. If the requirement is to publish a website, you need a hosting environment and an application. If the requirement is private access to an administration network, a tunnel may be part of the design. If one application must connect through a controlled intermediary, a proxy may fit. Choosing by role keeps you from expecting a hosting product to change the traffic of a device automatically. ## A tunnel protects a specific leg of the journey A VPN encrypts traffic within its configured tunnel; routing determines which traffic enters that tunnel. A full-tunnel configuration and a split-tunnel configuration have different effects. Review DNS handling, IPv6 routes and the behaviour when the tunnel becomes unavailable. Test those paths on the actual client rather than assuming an installation screen proves all traffic follows the intended route. The tunnel endpoint becomes part of the trust model. After traffic exits, its protection depends on the next connection and application protocol, including HTTPS where used. A VPN does not remove website accounts, browser identifiers or information you submit. It also does not correct a compromised device. Evaluate access control and the endpoint operator alongside the protocol, and keep claims about anonymity separate from a verified routing result. ## A proxy has a narrower and configurable scope A forward proxy receives client connections and makes onward connections according to its configuration. HTTP and SOCKS proxies present different interfaces, and applications must support or be configured for the chosen one. A proxy does not inherently encrypt every connection from the device. The connection to the proxy and the onward connection must be evaluated separately. A reverse proxy sits in front of a service and receives requests from its users. It can route to internal application processes and handle public HTTP settings. This is an operator-facing architecture decision rather than a substitute for a client VPN. Avoid creating an unauthenticated open proxy: allow only the users and destinations required for your legitimate workflow and monitor failures without retaining unnecessary browsing data. | Component | Primary role | What it does not establish | | --- | --- | --- | | VPS | Runs an operating system and applications | A configured tunnel for your device | | VPN tunnel | Carries selected network traffic between peers | An anonymous identity at the destination | | Forward proxy | Relays supported client traffic | Protection for every device connection | | Reverse proxy | Receives requests on behalf of an application | Application correctness or unlimited attack capacity | ## Select a protocol from the endpoints and policy WireGuard uses UDP and a defined cryptographic design with public-key peer configuration. OpenVPN's documented deployment options include routed tunnels, certificates and TCP or UDP transports. IPsec describes protection at the IP layer and commonly appears with a key-management system such as IKE. These are technical families with different deployment choices, not a universal speed ranking. Check client support, key rotation, how users are removed and what the networks between peers permit. A design for a site-to-site link may differ from remote access for staff devices. Test reachability and throughput using representative endpoints and permitted traffic. Record the protocol and conditions with the result. A faster result in one environment does not prove that the same protocol is the best fit everywhere. ## Self-hosting transfers work to you Running a tunnel on your own server gives you responsibility for updates, keys, firewall rules and availability. Restrict the administration interface, protect backups of configuration and decide how a lost device's access is revoked. A single server creates a clear dependency: if it stops working, the route it provides stops working too. Plan recovery before relying on it for your only administration path. Write a logging policy that you can actually implement. Keeping few logs can reduce stored information, but it can also limit incident investigation. Do not infer a no-logs policy from the presence of a VPN protocol or a server location. Monitor service health without recording more user activity than necessary. Keep credentials and private keys outside public application directories and generated configuration examples. ## Verify the whole path before choosing a plan Test DNS resolution, the public address seen by an approved test destination and access to the resources that should remain private. Disconnect the tunnel and confirm the intended fallback behaviour. Repeat on the devices and networks your users will employ. For a proxy, test an application that uses it and one that does not, so its scope is visible. Shield is the SwissOctet VPN service family; Vector or dedicated ranges are separate hosting choices for software you administer. Read their listed options and confirm the required capability before ordering. Select capacity from expected traffic, concurrent sessions and measured endpoint resources. The right route is the one whose scope, permissions and failure behaviour match the project, with responsibilities that you are ready to maintain. ## Checklist - Draw clients, intermediaries and destinations. - Decide which traffic enters the tunnel or proxy. - Check DNS, IPv6 and disconnected behaviour. - Select protocols from support and policy requirements. - Plan key revocation, updates and endpoint recovery. ## Frequently asked questions ### Can I run a VPN on a VPS? Yes, if the operating environment supports your chosen software and networking requirements. You remain responsible for its configuration, maintenance and keys. ### Does a proxy encrypt all traffic? No. Protection depends on the protocol and configuration of each connection. Applications outside its scope may connect directly. ### Which VPN protocol is always fastest? There is no universal result. Client hardware, transport, path and configuration matter. Measure the intended deployment and consider support and access policy too. ## Primary sources - [WireGuard: Protocol and Cryptography](https://www.wireguard.com/protocol/) - [OpenVPN: Community deployment guide](https://openvpn.net/community-docs/how-to.html) - [RFC 4301: Security Architecture for the Internet Protocol](https://www.rfc-editor.org/rfc/rfc4301) - [NGINX: HTTP proxy module](https://nginx.org/en/docs/http/ngx_http_proxy_module.html) ## Related infrastructure - [Shield VPN](https://swissoctet.com/services/shield/index.txt): A Swiss OpenVPN configuration for one device, with AES-256 encryption and unlimited traffic. - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Metal Origin](https://swissoctet.com/services/metal-origin/index.txt): A practical entry to dedicated hardware. Your workload, on its own physical machine. ## Related guides - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. - [A practical threat model for your hosted project](https://swissoctet.com/insights/threat-model-a-hosted-project/index.txt): Map assets and trust boundaries, choose a few realistic failure scenarios and turn them into controls you can test. - [Separate your public web edge from the application](https://swissoctet.com/insights/separate-the-web-edge-from-the-app/index.txt): Give the web server, reverse proxy and application distinct responsibilities, with deliberate origin access, TLS, request limits and an incident path. --- # Understand the machine boundary behind your VPS > Read KVM, virtual hardware, containers and dedicated servers as operating boundaries, then maintain the shell and services inside the boundary you choose. Canonical human page: https://swissoctet.com/insights/understand-the-vps-machine-boundary/ SwissOctet Editorial. Topic: compute. Level: Foundation. Reading time: 4 minutes. ## Direct answer KVM, virtual machines, containers and dedicated hardware describe different operating boundaries. Choose the boundary your project needs, verify the features exposed by the offer and maintain the software within that environment. ## A virtual machine is a guest environment A virtual machine presents an operating system with virtualised hardware such as processors, disks and network interfaces. The physical host runs the machinery that makes those guests possible. A VPS is a hosting product built around a virtual server, with a stated resource allocation and an operating environment that the customer can use. Read the allocation as part of the offer, rather than imagining a physical machine behind every virtual CPU. A dedicated server gives the project a physical machine boundary. It can run one operating system or host virtual machines of its own when the hardware and deployment support that design. This changes resource ownership and administration, but it does not remove software vulnerabilities, update work or the need for backups. Choose the boundary from a real isolation or capacity requirement. ## KVM identifies a virtualisation technology KVM provides virtualisation support in the Linux kernel. QEMU supplies a machine model and can use KVM as a virtualisation accelerator, while management software such as libvirt can organise guest configuration and lifecycle. These components explain how an environment can be built; the letters KVM do not specify CPU scheduling, storage performance or service availability. Virtualisation documentation sometimes distinguishes Type 1 and Type 2 hypervisors according to their relationship with the host platform. For a hosting decision, a label is less useful than knowing the guest boundary, maintenance responsibility and exposed hardware. Ask whether the required guest operating system and drivers are supported. Features described by a software project are not automatically enabled in every provider's product. ## Do not confuse guest control with host control Root or administrator access inside a guest lets you manage that guest. It does not give you access to the physical hypervisor, another tenant or every possible host feature. Nested virtualisation, device passthrough and specialised network settings require explicit support. Do not select a VPS on the assumption that a capability available on your laptop will be exposed identically by the hosting environment. Compare the actual plan's CPU, memory, storage, network and licences. Observe your application's latency and resource pressure with representative work after delivery. A virtualisation technology can create a useful isolation boundary while still sharing underlying hardware resources according to provider policy. Neither a guest label nor a dedicated label is a substitute for measurements and a complete operational specification. | Boundary | What the project manages | A capability to verify | | --- | --- | --- | | Virtual machine | Guest OS and its services | Supported OS, drivers and exposed features | | Container | Process and image configuration | Kernel features, limits and mount scope | | Dedicated server | The selected physical machine environment | Hardware and virtualisation requirements | ## Containers organise processes inside an environment A container typically shares its host kernel while grouping processes and their resources. A virtual machine runs a guest kernel. You can run containers inside a VPS when the operating system and runtime support the intended configuration. That combination can make dependencies easier to package without replacing the guest's security maintenance or recovery plan. Docker's resource controls need deliberate settings: by default, the runtime does not place CPU and memory limits on each container. Bound resource use and avoid unnecessary privileges or host mounts. Separate workloads with different trust requirements where practical. Keep the host and images maintained. Treat a container image as software you must verify, rather than as an automatic security decision because it is easy to start. ## The shell is an interpreter, not the server itself A terminal supplies an interaction surface; a shell interprets commands and starts programs. On Linux, Bash is a common shell, while other shells offer different syntax and interactive features. A script must target the interpreter it expects. Changing a login shell does not change every application's interpreter or make a script written for another shell compatible. Shell input can undergo expansion, redirection and command substitution before a program receives its arguments. Understand that processing before building maintenance commands from filenames or user data. Keep untrusted input out of executable command text, quote arguments correctly and prefer a program's structured interface for automated work. History, logs and process arguments may retain sensitive values, so use the private credential mechanism appropriate to the application. ## Operate the boundary you chose After delivery, identify the guest OS, access route and recovery mechanism. Apply updates, establish a restricted administration account and expose only the services the project needs. Test a small deployment before transferring important data. Record the runtime, images and configuration needed to rebuild it; the boundary does not tell you whether the application state is recoverable. Use the SwissOctet comparison to shortlist Vector, DeskLink or a Metal range according to the workload and operating environment. Confirm specialised capabilities before preparing an order. Keep operating-system work, application work and provider work distinct in the runbook. A clear boundary is useful because it tells you what you can configure and what you must ask about, while preserving a practical path for migration and restoration. ## Checklist - Distinguish guest access from host access. - Verify specialised hardware and virtualisation requirements. - Measure the complete configuration, not a hypervisor label. - Configure container limits and permissions. - Use the intended shell and protect command inputs. ## Frequently asked questions ### Does KVM mean I receive dedicated physical CPU cores? No. KVM identifies virtualisation technology. Read the product's CPU allocation and resource policy separately. ### Can containers replace guest maintenance? No. The host environment, container runtime and images all need maintenance, appropriate permissions and recovery planning. ### Are a terminal and a shell the same thing? No. A terminal provides an interface. A shell interprets command input and launches programs within that interface. ## Primary sources - [KVM project: Kernel Virtual Machine](https://www.linux-kvm.org/page/Main_Page) - [QEMU: System emulation introduction](https://www.qemu.org/docs/master/system/introduction.html) - [Docker: Resource constraints](https://docs.docker.com/engine/containers/resource_constraints/) - [GNU Bash: Shell expansions](https://www.gnu.org/s/bash/manual/html_node/Shell-Expansions.html) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [DeskLink RDP](https://swissoctet.com/services/desklink/index.txt): A Windows workspace that follows you. Remote desktop access, configurable resources and a Swiss location. - [Metal Origin](https://swissoctet.com/services/metal-origin/index.txt): A practical entry to dedicated hardware. Your workload, on its own physical machine. - [Metal EPYC](https://swissoctet.com/services/metal-epyc/index.txt): AMD-powered dedicated hardware for parallel workloads and serious compute. ## Related guides - [VPS or dedicated: choose the boundary that fits](https://swissoctet.com/insights/vps-or-dedicated-server/index.txt): Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload. - [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/index.txt): Secure administration, expose only required services and establish updates and recovery without locking yourself out. - [Size VPS CPU and memory from a real workload](https://swissoctet.com/insights/size-vps-cpu-and-memory/index.txt): Build a memory budget, inspect contention and separate one busy thread from work that can use several virtual cores. --- # Plan addresses and DNS as parts of your deployment > Separate public, private, static and dedicated addresses, then map forward DNS, reverse DNS and TLS to the parties that can configure them. Canonical human page: https://swissoctet.com/insights/plan-addresses-and-dns-for-deployment/ SwissOctet Editorial. Topic: network. Level: Foundation. Reading time: 4 minutes. ## Direct answer Public, private, static and dedicated are independent address properties. Build a deployment map that also covers routing, firewalls, forward DNS, reverse DNS and TLS, and verify each setting with the party that controls it. ## Address properties answer different questions Public and private describe where an address is intended to be routed. Static and dynamic describe how an assignment behaves over time. Dedicated and shared describe how an address is used or allocated within a service. These are separate properties: a stable public address might serve many sites, and a private address can be assigned dynamically inside a controlled network. Write the role of each address in the deployment: public entry point, internal database, management route or outbound connection. Then identify who assigns it and what can change. This prevents configuration work from depending on an assumption such as dedicated means permanently fixed or public means the service is reachable. Reachability also depends on routing, firewalls and the application's listener. ## Private addressing still needs routing and access control RFC 1918 reserves the IPv4 ranges 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 for private networks. Their addresses are not globally unique public destinations. A network may translate private addresses for outgoing connections or connect private networks through explicit routes. An inbound service behind translation needs a deliberate publication method; changing a DNS record alone does not create that route. IPv6 has its own address types and scopes, including link-local addressing and globally routable unicast addresses. Review it separately rather than assuming an IPv4 firewall or translation rule covers IPv6. A private address is not an authentication mechanism, and a public IPv6 address is not a reason to expose every service. Test access from each relevant network and restrict administration at the appropriate boundary. ## Stable names and stable addresses are related DHCP allocates address configuration through a protocol and can use leases. A dynamically assigned address may remain unchanged for some time; that does not make its permanence a contractual guarantee. When an application depends on a stable address, verify the provider's assignment and change policy instead of inferring it from yesterday's connection. Dynamic DNS can update a name after an address changes, but clients may still cache the previous answer. It also cannot overcome an unreachable listener, a missing inbound route or carrier-grade address translation. Use it when the network permits the connection and the application tolerates update delays. For a hosted deployment, document the intended address lifecycle before building allowlists or external integrations around it. | Property | What to confirm | Common mistaken assumption | | --- | --- | --- | | Public or private | Routing scope and access path | An address alone makes a service reachable | | Static or dynamic | Assignment and change policy | An unchanged lease is permanent | | Dedicated or shared | Allocation and allowed use | A dedicated address provides anonymous identity | | IPv4 or IPv6 | Both routing and firewall configurations | One protocol's settings cover the other | ## Forward DNS and reverse DNS have different owners Forward DNS maps names to data such as A and AAAA address records. Reverse DNS uses an address-related namespace and PTR records to associate an address with a name. The organisation controlling the forward DNS zone is not necessarily the organisation controlling reverse DNS for the address range. Obtain the right configuration path before promising a reverse name. Check the record through the appropriate resolver and record the result. For a PTR intended to identify a host, also check whether the corresponding forward record points to the expected address. Reverse DNS can support operational identification and some mail-system checks, but it does not authenticate an application or guarantee message delivery. Mail sending also needs its own domain, reputation and authentication review. ## A dedicated address is not required for every HTTPS site HTTP host routing and the TLS Server Name Indication extension allow supported clients and servers to select a site or certificate by name. Several HTTPS sites can therefore use an address without requiring one public address per domain. The actual hosting configuration and required clients determine whether that arrangement is suitable. Choose an extra address only when a documented requirement calls for one, such as a supported network separation or an external system that expects a distinct endpoint. An address does not provide immunity from reputation problems or identify the person operating a service. Keep certificates, hostname routing and address allocation as separate checks. Verify the served certificate through the hostname users will actually visit. ## Use a deployment map before changing records Create a small map containing each hostname, address record, listener, firewall path and responsible party. Include administration, backups and any outbound allowlists. Check whether the SwissOctet configuration lists the address option you need and ask about reverse DNS control before relying on it. Do not present catalogue options as a live assignment that has already been provisioned. During a move, prepare the destination application and TLS settings before directing users there. Account for DNS caches and maintain a workable recovery path. Verify forward resolution, actual application reachability and the expected reverse name separately. The map makes failures easier to locate because a wrong record, a closed port and a mismatched certificate are different problems with different owners. ## Checklist - Map address role, assignment and ownership. - Check IPv4 and IPv6 separately. - Verify inbound routing before relying on DNS. - Identify who controls PTR records. - Test the hostname, certificate and application together. ## Frequently asked questions ### Does a dedicated IP make a service anonymous? No. It describes an allocation or use arrangement, not an identity or privacy guarantee. Accounts, traffic and application data have separate implications. ### Can I set PTR records from my domain's DNS panel? Only if it also controls the relevant reverse zone. The address provider commonly controls that zone or supplies a separate request process. ### Does each HTTPS domain need its own address? Not necessarily. Supported clients and servers can use name-based routing and TLS SNI. Verify the actual hosting and client requirements. ## Primary sources - [RFC 1918: Address Allocation for Private Internets](https://www.rfc-editor.org/rfc/rfc1918) - [RFC 2131: Dynamic Host Configuration Protocol](https://www.rfc-editor.org/rfc/rfc2131) - [RFC 1035: DNS implementation and specification](https://www.rfc-editor.org/rfc/rfc1035) - [RFC 4291: IPv6 Addressing Architecture](https://www.rfc-editor.org/rfc/rfc4291) - [RFC 6066: TLS extensions, including Server Name Indication](https://www.rfc-editor.org/rfc/rfc6066) ## Related infrastructure - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Canvas Web](https://swissoctet.com/services/canvas/index.txt): A clean foundation for websites and publishing. Pick your storage, domains and hosting options. - [Metal Origin](https://swissoctet.com/services/metal-origin/index.txt): A practical entry to dedicated hardware. Your workload, on its own physical machine. - [Shield VPN](https://swissoctet.com/services/shield/index.txt): A Swiss OpenVPN configuration for one device, with AES-256 encryption and unlimited traffic. ## Related guides - [A domain, DNS and TLS cutover runbook for a new server](https://swissoctet.com/insights/dns-tls-cutover-runbook/index.txt): Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections. - [Secure Windows RDP administration without losing access](https://swissoctet.com/insights/secure-windows-rdp-administration/index.txt): Separate network reachability, authentication and privilege, then verify a recovery route before tightening remote access. - [Choose a traffic path: server, tunnel or proxy](https://swissoctet.com/insights/choose-a-server-tunnel-or-proxy/index.txt): Understand what a VPS, VPN and proxy each change, then select routing, protocols and operating responsibilities from the connection you actually need. --- # Separate your public web edge from the application > Give the web server, reverse proxy and application distinct responsibilities, with deliberate origin access, TLS, request limits and an incident path. Canonical human page: https://swissoctet.com/insights/separate-the-web-edge-from-the-app/ SwissOctet Editorial. Topic: hosting. Level: Applied. Reading time: 4 minutes. ## Direct answer Separate HTTP publication from application execution and persistent data. A reverse proxy can organise routing and limits, but origin access, application authorisation, upstream capacity and recovery each require their own controls. ## A web request crosses several responsibilities A web server receives HTTP requests and can serve static files. An application process executes the project's dynamic behaviour, such as checking an account or querying a database. A reverse proxy receives requests on behalf of that process and forwards them to an upstream. One program may fulfil several roles, but separating the responsibilities makes configuration and recovery easier to reason about. Trace one request from hostname resolution to the response. Record where TLS ends, which process chooses the route and which component can read application data. Do the same for an administrative request. This exercise often exposes a listener or hostname that was created for testing and accidentally remained reachable. The diagram should describe the deployed path rather than the architecture you hoped to build. ## Use the edge to organise HTTP behaviour NGINX documents both serving static content and forwarding requests to an upstream. Its worker architecture and HTTP modules provide configuration mechanisms, but a particular configuration still determines the behaviour. Define hostnames, upstreams and filesystem roots deliberately. Restrict the files that can be served so configuration, credentials and repository metadata never become downloadable because they happen to sit near the application. Set appropriate limits for request bodies, timeouts and connections according to the application. Treat caches as a data decision: content tied to a user or permission cannot safely inherit a shared caching rule without review. Test authentication and cache behaviour together. Keep a reproducible configuration and validate changes before reloading the service, with a known route back to the previous working version. | Layer | Useful responsibility | Check before launch | | --- | --- | --- | | Public web edge | TLS, hostname routing and HTTP limits | Certificates, roots and intended hostnames | | Application process | Business logic and authorisation | Authentication, input checks and dependency failure | | Internal data service | Persistent application state | Restricted access and tested restoration | | Upstream provider network | The contracted network service | Protection scope and escalation path | ## A reverse proxy does not remove the origin's exposure If the origin remains publicly accessible, a client may reach it without using the intended proxy route. Restrict origin access through the network design and application configuration when the deployment requires that boundary. On one machine, a backend can often listen on loopback or a local socket. Across machines, use explicit restricted routes and suitable protection for the upstream connection. Forwarded headers need a trust rule too. Accept information about the original client only from trusted intermediaries, and prevent arbitrary callers from supplying values that the application treats as authoritative. Decide what appears in access logs and error reports. A proxy can change the information available at each layer; it does not erase account identifiers or make the application anonymous to its own operator. ## Apply access decisions inside the application NIST's Zero Trust architecture focuses on access decisions for resources rather than implicit trust based only on network location. Apply that principle concretely: authenticate the caller, authorise the requested operation and give service accounts only their required scope. A request arriving from an internal subnet should not automatically become an administrator request. Separate public and administrative functions where practical. Recheck permission when a user accesses a record rather than relying only on the initial login. Keep credentials for the proxy, application and database distinct. Introduce changes in stages that can be tested, beginning with a narrow sensitive path. Calling a deployment Zero Trust is less useful than demonstrating that a forbidden action is actually denied at the component responsible for it. ## Plan denial of service at more than one layer A saturated network link and an expensive application request fail at different places. Rate limiting at the web edge may help constrain request patterns, while application limits can bound work such as searches, uploads or exports. NGINX's request-limit module supplies one mechanism; the key and thresholds must fit real users and be tested to avoid rejecting legitimate traffic. OWASP's denial-of-service guidance also addresses resource exhaustion in application behaviour. Put time and size limits around expensive work, use bounded queues and monitor failure signals. Local controls cannot create capacity in an upstream link that is already saturated. Confirm the specific network protection included in the chosen offer and prepare an escalation path. Never assume a catalogue's Layer 3–4 protection also proves protection for every HTTP workload. ## Make recovery part of the publication Check the site from an external client using its intended hostname. Verify HTTPS, redirects, static resources, logins and a representative application transaction. Confirm that administrative listeners and private files remain inaccessible. Simulate a stopped upstream and check that the edge returns a controlled failure rather than exposing internal details or waiting without a limit. For Canvas, read the controls available within the hosting account. For a VPS, maintain the web edge and application as part of your own operating plan. A large network port is a capacity specification, not proof that the application can sustain that throughput. Keep monitoring, restoration and provider contacts in the runbook. Publish only after the actual request path and a practical recovery path have been verified. ## Checklist - Trace a public and an administrative request. - Define served roots and upstream listeners. - Trust forwarded headers only from approved intermediaries. - Test authorisation and cache boundaries. - Prepare limits and escalation for network and application failures. ## Frequently asked questions ### Can a web server also act as a reverse proxy? Yes. NGINX is one documented example. Its roles depend on the configuration, and the application still needs its own authorisation and maintenance. ### Does a reverse proxy automatically hide the origin? No. The origin may remain reachable unless routing, firewall and listener settings enforce the intended boundary. ### Will request limiting stop every DDoS attack? No. It addresses selected HTTP request patterns. Network saturation and other resource failures require appropriate upstream and application controls. ## Primary sources - [NGINX: Beginner's guide](https://nginx.org/en/docs/beginners_guide.html) - [NGINX: HTTP request limiting](https://nginx.org/en/docs/http/ngx_http_limit_req_module.html) - [NIST SP 800-207: Zero Trust Architecture](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-207.pdf) - [OWASP: Denial of Service Prevention](https://cheatsheetseries.owasp.org/cheatsheets/Denial_of_Service_Cheat_Sheet.html) ## Related infrastructure - [Canvas Web](https://swissoctet.com/services/canvas/index.txt): A clean foundation for websites and publishing. Pick your storage, domains and hosting options. - [Vector VPS](https://swissoctet.com/services/vector/index.txt): Your own Linux environment, with KVM virtualization and a clear path from small projects to larger workloads. - [Pulse NVMe](https://swissoctet.com/services/pulse/index.txt): Fast NVMe storage for applications where I/O is part of the performance equation. - [Transit 40](https://swissoctet.com/services/transit-40/index.txt): Dedicated configurations with a 40 Gbps port for bandwidth-intensive applications. ## Related guides - [A Linux VPS hardening baseline you can maintain](https://swissoctet.com/insights/linux-vps-hardening-baseline/index.txt): Secure administration, expose only required services and establish updates and recovery without locking yourself out. - [Build monitoring that leads to a useful incident response](https://swissoctet.com/insights/monitoring-incident-response-playbook/index.txt): Connect application symptoms, actionable alerts and a small response playbook so that an operator can make clear decisions when a service degrades. - [A domain, DNS and TLS cutover runbook for a new server](https://swissoctet.com/insights/dns-tls-cutover-runbook/index.txt): Prepare hostname routing, certificates and rollback together so that a migration changes the server without breaking the site's identity or secure connections.