> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getomni.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment Overview

> Choose the right deployment strategy for your needs

Omni supports two deployment strategies: Docker Compose and AWS Terraform.

## Deployment Options

<CardGroup cols={2}>
  <Card title="Docker Compose" icon="docker" href="/deployment/docker-compose">
    Development, small teams, single-server production. Get running in 10-15 minutes.
  </Card>

  <Card title="AWS Terraform" icon="aws" href="/deployment/aws-terraform">
    High availability, auto-scaling, multi-region. Production-ready in 30-45 minutes.
  </Card>
</CardGroup>

<Note>
  After deploying, follow the [Initial Setup](/deployment/initial-setup) guide to configure LLM providers, embeddings, and connectors.
</Note>

## Omni Components

All deployments include the same core components:

| Component                  | Purpose                                                               |
| -------------------------- | --------------------------------------------------------------------- |
| **omni-web**               | SvelteKit frontend and API                                            |
| **omni-searcher**          | Search query processing                                               |
| **omni-indexer**           | Document processing                                                   |
| **omni-ai**                | LLM and embedding orchestration                                       |
| **omni-connector-manager** | Orchestrate connector services                                        |
| **omni-sandbox**           | Isolated execution environment for agent tools (bash, Python, files)  |
| **omni-docling**           | Optional structured text extraction for PDFs, Office docs, and images |
| **PostgreSQL**             | Database with pg\_search and pgvector                                 |
| **Redis**                  | Caching and sessions                                                  |

Each connector runs in its own Docker container. Connectors are typically very lightweight services whose only job is to act as an interface between Omni and the third-party APIs. For reference, the built-in Google connector uses \~5MB memory at idle, and \~50MB during indexing.