When you download the pre-built CrateDB packages from the Crate.io website, you are downloading the edition that comes with Enterprise Features. If you want to run CrateDB on more than three nodes, you must acquire an Enterprise License.

When you build CrateDB from source, you get the CrateDB Community Edition which does not come with enterprise features and does not have any node limitations.

See also

For more information about the different editions of CrateDB, consult the overview product comparison.

For more detailed licensing information, please contact us directly or consult the information in the NOTICE and LICENSE files.

Table of contents


Take note of the following items when using this edition of CrateDB.

Node limitation

To make full use of CrateDB, you must acquire an Enterprise License. Unless and until you do that, CrateDB is limited to running on no more than three nodes.


An Enterprise License will be provided at no cost for use by non-profit and educational organizations. Limitations apply. Please contact us.


If you exceed the three-node limitation, your cluster will stop accepting queries and CrateDB functionality will be limited to the following SQL statements:

To restore functionality, you must SET LICENSE or scale down to three or fewer nodes.

If you wish to use CrateDB without an Enterprise License and without the three-node limitation, you can switch to the CrateDB Community Edition.

CrateDB Community Edition

The CrateDB Community Edition (CrateDB CE) does not include any Enterprise features but can be run on as many nodes as you wish.


CrateDB requires a Java virtual machine to run.

Starting with CrateDB 4.2, a JVM is bundled with the tarball and no extra installation is necessary.

Versions starting from 3.0 to 4.1 require a Java 11 installation. We recommend using Oracle’s Java on macOS and OpenJDK on Linux Systems.

Earlier versions required Java 8.

CrateDB CE must be built from source:

sh$ git clone https://github.com/crate/crate
sh$ cd crate
sh$ git checkout <TAG>
sh$ ./gradlew clean communityEditionDistTar

The steps above:

  • clone the CrateDB Git repository and navigate into the directory
  • replace <TAG> with the Git tag that corresponds to the release you wish to use or just the version number of the release
  • execute the Gradle Wrapper script included in the repository to clean up any old build files and to invoke a distribution plugin that will build the Community Edition tar archive

When the gradlew command completes successfully, the relevant CrateDB CE release tarball will be located in the app/build/distributions directory.

You can refer to our guide on running CrateDB tarball installations.


How helpful was this page?