Installation FAQ


Self-hosted or private cloud options available

You may either install Countly on-premises (e.g. self-hosted) or let Countly handle the deployment, maintenance, and backup procedures for you. This FAQ includes questions regarding the self-hosted installation of Countly.

Where can I download the Countly server and client libraries?

While downloading from Github, we suggest you use the latest release, as the main branch is used for developing the next version and may be unstable.

Note that the Enterprise Edition is only downloadable after purchase.

How much time does it take to install Countly and the SDKs?

If your server has all the requirements, it takes approximately 10 minutes to install Countly and to get ready to start collecting data from devices. Follow the instructions in the Server Installation Manual. Note that installation and configuration do not require any developer skills, rather just a dedicated/virtual server for this purpose.

In order to integrate the SDK, you will need to know your KPIs before integration. This includes the custom events you need to track and whether you are going to implement Views and such. Depending on the list and analysis, this may take a few days.

Enterprise Edition customers have the right to rebrand Countly. While simple rebranding (custom logo, custom colors, etc.) takes less than a day to complete, complex rebranding (customization of menus, CSS modification, single-sign-on) would take longer.

If you have an iOS application, please take into consideration the submission to the Apple Appstore, as you have been including the Countly SDK in your iOS app.

What are the system requirements?

We develop, test, and use Countly on Ubuntu (for Community / Enterprise Editions) and Red Hat Enterprise Linux (for Enterprise Edition). A decent Linux machine can handle several hundreds (if not thousands) of requests per second. Depending on the load, as a minimum, you will need at least 1 CPU server with at least 1 GB RAM dedicated to mobile analytics, and at least 2 GB RAM for push notifications. You will also need to add swap space for cases where memory is not sufficient for MongoDB.

For exceedingly large amounts of traffic (several billions of requests per month), we sell and support the Countly Enterprise Edition, which scales horizontally using sharding technologies as your business grows.

64-bit support only

Due to MongoDB and 32-bit limitations, we only support new installations on 64-bit servers.

Which hosting provider do you suggest?

Any will do. We carry our tests on Google Cloud, Amazon, and Digital Ocean. Make sure you install Countly on a freshly installed, vanilla operating system without any servers running on it (e.g. LAMP stack, LEMP stack, etc.).

Is it possible to install on Digital Ocean?

Yes - and we have a fantastic Countly Digital Ocean Installer, right here. Go to this link, select a few parameters, and hit the "Install Countly" button. You'll have your Countly instance running in under 10 minutes!

Is it possible to use MongoDB Atlas with Countly?

You may go with MongoDB Atlas, which is a SaaS database solution from MongoDB. In this case, please get in touch with us beforehand for best practices and the necessary configuration advice.

What are the main differences between self-hosted and private cloud deployment?

There are a few differences you would need to look at before choosing a deployment option.

  Private cloud Self-hosted
Server setup Countly is responsible for the setup and configuration of the operating system, Countly server, MongoDB (including the replica set support), Ngnix, and additional components. Countly provides the customer with the recommended specifications and configurations for servers that will be used to host the software. The customer obtains and configures the servers according to these recommendations and installs the supported Linux OS along with Countly.
Maintenance Countly is responsible for the maintenance of the software and for the end-to-end health of the servers and network connectivity. Network related issues by 3rd party hosting companies are handled by them accordingly. The customer is responsible for the end-to-end health of the servers and network connectivity. Any maintenance related to Countly software is executed by the customer according to the directions provided by Countly.
Backups Countly establishes and executes backup procedures. The customer establishes and is responsible for backup procedures.
Upgrades Upgrades are automatically applied and tested by Countly after a new version is released. Upgrades are included as part of the subscription plan and are the responsibility of the customer to install and test. Countly provides documentation for installing any upgrades. Typically, there are 3 upgrades annually.
Monitoring Server monitoring is done using a 3rd party professional monitoring service. In case an issue occurs, the support staff is alerted immediately. Server monitoring is implemented by the customer and the customer is responsible for informing Countly regarding any app-level issues detected. Countly can make recommendations for server monitoring services if requested.
Support Countly has immediate and full access to the customer's instance in order to assist with investigating, recreating, diagnosing, and resolving any reported issues. The customer assists the Countly support team by documenting any issues, providing additional information as requested by Countly, and authorizing and approving remote access to the software upon Countly's request.

Which browsers does Countly run on?

We test Countly on Chrome, Firefox, and IE9+. A recent(ish) version of these modern browsers work well. We do not support IE8.

What's the programming language and underlying infrastructure?

Countly relies on MongoDB, Node.js and Nginx. The main programming language is JavaScript.

Why did you choose MongoDB and Node.js?

We searched for the most reliable and performance-centric stacks and chose our stack carefully. MongoDB and Node.js are used across the globe and are powered and trusted by tens of thousands of companies, from Foursquare to Adobe and eBay to McAfee.

Should I install Countly on a clean instance?

Short answer: Yes

Long answer: Countly is an analytics platform that installs several modules from trusted sources that we should know of, and when there is an issue with underlying core functions (e.g. MongoDB, Node, or Nginx), it becomes hard for us to understand where the issue stems from. Another reason is that we expect that Countly should solely be running on the instance where it is installed.

How can I keep the system up-to-date?

You may download the new version and install it on your server using the Countly upgrade script. Countly’s Community Edition also includes a plugin to automatically update from Github.

How much bandwidth does the Countly SDK consume?

Every 60 seconds the Countly SDK connects to the server and updates connection information. Each connection sends approximately 500 bytes of data from the SDK to Countly to be written to the database. Therefore, the network overhead is very negligible.

What's the recommended installation directory?

A directory to install the external package (e.g. /var directory, /usr/local, etc.) is just fine. If you happen to have a setup that reveals some folder to public access (for ex. public_html folder), you may want to avoid extracting Countly there.

Do I need a mail server?

Countly needs an MTA to send emails created by the admin to the user. Countly’s automated installer uses Sendmail by default.

How do I install an SSL certificate?

Out of the box, Countly uses port 80 and no SSL. If you prefer to encrypt communication and use HTTPS in favor of HTTP between devices & web pages and your server, you'll need to configure your nginx.conf file under /etc/nginx. Change the location of the ssl_certificate_key parameter below. Ensure the SSL certificate key is located under a directory that is not visible from the outside.

        ssl_certificate_key /PATH_TO_KEY.key;
        server_name  localhost;

        location = /i {
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Real-IP $remote_addr;

        location ^~ /i/ {
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Real-IP $remote_addr;

        location = /o {

        location ^~ /o/ {

        location / {
                proxy_set_header Host $http_host;

I installed Countly on an Amazon AWS but I cannot reach the dashboard

By default, Amazon doesn't allow you reach port 80. You should allow incoming connections to port 80 via the security group on your dashboard as you create your Amazon instance.

I installed Countly on Google Cloud, but the server cannot send emails

All outbound known mail sending ports are blocked on Google Cloud instances due to the large amount of abuse, and you will need to use third party services to send out emails. Google recommends you use one of the mailing service mentioned in their documentation.

Is it possible to run the dashboard and the database on different servers to increase security?

Countly has a server parameter for both app.js and api.js configuration files (/frontend/express/config.js and /api/config.js) to make it possible to run the dashboard and the application on different servers (defaults to localhost).

I installed Countly, but forgot my password

When you first installed Countly, chances are you haven't yet set up DNS or MX records, so the "forgot password" link won't work. In this case, you should create a global admin user from your console using the following command:

countly add_user  

Then, login to your dashboard with this user and password. You may then change the password of the user you have created before.

How can I restart Countly?

In order to restart Countly, type the following as root:

countly stop
countly start

How do I reinstall Countly?

Deleting the countly directory, extracting the new package to the same directory and running countly upgrade should do the trick. This is explained in the Upgrading Countly documentation. If you have an old server, we suggest you read this documentation first.

I installed CE and I would like to install EE on top. How can I do this?

When you install the Community Edition and would then like to install the same version of Countly Enterprise Edition on top, just run the countly upgrade.

If you would like to install a newer Enterprise Edition on top of the Community Edition, you should run upgrade scripts for each version as shown here.

Was this article helpful?
0 out of 0 found this helpful

Looking for help?