Bring Your Own Storage

Overview

By default, Ingate stores all data (logs, prompts, evals) in the Ingate-hosted database. With BYOS, you provide your own PostgreSQL instance. Ingate transparently routes all data operations for your organization to your database.

How It Works

1. You provide a PostgreSQL connection URL via the API
2. Ingate validates connectivity by test-connecting and pinging
3. The URL is encrypted with AES-256 and stored in the central database
4. On the next request, Ingate creates a connection pool to your database
5. Schema migrations run automatically on first connection
6. All subsequent reads and writes for your org use your database

Configure BYOS

curl -X PUT https://api.ingateai.com/api/v1/orgs/{org_id}/storage \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"postgresql_url": "postgres://user:pass@your-db.example.com:5432/ingate?sslmode=require"}'

The URL is validated before storage. Ingate connects, pings, and reports the latency:

{
  "configured": true,
  "postgresql_url": "postgres://user:***@your-db.example.com:5432/ingate?sslmode=require",
  "ping_ms": 12
}

Check Status

{
  "configured": true,
  "postgresql_url": "postgres://user:***@your-db.example.com:5432/ingate?sslmode=require",
  "status": "connected",
  "ping_ms": 12
}

Test Before Committing

Remove BYOS

Connection Management

• Per-org pools are lazily created on first request and cached in memory
• Pools are health-checked on every request with automatic reconnection on failure
• Idle pools are evicted after 10 minutes to conserve resources
• Maximum 5 connections per org pool (configurable)

Requirements

• PostgreSQL 14 or later
• Network connectivity from Ingate to your database (whitelist Ingate IPs)
• SSL recommended (sslmode=require or sslmode=verify-full)
• A dedicated database (Ingate manages the schema via migrations)