Connectors & Dialects

Database Setup & Dialects

Orcha Agent OS supports connecting to PostgreSQL, MySQL, MariaDB, Microsoft SQL Server, Oracle, and SQLite database systems with automated schema discovery and credential encryption.

👉 Looking for the visual step-by-step UI walkthrough from connection setup to live chatting?
View Visual Guide →

Supported Database Adapters

PostgreSQL

Default port 5432. Native SSL, partition statistics inspection, and schema namespace discovery.

MySQL & MariaDB

Default port 3306. Multi-host TCP fallback and INFORMATION_SCHEMA column metadata discovery.

Microsoft SQL Server

Default port 1433. Enterprise TDS protocol, sys.tables indexing inspection, and TOP/OFFSET transpilation.

Oracle Database

Default port 1521. Enterprise relational schema and dialect unparsing rules.

SQLite

Local file path resolution. In-memory execution and zero-network overhead for local testing.

PostgreSQL Configuration

When adding a PostgreSQL database via the UI (/configure) or via /api/test-connection:

json
{
  "type": "postgres",
  "host": "db.example.com",
  "port": 5432,
  "user": "postgres",
  "password": "your_secure_password",
  "database": "production_warehouse",
  "ssl": true
}

MySQL & MariaDB Configuration

json
{
  "type": "mysql",
  "host": "mysql.internal.network",
  "port": 3306,
  "user": "app_reader",
  "password": "your_secure_password",
  "database": "ecommerce",
  "ssl": false
}

MSSQL Server Configuration

json
{
  "type": "mssql",
  "host": "sqlserver.corp.local",
  "port": 1433,
  "user": "sa_readonly",
  "password": "your_secure_password",
  "database": "Northwind",
  "ssl": true
}

SQLite Configuration

SQLite connects directly to a file on your local filesystem without requiring host, port, or user credentials:

json
{
  "type": "sqlite",
  "filePath": "/absolute/path/to/database.sqlite"
}

Zero-Knowledge Credential Encryption

AES-256 GCM Envelope Encryption

Database passwords and connection strings are encrypted client-side or at the API boundary before being stored in Convex. The ENCRYPTION_KEY environment variable is only accessible by the secure server execution runtime.

At query time, the connection manager resolves and decrypts credentials just-in-time inside memory, opens an ephemeral connection pool, executes the query, and cleans up buffers.