ClickHouse for analytics, on your own disk.

Analytics data grows faster than anything else in a product, which is exactly the workload usage-based pricing punishes. Depfloy provisions ClickHouse on a server you own, where the cost is the machine.

Start free trial Read the docs
ClickHouse
Runs on
A server you own
Scheduled backups
Supported
The workload where owning the machine pays off

Event and analytics tables grow without asking permission. On your own server, growth costs disk — not a per-gigabyte line on an invoice.

Managed next to the app that writes to it

The ClickHouse server appears in the same console as the app, with the same firewall, monitoring and backup screens.

Backups with restore

A schedule dumps the database to your destination of choice, with retention and checksums, and restore targets a database you pick.

ClickHouse is the clearest case for owning the hardware: analytics volume is unpredictable, and metered storage turns that unpredictability into an unpredictable bill.

FAQ

ClickHouse questions

Should ClickHouse share a server with PostgreSQL? +
Better not to. It is memory-hungry by design, and a separate database server keeps an analytics query from starving the transactional database.
Can I query it from my app? +
Yes — open the port to your app subnet over the private network and connect with any ClickHouse client.
Is the data included in my Depfloy plan? +
There is no data charge at all. Your provider bills you for the server; Depfloy bills a flat plan regardless of how much you store.

Six other services, provisioned the same way.

Each one is installed, firewalled and monitored from the same console.

PostgreSQL MySQL Redis Valkey Meilisearch

Run ClickHouse on your own server.

7 days free, no credit card. Your provider bills you for the machine; we bill a flat plan.

Start free trial How releases work