Enterprise installation
Seqera Enterprise requires a license. If you have not already purchased a license, contact us for more information.
Seqera Platform Enterprise is a web application with a microservice-oriented architecture that is designed to maximize portability, scalability, and security. It's composed of several modules that are configured and deployed according to your organizational requirements. Seqera provides these modules as Docker container images that are securely hosted on a private container registry.
Architecture
Platform backend
The Seqera backend is a JVM-based web application based on the Micronaut framework, which provides a modern and secure backbone for the application. The backend implements the main application logic, which is exposed via a REST API and defined with an OpenAPI schema. The backend uses JPA, Hibernate, and JDBC API industry standards to interact with the underlying relational database.
The backend can be run standalone or as multiple replicas for scalability when deployed in high-availability mode. It should run on port 8080.
Platform cron
Cron is an auxiliary backend service that executes regularly-occurring activities, such as sending email notifications and cleaning up stale data. The cron service also performs database migrations at startup.
Platform frontend
The Seqera frontend is an NGINX web server that serves the Angular application and reverse-proxies HTTP traffic to the backend. The frontend should run on port 80 within the container and should be the only service that accepts incoming HTTP traffic. The frontend can also be exposed via HTTPS or a load balancer.
Redis or Valkey cache
Seqera Enterprise requires a Redis-compatible cache store for caching purposes. Redis 7.2 and 7.4 are supported, as is Valkey 7.x. See Cache layer changes for migration guidance.
SQL database
Seqera requires a SQL database to persist user activities and state. MySQL 8.4 (LTS) is the recommended version. Contact Seqera support if you need to use a different JDBC-compliant SQL database.
- MySQL 8.4 (LTS) is the recommended and tested database version from Seqera Enterprise 26.1.
- MySQL 5.7 and 8.0 have reached upstream end-of-life and are no longer tested or supported. Migrate to MySQL 8.4 before upgrading to 26.1.
- For the full database support matrix, including AWS Aurora MySQL and MariaDB, see Upgrade.
SMTP service
Seqera requires an SMTP relay to send email messages and user notifications.
Authentication service (optional)
Seqera supports enterprise authentication mechanisms such as OAuth and OpenID. Third-party identity providers and custom single sign-on flows can be developed according to specific customer requirements.
Deployment options
Seqera can be deployed to a single node with Docker Compose, or to a Kubernetes cluster either with raw manifests or via the Helm chart. This documentation includes instructions for all options across multiple platforms, including Amazon AWS, Microsoft Azure, Google Cloud, and on-prem infrastructure.
Single-node
The minimal Seqera Enterprise deployment requires only the frontend, backend, and database services. These services can be deployed as Docker containers or as native services.
Kubernetes
Kubernetes is the recommended deployment target for production workloads requiring high availability and scalability. Seqera Enterprise supports Kubernetes deployments using raw manifests or the Seqera Helm chart.
Reference architecture diagram of Seqera Platform Enterprise on AWS using Elastic Kubernetes Service (EKS)
Application container images
Seqera Enterprise is distributed as a collection of Docker containers available through the Seqera container registry cr.seqera.io. Contact support to get your container access credentials.
Support
For further information, contact Seqera support.