Server Deployment#

Covalent supports both local and remote installation to suit different use cases. For quick prototyping and testing, running Covalent locally is sufficient.

For dispatching large compute-intensive workflows that require lots of CPU cores and memory, deploying Covalent as a remote server (cloud or on-premise) uses resources more efficiently. You can develop workflows locally, then dispatch them to the remote Covalent server for execution.

Covalent self hosted deployment

Deployment Instructions#

Click an option below for instructions on deploying to that platform.

On-Premise Deployment

Install the Covalent server on an on-prem server or virtual machine to create a centralized deployment.


Pull the pre-built container image from our public registries and run it in Docker.


Use systemd on a Linux host to manage a self-hosted Covalent server.

Cloud Deployment

Deploy on any major cloud platform to scale your deployments based on compute and memory needs.


Deploy Covalent in an AWS account with any x86-based EC2 instance.

Best Practices#

Whether you deploy on-prem or on a web service, there are some issues to be aware of that don’t apply when you run Covalent locally. This information will help you avoid some common remote deployment pitfalls.