In selfhosted mode, the database, files, and supported search services can run on your infrastructure. AI processing can remain local or use a provider you configure; image delivery, telemetry, and integrations determine the deployment's actual egress boundary.

How it works

The portable deployment uses PostgreSQL for structured data and local or S3-compatible storage for files. Supported search and AI workloads can use local services, while configured hosted providers remain explicit egress choices.

Storage architecture showing local database, file storage, and optional providers

Why it matters

Local storage lets privacy-sensitive teams keep the core knowledge data plane within infrastructure and regions they operate. The deployment documentation identifies which optional services create external dependencies so operators can choose an appropriate custody profile.

Local deployment boundary with optional external services

Related Features

Data Portability & Selfhosted

Selfhosted Deployment

Containerized local stack on infrastructure you control.

Encryption & Privacy

Vault Encryption

Encrypt entire vaults; content only readable by key holders.

Previous

MCP Server Included

Get early access to Local Storage

Create your free account and get access to Local Storage today.

Get Started