cloudparts

Cherry Servers

A Lithuanian host that rents dedicated bare-metal servers through an API, billed by the hour, as spot capacity or by the month, from seven locations in Europe, the US and Asia.

What it is
Infrastructure as a service (IaaS)
Used for
Virtual machines,Block storage
Type
Commercial product
Made by
Cherry Servers, UAB
License
Proprietary
Facts checked
24 October 2026
Website

What it is

Cherry Servers is mainly a bare-metal provider. Instant Servers are stocked dedicated machines, up to 128 cores and 768 GB of memory, that deploy in about 12 minutes; Custom Servers are built to order in one to three days, with up to 1,152 GB of memory, ten NVMe disks and optional GPUs. Next to them sit virtual servers (shared-core VPS and dedicated-core VDS, including Arm VDS), Elastic Block Storage and backup storage. Everything is driven through a REST API, the cherryctl CLI, Python and Go SDKs, a Terraform provider and an Ansible collection.

Servers can be billed monthly or annually in advance, or on demand by the hour. Spot servers are spare on-demand machines sold at up to 70% off; Cherry Servers can reclaim them with two minutes’ notice, which you only see by polling the server’s termination-date API endpoint, and the SLA doesn’t apply. Traffic is metered on outgoing data only: a fixed-term dedicated server includes 100 TB a month, allowances are pooled across a project, and extra traffic costs €0.50 per TB in Europe and the US. Singapore and Tokyo have their own, smaller allowances (20 TB for a dedicated server) and €1.69 per TB.

The company’s headquarters are in Šiauliai, Lithuania, which is also one of its server locations; the others are Amsterdam, Frankfurt, Stockholm, Chicago, Singapore and Tokyo. It accepts card payments and cryptocurrencies, and counts blockchain node operators, streaming and gaming companies among its customers.

Why teams pick it

  • Single-tenant hardware created and destroyed through an API and billed by the hour, which suits short jobs and CI on bare metal
  • Generous pooled traffic: 100 TB a month per fixed-term dedicated server in Europe and the US, at €0.50 per extra TB
  • Spot servers at up to 70% off for stateless, fault-tolerant work
  • Automation tools for the whole lifecycle: REST API, cherryctl, SDKs, Terraform and Ansible, with user data at deploy time

Watch out for

  • A host, not a full cloud: the product list stops at servers, block storage and backups, so databases and orchestration are yours to run
  • Asia-Pacific traffic is much more expensive and allowances there are a fifth of Europe’s; Singapore traffic is not pooled with other regions
  • Spot servers can be terminated with two minutes’ notice, and the notice only shows up if you poll the API for each server
  • If a project goes over its traffic cap, bandwidth can be throttled to 100 Mbps until usage drops or more traffic is bought

Alternatives

What all infrastructure as a service (iaas) have in common →Compare side by side →
OVHcloudCommercialA French cloud provider that builds its own servers and data centers and sells bare-metal servers, an OpenStack-based public cloud and hosted private clouds.ScalewayCommercialThe cloud arm of France’s iliad group: VMs, GPUs, bare-metal servers, Kubernetes and managed databases in four three-zone regions in Paris, Amsterdam, Warsaw and Milan.HetznerCommercialA German host that rents cloud VMs by the hour and whole dedicated servers by the month from its own data center parks in Germany and Finland, plus cloud-only sites in the US and Singapore.

How it fits with other technologies

Deploy an hourly bare-metal server in Šiauliai with `cherryctl` · bash

cherryctl init                      # prompts for API key, team and project
cherryctl plan list
cherryctl image list --plan e5_1620v4

# hourly is the default billing cycle; add --spot-instance for spot pricing
cherryctl server create -p <project_id> --plan e5_1620v4 \
  --hostname staging-server-1 --image ubuntu_24_04 --region LT-Siauliai \
  --ssh-keys <ssh_key_id> --userdata-file cloud-init.yml

cherryctl server list

See it in a real stack

No architecture uses Cherry Servers yet. Drop it into the playground and wire it up yourself.Open playground →
Where it came from2001–2026

Cherry Servers began in 2001 as a few college students in Lithuania who wanted to build their own IT business, trying everything from website hosting to desktop software. In 2008 they dropped the side ventures and went all in on hosting and infrastructure. In 2010 the company, then a dedicated-server host, introduced a brand for foreign markets, BalticServers, and an EU-funded project record later described it as the biggest exporter of data center services in Lithuania.

The company traded as Baltic Servers and later renamed itself Cherry Servers. It grew without outside funding, reinvesting in its product and team, and shifted toward API-driven bare metal for developers, Web3 and data-heavy teams. Locations outside Lithuania followed: Frankfurt became its sixth in February 2025, Arm VDS plans launched in Lithuania that August, and Tokyo went live in May 2026.

Why it’s built this way

Focus on hosting alone
In 2008 the founders stopped their side ventures because spreading effort across unrelated products slowed them down; concentrating on hosting let them improve faster and give more consistent service.
Bare metal billed like cloud
On-demand servers are paid by the hour from a prepaid team balance and spare stock is sold as spot capacity, so the same dedicated hardware can be rented for an hour or for a year.
Grow without outside funding
The company says it reinvested in its product, team and customers rather than raising money, and grew steadily as a result.

Timeline

  1. 2001

    Founded by students in Lithuania

  2. 2008

    Goes all in on hosting and infrastructure

  3. 2010

    Launches the BalticServers brand for foreign markets

  4. 2025

    Frankfurt opens as the sixth location (February); Arm VDS in Lithuania (August)

  5. 2026

    Tokyo location goes live in May

Sources9 · facts checked 24 October 2026

Improve this page on GitHub