Skip to main content

​
Overview

This page compares methods for deploying a Speckle server on infrastructure your organisation operates. It does not compare self-hosting with Speckle Cloud. If you have not established that operating Speckle infrastructure creates value for your organisation or is required by a concrete constraint, start with Choosing a Speckle Deployment. Speckle Cloud remains the recommended deployment for most organisations. After choosing to self-host, select a deployment method based on factors such as:
  • Team size and expected user load
  • Technical expertise available
  • Infrastructure requirements and budget
  • Scalability needs and growth plans
  • Security and compliance requirements
  • Maintenance preferences and resources

​
Deployment Methods

Deployment support can change between Speckle releases. Confirm that a method is documented for the version you intend to run before designing your infrastructure around it. Docker Compose is a currently documented public OSS path for development, evaluation, and testing. Speckle does not recommend Docker Compose for production deployments. Customer-operated production deployments, including Speckle Enterprise Server, use Kubernetes. Enterprise deployments follow the prerequisites in the Enterprise License guide.

​
Docker Compose (Current Public OSS Path)

Best For: Development, evaluation, testing, and experimentation with versions of the public OSS distribution that document Docker Compose Key Benefits:
  • Simple Setup: Single command deployment with minimal configuration
  • Accessible Infrastructure: Runs on a Linux server with Docker support
  • Full Control: Complete control over infrastructure and configuration
  • Direct Operations: Updates, backups, and recovery can use the operator’s existing server tooling
Technical Requirements:
  • Docker and Docker Compose installed
  • Linux server with 4GB+ RAM and 20GB+ storage
  • Domain name and SSL certificate
  • Basic Linux administration knowledge
Use Cases:
  • Local development and contribution environments
  • Evaluation and testing
  • Short-lived experiments with the public OSS distribution
Limitations:
  • Single server deployment (no built-in high availability)
  • Manual scaling required
  • Limited to single geographic location
  • Requires manual maintenance and updates
  • Not recommended for production deployments

​
Kubernetes (Multi-Node and Enterprise Deployments)

Best For: Customer-operated deployments that require multi-node infrastructure, orchestration, or the licensed Speckle Enterprise Server product Key Benefits:
  • High Availability: Multi-node deployment with automatic failover
  • Auto Scaling: Automatic scaling based on load and resource usage
  • Placement Flexibility: Use clusters in the regions or cloud infrastructure you operate
  • Advanced Orchestration: Rolling updates, health checks, and auto-recovery
  • Infrastructure Controls: Load balancing, ingress management, and monitoring
Technical Requirements:
  • Kubernetes cluster (v1.33+) with at least 3 nodes
  • kubectl and Helm package manager
  • Gateway API enabled Kubernetes cluster or service mesh
  • Domain name and SSL certificates
  • Kubernetes administration expertise
Use Cases:
  • Public OSS deployments with high-availability or advanced orchestration requirements
  • Organisations with existing Kubernetes infrastructure
  • Licensed Speckle Enterprise Server deployments
  • Multi-region deployments where supported by the selected product and configuration
Limitations:
  • High complexity and learning curve
  • Requires significant infrastructure resources
  • Expensive for small deployments
  • Requires specialized Kubernetes knowledge

​
Comparison Matrix

​
Decision Guide

This guide applies after self-hosting has been chosen intentionally. If operating Speckle infrastructure does not create value for your organisation, use Speckle Cloud.

​
I need a public OSS development, evaluation, or test environment

Use: The Docker Compose path documented for your version:
  • Simple one-command deployment
  • Minimal configuration required
  • Works on any Linux server
  • Includes all necessary components

​
I chose public OSS for a production environment

Choose: Kubernetes:
  • Multi-node deployment with automatic failover
  • Auto-scaling capabilities
  • Advanced monitoring and orchestration
  • Suitable when your operations team is prepared to run Kubernetes

​
I need the Enterprise product in customer-controlled infrastructure

Evaluate: Speckle Enterprise Server:
  • Confirm that the licensed product and support boundary meet your requirements
  • Follow the Enterprise License guide
  • Plan for the required Kubernetes infrastructure and customer-operated data plane

​
Getting Help

Last modified on August 16, 2026