The Countly Server Hub provides essential documentation for installing, sizing, configuring, upgrading, and backing up a self-hosted Countly Server.
If you are setting up a new Countly Server, start with Countly v26.01. If you are running v25.03 or earlier, see Countly v25.03 and earlier below.
Deployment Paths
Countly v26.01 supports two self-hosted deployment paths. Docker Compose is the fastest way to a running server, and Kubernetes with Helmfile is recommended for production at scale.
Sizing
Pick a preset tier or sizing profile that matches your expected traffic and retention, instead of tuning each component by hand.
Migrating to v26.01
If you are moving an existing deployment (v25.03 or earlier) to v26.01, you must copy your historical events from MongoDB to ClickHouse. Start with the introduction to plan your cutover.
Countly v25.03 and earlier
The guides in this section apply to Countly v25.03 and earlier. For new installations, use Getting Started with Countly v26.01.
Installation
Looking to find out the System Requirements, Deployment Types, and Installation Procedures for both Countly Enterprise and Lite editions? Check out our guides here:
Configuration
After installing the Countly server, it's time to set it up! Check out our guides here for the configuration process, securing your new Countly server, and monitoring your system.
Docker & Kubernetes
You can also deploy Countly with Docker or Kubernetes. Our guides below detail how to set up and upgrade Countly using Docker or Kubernetes.
Database: MongoDB
Let's check out the guides below to see how we can secure the database and the MongoDB features we use.
Performance
Check out the following article to see our general recommendation for your Countly Server.
Maintenance & Backup
Our strongest best practice recommendation: Keep your Countly server up to date and regularly back up your data (for self-hosted environments). Let's see how we can do this in the following guides.
Migration Guides
This section offers a step-by-step guide to upgrading from one version to the next, which may include breaking changes and special instructions. We recommend reviewing this section carefully to ensure a smooth upgrade.