LINUX VPS

Linux VPS hosting. Built around your project.

Configure a Linux VPS for websites, APIs or containers. Choose Ubuntu, Debian or AlmaLinux, compatible setup options and a term of at least three months.

  • Linux · SSH · Docker
  • Crypto payment
Your next line of code.
A Linux environment preview. Available images depend on the plan.Preview

Your workload

Size the server for your application and its data.

Your environment

Check the distribution and options on the selected offer.

Your administration

Plan access, system updates and backups.

VPS CONFIGURATIONS

Resources for your next project.

Compare configurations and choose resources that fit your applications.

Offers

Libre 1

Your first site or development environment.

From
€11.52for 3 months

EUR reference · crypto payment

  • 1 vCPUProcessor
  • 4 GBMemory
  • 50 GB NVMeStorage
  • 4 TBIncluded transfer
  • 3 monthsPeriod

Libre 4

Resources for several services and their data.

From
€23.07for 3 months

EUR reference · crypto payment

  • 4 vCPUProcessor
  • 16 GBMemory
  • 200 GB NVMeStorage
  • 16 TBIncluded transfer
  • 3 monthsPeriod

Libre 8

A larger configuration for demanding projects.

From
€46.17for 3 months

EUR reference · crypto payment

  • 8 vCPUProcessor
  • 32 GBMemory
  • 400 GB NVMeStorage
  • 32 TBIncluded transfer
  • 3 monthsPeriod
THE DIFFERENCES AT A GLANCE

Compare what matters to your project.

Choose a term to compare the base plan amount. Select additional options in the hosting configurator.

Term to compare

Scroll to compare all plans.

These are the resources listed for the base plan.
ConfigurationLibre 1Libre 2Libre 4Libre 8
Processor1 vCPU2 vCPU4 vCPU8 vCPU
Memory4 GB8 GB16 GB32 GB
Base storage50 GB NVMe100 GB NVMe200 GB NVMe400 GB NVMe
Included transfer4 TB8 TB16 TB32 TB
Initial environmentUbuntu 24.04 LTSUbuntu 24.04 LTSUbuntu 24.04 LTSUbuntu 24.04 LTS
Total for this term3 months€11.52€16.77€23.07€46.17
ConfigurationConfigureConfigureConfigureConfigure

Base plan amount before extras. Your quotation confirms the complete selection.

START WITH YOUR PROJECT

Find a plan to compare.

Choose how you will use the server, then compare the actual resources with your application inventory. A workflow alone cannot determine the right server size.

Your project type
Compare the available configurations

These are the available server configurations to compare. Measure the combined CPU, memory, storage and transfer needs of your applications before selecting a size.

  • Budget resources for concurrent processes and the operating system together.
  • Assign responsibility for system updates, access security and data recovery.
Build a VPS resource checklist
ONE ENVIRONMENT, YOUR PROJECTS

From your first site to your next application.

Organise your server around what you deploy. Your project’s needs guide the choice of resources.

01

Websites & applications

Prepare your web server, domain and files to host your project.

02

Docker & containers

Separate services and plan the memory and volumes they need.

03

APIs & databases

Bring applications and data together with organised access and backups.

Prepare the Linux environment your application needs

Size the complete stack, including maintenance work

List the processes your VPS will run: application, database, reverse proxy, scheduled jobs and any supporting services. Compare their requirements with the published vCPU, memory, storage and transfer figures. Include the operating system and background work in the inventory rather than sizing only the main application.

Existing measurements are the strongest starting point. Include build jobs, database imports and backup operations when reviewing periods of higher usage. Plan where logs, uploads and recovery copies will live. Choose the configuration against those needs, then revisit it when the application changes or real usage reveals a different requirement.

For a Node.js API, include the runtime, reverse proxy, database and workers in that measurement. Choose an administration owner for process supervision, deployment and recovery. The Linux plan and crypto checkout select the server and settle the hosting order; they do not install or maintain your application code.

Size a VPS from real workload requirementsPlan storage for applications and maintenancePrepare a VPS deployment for a Node.js API

Choose a compatible distribution, profile and panel

Choose an available Linux distribution supported by your software and the administrator who will maintain it. Review the preparation profile and panel options together. A website control panel, a general server-administration interface and a container workflow solve different tasks; your combination should follow the available compatibility choices.

For containers, identify the required runtime, persistent data and network exposure before choosing the initial setup. Use the Docker VPS page for that application-specific decision. Record your hostname and project preferences in the configurator, then use the actual delivered access details to verify and complete the environment.

Choose a VPS configuration for DockerCompare available VPS control-panel approaches

Assign an owner for access, updates and recovery

Decide who will manage SSH access, service configuration, operating-system updates and application releases. Document the access and recovery steps you need before opening the application to users. Keep credentials private and verify a second working access path before making changes that could interrupt administration.

Select backup extras according to your data and recovery requirements, then check the delivered service scope. Keep an independent copy of important files and database data and test a restore. The initial setup choices are part of your order; the maintenance and recovery plan gives that environment a practical owner over time.

Prepare a Linux VPS security checklistOrganise backups and restoration

FROM CONFIGURATION TO YOUR ACCOUNT

A clear path from your project to your service.

  1. Configure your hosting

    Choose your plan, term, software and extras. Your quotation breaks down the amount due.

  2. Pay the crypto invoice

    Find the exact amount, asset, network and destination on your invoice.

  3. Track your order

    Follow payment and service setup in your account. Access details appear after delivery.

FREQUENT QUESTIONS

Before you begin.

Compare VPS offers
Which Linux distribution should I choose?

Check your software requirements against the available Ubuntu 24.04 LTS, Debian 12 and AlmaLinux 9 choices. The configurator also offers compatible setup profiles and panels. HestiaCP requires Ubuntu or Debian with the clean-system profile. You remain responsible for planning maintenance and application compatibility.

Which crypto payments are supported?

Checkout methods are BTC on Bitcoin; ETH, USDT and USDC on Ethereum; SOL on Solana; TRX and USDT on Tron; LTC on Litecoin. Choose an available method and follow the asset, network and exact amount shown on your invoice.

How does renewal work?

Renewal uses a new crypto invoice for the same service and its purchased options, with a minimum three-month period. Review the total and next deadline in your account. The initial payment does not schedule an automatic wallet debit.

Learn more

A Linux virtual server can host a website, an API or containers. Start with your application, the distributions offered and the time you can devote to server administration.

Host a website, an API or containers

Linux provides an environment for many server applications. A web application may need an HTTP server and a database; an API may require a specific runtime; a Docker project can bring together several services isolated in containers.

Check software requirements against the Ubuntu 24.04 LTS, Debian 12 and AlmaLinux 9 choices in the configurator. Choose a system-only, Docker or Nginx preparation profile and a compatible panel. HestiaCP requires the clean-system profile with Ubuntu or Debian. These are requested delivery preferences, not proof of an already running server.

Also plan a domain name, DNS configuration and a TLS certificate for a public web service. These are part of preparing your application and should not be assumed to be included with every VPS rental.

Size the resources without overbuying

Memory must accommodate the system, application, caches and services running in parallel. Storage needs to cover files, databases, logs and their growth. Compute requirements depend on the actual workload and number of simultaneous tasks.

For containers, add up the services’ requirements and leave room for the host system. A small test application and a heavily used database need different sizing. Measure usage after deployment to refine your choice.

Compare the resources, location and transfer limits actually published. Geographic proximity can matter for your audience, but only measurements from the relevant locations can establish application latency.

Prepare SSH access and maintenance

Before exposing the server, plan protected SSH access with suitable keys. Apply system updates, configure the required firewall ports and give each service the permissions it needs.

A working application also needs monitoring of disk space, logs and backups. Keep a copy outside the VPS and test restoration. Planning backups within your organisation does not mean an offer includes a backup service.

Check whether the VPS is managed or whether these tasks are your responsibility. Included services and available actions appear in the offer and its terms. Crypto pays for the order; it does not replace server maintenance.

Your Linux deployment plan
  • Confirm the available distribution, version and access rights.
  • Estimate the required memory, compute, storage and transfer.
  • Prepare SSH, the firewall and system updates.
  • Define backups and test a restoration.

Guides for your next steps

All guides

Explore VPS hosting

Go from requirements to offers.

Use the specifications, options and prices of the offers published in the catalogue.

Compare VPS offers