Choosing the right deployment size starts with understanding your workload. This guide covers five reference tiers from single-node evaluation deployments through to high-availability Kubernetes clusters for production, using daily action runs as the primary scaling dimension.
All Tines self-hosted deployments consist of the same core components — tines-app (web server), tines-sidekiq (background worker), tines-command-runner (optional), PostgreSQL, Redis, and a load balancer / reverse proxy — scaled according to workload.
Deployment Options and Sizing Overview
💡Note
Tier 1: Small
Docker Compose (up to 100K actions/day)
All containers run on a single host. Suitable for evaluation, proof-of-concept, and small production workloads.
Tier 2: Medium
Docker Compose (up to 1M actions/day)
Single application host with externalized (managed) data services recommended. Suitable for small-to-mid production workloads.
Tier 3: Large
Kubernetes (up to 5M actions/day)
Multi-pod Kubernetes deployment with HA data services. First tier to support horizontal pod autoscaling and data tier redundancy.
Tier 4: X-Large
Kubernetes HA (up to 10M actions/day)
High-availability Kubernetes deployment. All data services run in HA pairs. This is the recommended production configuration for large-scale deployments.
Tier 5: XX-Large
Enterprise-scale high-availability deployment for the highest throughput requirements. Scales the Tier 4 reference architecture proportionally.