Scrydon
DeploymentPrerequisites

PostgreSQL

Bundled PostgreSQL and managed Postgres prerequisites

The Helm chart bundles PostgreSQL 18 with pgvector by default (infra.db.enabled: true). No external database is required for standard deployments; the bundled instance pre-creates every database the enabled services need.

Bring your own managed Postgres

If you prefer a managed instance (RDS, Cloud SQL, Azure Database for PostgreSQL, Supabase, Neon, CloudNativePG, …), set infra.db.enabled: false and pre-provision the following before running helm install. The chart's migration Jobs will crash on first install otherwise.

RequirementNotes
VersionPostgreSQL 15 or later
Extensionpgvector must be installable. Most managed providers ship it: RDS ≥ 15.3, Cloud SQL 15+, Azure Flexible Server with azure.extensions=VECTOR, Supabase, Neon.

Databases to pre-create. One per enabled component. Every component is enabled by default in the chart, so plan for all five unless you've disabled something:

DatabaseRequired whenpgvector?
authalwaysyes
agenticalwaysyes
analyticsanalytics.enabled: true (default)no
cortex (or cortex.database.name)cortex.enabled: true (default)yes
ontology (or apiOntology.database.name)apiOntology.enabled: true (default)no

Apply this against your managed Postgres before helm install:

CREATE DATABASE auth;
CREATE DATABASE agentic;
CREATE DATABASE analytics;   -- if analytics.enabled (default)
CREATE DATABASE cortex;      -- if cortex.enabled (default)
CREATE DATABASE ontology;    -- if apiOntology.enabled (default)

\c auth
CREATE EXTENSION IF NOT EXISTS vector;

\c agentic
CREATE EXTENSION IF NOT EXISTS vector;

\c cortex
CREATE EXTENSION IF NOT EXISTS vector;

See Managed Postgres (BYO Database) for per-provider notes, the corresponding infra.db.external.* Helm values, and connection-pooling guidance.

On this page

On this page