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 many CPU cores and a lot of 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.
Click an option below for instructions on deploying to that platform.
Pull the pre-built container image from our public registries and run it in Docker.
systemd on a Linux host to manage a self-hosted Covalent server.
Deploy Covalent in an AWS account with any
x86-based EC2 instance.
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.