Jitera Self-Hosted runs on Kubernetes and is deployed exclusively using Helm charts. You can install it on managed Kubernetes services (Amazon EKS, Azure AKS) or self-managed clusters, including air-gapped environments.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.
Before You Start
Recommended Deployment Architectures
For functional verification or development environments: We recommend building a Kubernetes cluster on a public cloud provider’s infrastructure and deploying Jitera in an In-Cluster configuration — all databases, caches, and message brokers run inside the Kubernetes cluster using the Helm chart defaults. For production or staging environments: From the perspectives of scalability and high availability, we recommend a configuration that utilizes external services for databases, caches, and messaging — for example, Amazon RDS, Azure Database for PostgreSQL, ElastiCache, or Azure Cache for Redis. See Architecture for supported deployment configurations, component details, and sizing guidance.Requirements
Deployment Requirements
Mandatory and optional requirements — Kubernetes cluster, credentials, LLM provider, DNS, storage, SMTP, and certificates
Deploy Jitera on a cloud provider
AWS EKS
Deploy on Amazon Elastic Kubernetes Service with S3, RDS, and SES integration
Azure AKS
Deploy on Azure Kubernetes Service with Blob Storage, PostgreSQL, and Communication Services
Offline Jitera
On-premises
Deploy on self-managed Kubernetes clusters, including air-gapped environments
Architecture
Architecture Overview
System architecture, reference deployments, and high availability
Sizing Guide
Resource sizing recommendations by deployment scale
Scaling Guide
Horizontal and vertical scaling strategies