Choose a Deployment Model
CAST Imaging can be deployed in three ways. Choose the model that best fits your infrastructure and operating constraints.
Before you start
| Who this is for | IT administrator planning a new installation |
| Role required | None (planning phase) |
| Prerequisites | None |
Comparison
| Model | Operating system | Best for |
|---|---|---|
| Windows installer | Windows Server | Single-server setups, teams already using Windows infrastructure |
| Docker (Linux or Windows) | Linux or Windows with Docker Desktop | Reproducible environments, easier upgrades, containerized infrastructure |
| Kubernetes | Any Kubernetes cluster | High-availability, scalable, enterprise-grade deployments |
Windows installer
The Windows installer packages all CAST Imaging components into standard Windows executables. Installation is straightforward and does not require container knowledge.
Choose this if: your team manages Windows servers and does not use containers.
See Install on Windows.
Docker
Docker Compose runs all CAST Imaging services as containers. Upgrades are simpler because you only replace container images.
Choose this if: you use Docker in your infrastructure, or you want a clean environment that is easy to reset.
See Install with Docker.
Kubernetes
Kubernetes distributes CAST Imaging services across a cluster. This model supports high availability and horizontal scaling.
Choose this if: you have a Kubernetes cluster and need enterprise-grade reliability or large-scale deployments.
Air-gapped environments
All three models can work without internet access. You must install a local extension server. See Install an offline extension server.
Next steps
Feedback
Was this page helpful?