Proven Success
Altinity has helped thousands of development teams to focus on data not ClickHouse.
100 Million Downloads
Our open-source projects including the Altinity Kubernetes Operator for ClickHouse are used in thousands of applications.
Run Anywhere
Altinity.Cloud manages ClickHouse in any cloud including yours and on-prem with no vendor lock-in.
Trusted by enterprises and startups worldwide
Managed service for ClickHouse
Run ClickHouse in our cloud account or yours and enjoy the benefits of 100% open source ClickHouse.
Ideal for developers who want to focus on their application with support for ClickHouse included.
Support for ClickHouse
Get your cluster under control, optimize schema and query design, and make your queries 10X faster.
Ideal for developers who want to get expert help on designing their ClickHouse cluster.
Build innovative ClickHouse analytics on Kubernetes
Operate ClickHouse with confidence in any Kubernetes environment.
Ideal for developers who want to leverage the full power of data on Kubernetes.
Why enterprises choose Altinity
100% Open-Source ClickHouse Compatibility
We support whichever way you want to run ClickHouse. No vendor lock in.
Pioneers of ClickHouse on Kubernetes
Altinity has helped thousands of companies deploy ClickHouse on Kubernetes.
Leading advocates and contributors to ClickHouse
Altinity has contributed over 1000 PRs to ClickHouse and ecosystem projects.
Get curated ClickHouse tips and tricks straight to your inbox.
No marketing BS. No company talk. Just one tip every month that will transform how you operate ClickHouse.
Read the Latest From Our Blog
-
Slash CI/CD Bills (Part 1): Using Hetzner Cloud GitHub Runners for ClickHouse Builds
If controlling CI/CD bills is essential for you or you’re interested in exploring non-AWS-oriented runner solutions for your projects hosted on GitHub, then read on and see how using Hetzner Cloud GitHub runners for ClickHouse helped us control our ClickHouse CI/CD bills.
-
Adventures in ClickHouse Development: Running Integration Tests, Part 2
In Part 2 of this two-part series, we will pick up where we left off and first try to run all the integration tests by hand. We will first try the naive approach and then go back to ci-runner.py to get the details of how all the integration tests are executed using this script. After that, we will look into what it takes to solve the problem with the Docker images that are required for the tests. Finally, we will use a helper test program that we have developed for running integration tests that addresses the pain points that we discover along the way.
-
Adventures in ClickHouse Development: Running Integration Tests, Part 1
Most ClickHouse developers rely heavily on tests executed by the CI/CD pipeline. In this two-part article, we will show how you can execute ClickHouse integration tests by hand as well as look into the complexity of the CI/CD pipeline that is used to run all these tests.