Tools

AI Copilot

Name: Nexoxa Bridge
Author: Nexoxa

Natural-language help grounded in your schema — BYOK.

The story

These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.

Schema in your head does not scale past three databases. Copilot grounds answers in the active connection catalog and knowledge graph — JOIN paths, index ideas, migration order — in plain English.

BYOK: your API key, your bill, your data residency choices. Credentials and row data never upload; schema metadata stays local.

Ask like you would ask a senior engineer who actually read the ER diagram this morning.

Bridge path: /ai

Step 1

Ask in plain language

Which tables reference users.id and what ON DELETE rules apply? Copilot cites foreign-keys from catalog, lists CASCADE vs RESTRICT.
No hallucinated table names — grounded in introspection.

Natural-language help grounded in your schema — BYOK. Open at /ai. BYOK configuration in settings. Schema graph from db-knowledge-out when available.

Step 2

Run suggested SQL

Copilot proposes an index CREATE — DBA reviews in chat, opens in Query lab, runs on staging.
Human in the loop stays default.

Send suggestions to Query lab. Pro features may extend graph context depth.

Step 3

Privacy by architecture

Passwords never enter prompts; only saved connection names and schema shape. Client compliance signs off because data stays on laptop.
Same vault rules as Connections grid.

AES-256-GCM vault. MCP uses names not URLs. BYOK keys stored per user policy.

This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for postgresql://, ssh://, sftp://, s3://, or smtp:// examples.

Related connections

Database connection URLs