On this page

Before installing Teamwork Cloud, ensure that the system requirements described in this chapter are met.

Cassandra installation

Teamwork Cloud requires Cassandra installation. To learn more about the hardware requirements for Cassandra, see https://cassandra.apache.org/doc/latest/cassandra/operating/hardware.html

Recommended system and storage requirements

Note on system requirements

System requirements are dictated by the intended deployment, taking into account the overall load which the environment will experience, including:

  • Number of concurrent users
  • Level of activity (commits) per day
  • Overall number and size of the projects stored in Teamwork Cloud.

The database (Cassandra) can be located on the same server as Teamwork Cloud or on a separate server. Storage requirements apply only to the node where the database is located. The product hosting nodes can be virtualized without any issues if the host is not oversubscribed on its resources.

Multi-Node Clusters

Recommended minimum sizing stated above applies to each node in a multi-node cluster.

Note on storage requirements

For on-premises deployment, Apache Cassandra is designed to run on multiple independent servers. Each Cassandra node should have Directly Attached Storage (DAS) composed of NVMe drives for optimum performance. Traditional network-attached storage solutions that rely on IP-based connections (iSCSI, NFS, or SAN) are not recommended for on-premises deployments, as they introduce additional latencies and anti-patterns. To learn more, see the following topics:

For cloud deployment, use storage technologies that have been benchmarked for Cassandra. Modern solid-state/flash arrays with fast interconnects are preferred. Note that Teamwork Cloud is not compatible with managed Cassandra services, such as Amazon Keyspaces. To learn more, see the following topics:

SAN Storage

SAN Storage should not be used on Cassandra nodes for data or commit log volumes. This will result in severe performance degradation. There is no amount of SAN tuning and OS tuning which could mitigate this.

Resource requirements by deployment type
Deployment typeRecommended system requirementsRecommended storage requirements
Teamwork Cloud AND Cassandra
  • 96 -128 GB ECC RAM
  • >=16 processor threads (such as E5-1660)
  • >1TB SSD DAS storage
  • 8 Processor Cores - i.e. Quad-Core Hyper-threaded CPU (such as Intel E3-1230 or faster).
  • 32 GB RAM (Motherboard with an ECC RAM is recommended) and 8 GB RAM dedicated for Teamwork Cloud

  • At least 3 separate disks, preferably SSD (NVMe), (OS/Application, Data, and Commit logs). Depending on company backup procedures and infrastructure, an additional disk, equal to the data disk in size, may be required for storing the backup snapshots. Please see Preparing the operating system

Only Cassandra
  • 48 - 64 GB ECC RAM
  • >=8 processor threads (such as E5-1620)
  • >1TB SSD DAS storage
Only Teamwork Cloud
  • 48 - 64 GB ECC RAM
  • >=8 processor threads (such as E5-1620)
  • >250GB storage

Software requirements

Teamwork Cloud supports the following operating systems:

  • Linux 64-bit RedHat/CentOS 7, RedHat 8.

  • Windows 2016 or Windows 2019.

Operating Systems

We recommend using the Linux operating system. For more information, please visit https://www.datastax.com/dev/blog/cassandra-and-windows-past-present-and-future.

For a full working environment, you will also need:

  • OpenJDK (Eclipse Temurin™ by ADOPTIUM) 11.0.14

  • FlexNet license server
  • Cassandra 4.0.3
  • A static IP address for each node.

  • Open ports 1101, 2181, 2552, 7000, 7001, 7199, 9042, 9142 between servers in a cluster.

  • Open ports 3579, 8111, 8443, and 10002 (default) for clients. The port number 10002 can be changed according to the port assigned to secure connections between the client software and Teamwork Cloud.

The following table lists the ports that Teamwork Cloud services use and their descriptions:

ServicePortDescription
FlexNet server (lmadmin)1101FLEXnet server port

8090Default vendor daemon port (web browser management port)

27000-27009Internal license server manager port



Cassandra7000Internode communication port (not used if TLS is enabled)

7199Cassandra JMX port

9042Native client port (used with 2021x version and later)

9142Native client port when SSL is enabled (then Cassandra is on a separate server or for multinode deployment)



Teamwork Cloud2552Teamwork Cloud default remote server port

3579Default Teamwork Cloud port when SSL is not enabled

8111Teamwork Cloud REST API port

10002 Default port for encrypted TLS client-server communication.



Web Application Platform8443Web Application Platform port (Teamwork Cloud Admin, Collaborator…)



Zookeeper2181Zookeeper internal port


For additional server capacity and performance recommendations, see https://cassandra.apache.org/doc/latest/cassandra/operating/hardware.html

If deploying on Amazon EC2

In the case of deploying on Amazon EC2, we recommend using the m5-2xlarge, r5-2xlarge, or i3-2xlarge instances.  Depending on the workloads, you may want to go to the -4xlarge instances, but for the vast majority of users, the -2xlarge will suffice. The m5 instances meet the minimum system requirements and will be acceptable for small deployments. The r5 instances provide more memory for the same CPU density. The i3 instances should be used when workloads have a higher level of user concurrency due to the significantly improved performance of the ephemeral NVMe storage.