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

# BYOC | Collate

> Deploy Collate components in your own Kubernetes cluster while Collate manages the SaaS control plane.

# Bring Your Own Cloud (BYOC)

BYOC lets you run Collate components inside your own Kubernetes cluster while Collate manages the SaaS control plane.

Your data and inference traffic never leave your environment. The BYOC component communicates with the Collate Server over gRPC, with the connection initiated outbound from your cluster.

Collate never stores or accesses the credentials used to connect to your infrastructure — those are managed by your own environment and retrieved at runtime.

## Architecture Overview

<img src="https://mintcdn.com/collatedocs/2giDsuIWet2v3d__/public/images/collate-ai/byoc/caip-architecture.png?fit=max&auto=format&n=2giDsuIWet2v3d__&q=85&s=6db9d8cd18f0bb9545fe52c8c84abf3a" alt="BYOC deployment architecture showing communication between the Collate SaaS control plane and the component running inside your Kubernetes cluster" width="2048" height="1830" data-path="public/images/collate-ai/byoc/caip-architecture.png" />

## Requirements

### Hardware

The BYOC pod requires at least the following resources on the Kubernetes node where it runs:

* CPU: `2000m - 4000m` (2-4 cores)
* Memory: `12Gi - 16Gi` (12-16 GB RAM)
* Storage: No persistent storage required — the service is stateless.

### Software

* Kubernetes **1.19 or later**
* Helm CLI and `kubectl` installed locally
* An existing Collate installation running in your cluster

<Note>
  Collate BYOC requires **OpenSearch** as the search engine. ElasticSearch is not supported because Collate AI relies on OpenSearch's vector capabilities for Semantic and Hybrid Search.
</Note>