Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jitera.ai/llms.txt

Use this file to discover all available pages before exploring further.

This guide provides reference architectures for three deployment scales. Each tier specifies the cluster resources and per-component replica counts needed to support the indicated number of concurrent users.
The user counts below are approximations based on internal testing. Actual capacity depends on workload patterns (e.g., frequency of code generation, number of concurrent AI chat sessions). Monitor resource utilization after deployment and adjust accordingly.

Tier Overview

TierUsersNodesCPU (total)Memory (total)Storage (per node)Databases
SmallUp to 101–312 cores48 GB200 GB SSDIn-cluster
Medium10–503–532 cores64 GB200 GB SSDIn-cluster or external
Large50+5+64+ cores128+ GB200+ GB SSDExternal recommended

Small (Up to 10 Users)

Suitable for development, evaluation, and proof-of-concept deployments.

Cluster Resources

ComponentMinimum
Nodes1–3
CPU (total)12 cores
Memory (total)48 GB
Storage (per node)200 GB SSD

Application Replicas

ServiceReplicasCPU RequestMemory Request
Frontend1200m256Mi
Automation (Rails)1500m1Gi
Automation (Sidekiq)1500m1Gi
Ultron1500m1Gi
Boost1500m512Mi

Data Store Resources

ServiceCPU RequestMemory Request
PostgreSQL500m1Gi
MongoDB500m1Gi
Redis250m256Mi

Medium (10–50 Users)

Suitable for production environments with moderate usage.

Cluster Resources

ComponentMinimum
Nodes3–5
CPU (total)32 cores
Memory (total)64 GB
Storage (per node)200 GB SSD

Application Replicas

ServiceReplicasCPU RequestMemory RequestCPU LimitMemory Limit
Frontend2500m512Mi11Gi
Automation (Rails)212Gi24Gi
Automation (Sidekiq)212Gi24Gi
Ultron212Gi24Gi
Boost2500m1Gi12Gi

Data Store Resources

For production workloads, consider externalizing databases to managed services (e.g., Amazon RDS, Azure Database for PostgreSQL) for automated backups and high availability.
ServiceConfigurationCPU RequestMemory Request
PostgreSQLPrimary + 1 read replica12Gi
MongoDB3-node replica set12Gi
RedisPrimary + 1 replica500m512Mi

Large (50+ Users)

Suitable for enterprise deployments with high availability requirements. External managed databases are strongly recommended.

Cluster Resources

ComponentMinimum
Nodes5+ (dedicated node pools recommended)
CPU (total)64+ cores
Memory (total)128+ GB
Storage (per node)200+ GB SSD

Application Replicas

ServiceReplicasCPU RequestMemory RequestCPU LimitMemory Limit
Frontend3+500m512Mi11Gi
Automation (Rails)3+24Gi48Gi
Automation (Sidekiq)2+24Gi48Gi
Ultron2+24Gi48Gi
Boost2+12Gi24Gi
Kong2+500m512Mi11Gi

Data Store Resources

Use external managed services with high availability enabled:
ServiceRecommended Configuration
PostgreSQLManaged service with multi-AZ / HA (e.g., Amazon RDS, Azure Database for PostgreSQL)
MongoDBManaged service with replica set (e.g., MongoDB Atlas, Azure Cosmos DB)
RedisManaged service with replication (e.g., Amazon ElastiCache, Azure Cache for Redis)
See Helm Values for configuration details.

Architecture Overview

System architecture and components

Supported Configurations

Infrastructure deployment models

Scaling Guide

Scaling strategies and auto-scaling

Helm Values

All configuration options