Leneex - Hosting Provider
ClickHouse

Deploy ClickHouse on a VPS in One Click

Databases & data storageWeb analytics

Column-oriented OLAP database for real-time analytics on billions of rows.

Deploy on a VPSAll apps
  • Ready in ~5 min
  • Free installation
  • We handle the setup
At a glance
Version
Latest (26.x)
Operating system
Ubuntu Server 24.04 LTS
Minimum RAM
4 GB
License
Apache 2.0
Addressing
IPv4, IPv6
GitHub
50,000
Deployment~5 min
Open source & self-hosted
VPS plans

Choose a VPS plan for ClickHouse

Blazing-fast NVMe drives and powerful processors. Take a ready-made plan or build the configuration yourself.
Minex
Perfect for personal projects and small websites.
€3.20/mo
Save €0.80 per month
  • 1 vCPU core
  • 1 GB DDR5 RAM
  • 20 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 1 TB traffic
Basex
A great balance of power and affordable price.
€4.80/mo
Save €1.20 per month
  • 2 vCPU cores
  • 2 GB DDR5 RAM
  • 40 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 2 TB traffic
Most popular
Corex
For growing applications and businesses.
€7.20/mo
Save €1.80 per month
  • 4 vCPU cores
  • 4 GB DDR5 RAM
  • 50 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Midex
Resources for high-load projects.
€9.60/mo
Save €2.40 per month
  • 4 vCPU cores
  • 6 GB DDR5 RAM
  • 60 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Proex
Maximum power and scalability.
€12.00/mo
Save €3.00 per month
  • 6 vCPU cores
  • 8 GB DDR5 RAM
  • 70 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Scalex
Resources for scaling.
€16.00/mo
Save €4.00 per month
  • 6 vCPU cores
  • 10 GB DDR5 RAM
  • 150 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Maxex
A large reserve of power.
€44.00/mo
Save €11.00 per month
  • 8 vCPU cores
  • 16 GB DDR5 RAM
  • 200 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Apex
The top configuration.
€79.99/mo
Save €20.00 per month
  • 16 vCPU cores
  • 32 GB DDR5 RAM
  • 400 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic

What you can do with ClickHouse

ClickHouse is an open-source, column-oriented database engine built for fast analytical queries over massive datasets, aimed at data engineers and BI teams rather than general application developers. It powers dashboards, log analysis, and time-series reporting in cases where row-oriented databases like PostgreSQL start choking on billions of rows.

What sets it apart is raw scan speed paired with aggressive compression, plus native support for distributed queries across nodes. Running ClickHouse self hosted gives you direct control over memory allocation and disk I/O — the two factors that actually determine query latency at scale, which is exactly what a shared managed service takes away from you. A dedicated VPS for ClickHouse removes that ceiling entirely.

Get started
The applications screen of the control panel with one-click install

ClickHouse features

A server surrounded by app icons — applications running on a VPS

ClickHouse packs a wide analytical toolkit well beyond plain SQL querying. Solid hosting for ClickHouse means these features actually run at full capacity instead of hitting resource ceilings typical of shared plans.

01

MergeTree storage engine

Organizes data by partition and sorted primary key, so range scans over huge tables stay fast even without indexes on every column.

02

Vectorized query execution

Processes data in CPU-friendly batches rather than row by row, which is why aggregate queries return in milliseconds instead of seconds.

03

Real-time data ingestion

Accepts streaming inserts over HTTP, the native TCP protocol, or Kafka engine tables for pipelines that need fresh data without batch delays.

04

Materialized views

Precompute aggregations as new rows arrive, so repeated dashboard queries don't recalculate from scratch each time.

05

Distributed and sharded tables

Split data and query load across multiple ClickHouse nodes once a single server outgrows a dataset.

06

Native BI integrations

Connects directly to Grafana, Apache Superset, and Metabase without a middleware layer.

07

Array, Nested, and JSON functions

Handles semi-structured event and log data in plain SQL instead of forcing a rigid relational schema.

08

Docker-based deployment

The official clickhouse/clickhouse-server image makes a ClickHouse vps docker setup straightforward for isolated, reproducible environments.

Requirements

Which server to run it on

Minimum requirements for ClickHouse and the configuration worth starting with.
Minimum
  • CPU2 vCPU
  • Minimum RAM4 GB
  • Disk50 GB
Recommended
VPS Midex
  • CPU4 vCPU
  • Minimum RAM6 GB
  • Disk60 GB

Installation is free — you only pay for the server

Getting started

How to deploy ClickHouse

Three steps and the app is running on your server.
Step 1
Choose a server

Pick a plan with RAM headroom — ClickHouse installation performs best with 8 GB or more dedicated memory, since it caches large data blocks during merges.

Step 2
Pick the app

The one-click installer runs the official Debian repository flow to install ClickHouse on VPS automatically, including the systemd service setup.

Step 3
Get your credentials

You'll get the server IP, root credentials, and the default ClickHouse user's password for connecting via clickhouse-client or the HTTP interface right away.

Official websiteclickhouse.com
GitHub repositorygithub.com
Documentationclickhouse.com
Why us

Why Host ClickHouse on Leneex

Speed, protection and support you can rely on — on every plan, with no hidden limits.
Deployment speed
Deployment finishes in minutes: ClickHouse vps hosting through the one-click installer skips manual package builds, so your first analytical query can run the same day instead of losing a sprint to server prep.
Free installation
No setup fee on top of an engine that already demands real infrastructure spend for RAM and fast disks — every euro saved on install goes toward the SSD storage ClickHouse leans on for merge and scan performance.
DDoS protection
ClickHouse's HTTP and native TCP ports rarely need to face the open internet directly, but any dashboard, ingestion job, or exposed Play UI still draws flood and brute-force attempts — built-in filtering keeps query throughput stable instead of stalling under attack.
Control and support
Tuning MergeTree settings, replication, or per-query memory limits requires real root access, not a stripped-down control panel — and round-the-clock engineer support matters when a stuck merge or disk-pressure issue needs fixing outside business hours.
99.9% uptime with SLA compensation
Dashboards and monitoring pipelines built on ClickHouse are only as dependable as the server underneath — an SLA-backed 99.9% uptime keeps ingestion and query availability steady for teams who rely on current numbers, not stale ones.
Flexible payment
Data infrastructure budgets often route through a company card, crypto treasury, or invoiced procurement — flexible payment options let a ClickHouse deployment fit whichever billing process your team already runs on.
What to choose

ClickHouse: Self-Hosted vs Cloud — Which to Choose

We compare cost, control over your data and limits, so the choice is an informed one.
ClickHouse Cloud
Self-hosted on LeneexRecommended
Resources and limitsCompute and storage billed separately with autoscaling, but throughput ceilings apply per pricing tierDedicated CPU, RAM, and disk I/O — no contention from other tenants during heavy merges or backfills
Control and accessManaged control plane — no root/SSH, some low-level engine settings are restricted or unavailableFull root access, editable config.xml and users.xml, custom MergeTree and replication settings
Feature limitsA curated feature subset validated for the managed environment; some settings are locked downFull ClickHouse feature set, including experimental settings and custom engines
ScalingScales automatically within the plan, but cost rises with compute-seconds and storage usedUpgrade the VPS plan or add nodes manually for sharding
CostPay-as-you-go pricing tied to compute time and stored data — costs grow with usageFixed monthly VPS price regardless of query volume or data ingested
Who it fitsTeams that want zero operational overhead and are fine with usage-based billingTeams with heavy, predictable query loads or data residency requirements who want to tune the engine directly

ClickHouse Cloud exists as the official managed offering, so the comparison is direct. Self-hosted ClickHouse on VPS makes sense once ingestion volume or query load is steady and predictable — deploying ClickHouse in one click on your own server turns a variable, usage-based bill into a fixed one while handing back full root-level control over tuning.

Frequently Asked Questions about ClickHouse on VPS

What people ask most about ClickHouse and our servers.

  • Yes — export data with the BACKUP/RESTORE commands or the clickhouse-backup utility, transfer the backup files to the new server, and restore them into the freshly installed instance.

  • Vertically resizing CPU and RAM on the same VPS leaves the data directory untouched; moving to a plan with different storage requires migrating the /var/lib/clickhouse directory or restoring from a backup.

  • No — the base install does not configure a TLS certificate automatically, so it's best to restrict ports 8123 and 9000 with a firewall or connect through an SSH tunnel until TLS is set up manually.

  • A minimum plan comfortably runs light analytical workloads and dashboards for a handful of concurrent users, but production-grade ingestion pipelines typically need 8 GB of RAM or more to avoid merge backpressure.

  • You do — Leneex installs ClickHouse once via one-click deploy in one click, and future upgrades run through apt on the official ClickHouse repository, since major version jumps can affect replication and are not applied automatically.

What's already set up

ClickHouse server and the clickhouse-client are installed from the official packages.clickhouse.com repository, and the clickhouse-server service runs under systemd, starting automatically on reboot. Configuration lives in /etc/clickhouse-server/config.xml (networking, ports, logging) and /etc/clickhouse-server/users.xml (users and profiles). Data is stored in /var/lib/clickhouse/, logs in /var/log/clickhouse-server/. A default database named default and a system user default are created out of the box.

Getting access for the first time

The HTTP interface listens on port 8123 and the native TCP protocol used by clickhouse-client listens on port 9000. From your workstation, connect with clickhouse-client --host <server_ip> --user default --password <password>, or open http://<server_ip>:8123/play in a browser for ClickHouse's built-in Play UI to run ad-hoc SQL without installing a client. By default ClickHouse only accepts connections from localhost;. If remote access isn't already enabled, add <listen_host>0.0.0.0</listen_host> to config.xml and restart the service with systemctl restart clickhouse-server.

Practical first steps

Create a dedicated admin user and reduce reliance on the default account before connecting any application, since default carries broad privileges out of the box. Because this is a database engine rather than a web app, expect no browser-based admin dashboard beyond the lightweight Play UI — most day-to-day work happens through SQL, either via clickhouse-client or an HTTP client library. For anything beyond a single node, plan your MergeTree partitioning and replication strategy before ingesting production data, since restructuring large tables later is far more expensive than designing the schema correctly from the start.

Deploy ClickHouse in about 5 minutes

Choose a server — we do the rest: install, configure and send you the credentials.

Choose a serverAll apps