Home / Connectors / MariaDB
Database · Catalogue source

MariaDB × ServAI

Connect MariaDB to the ServAI Data Intelligence Role Pack with explicit data boundaries, read-only execution, human approval and traceable evidence.

Start a connection assessmentAll connectors
CategoryDatabase
Connection routeCatalogue source
Data modeRead-only
Publish authoritySeparate human release
What can be connected

The MariaDB data you approve—not the whole account.

ServAI can read approved tables or views containing transactions, master data and operational records. An administrator defines the allowed datasets, fields, query windows and sensitivity ceiling. Exact availability depends on the customer’s MariaDB plan, permissions and source configuration.

Boundary ruleThe agent cannot select an arbitrary account, table or resource from its prompt. Scope must be registered and approved first.
What Data Intelligence can do
  • Profile freshness, completeness and distribution
  • Compute approved KPIs and reconciliations
  • Explain trends, variance, segments and exceptions
  • Draft traceable dashboards and executive findings
How the connection works

Configured, admitted and health-gated.

Implementation differs by connector state. These are the actual boundaries for this ServAI catalogue entry.

01

Catalogue stage

The source has been named and classified only; no production-ready connector is claimed.

02

Build and review

A route needs implementation, read-only boundaries, tests, security review and health reporting.

03

Admit before use

A person must approve configuration, fingerprint and data scope before any read can become possible.

Governed path

From source to a verifiable dashboard.

Connecting a source does not grant authority to change data, define metrics or publish.

  1. 01Configure connection
  2. 02Review & admit
  3. 03Approve meaning
  4. 04Read-only query
  5. 05Dashboard & evidence
  6. 06Different-person verify
  7. 07Separate release
What you need

Deployment requirements

  • Proposed use-case and data scope
  • Read-only connector design
  • Tests, security review and health monitoring
  • Implementation and configuration approval before use
What this connector cannot do

Fixed boundaries

  • ServAI does not write to MariaDB or change source records.
  • No self-admission, self-approval of metrics or self-verification of dashboards.
  • The agent cannot submit raw SQL or arbitrary resource names.
  • A catalogue listing never means a customer connection is operating.
Status truth

Catalogued—not live

The customer control surface shows actual per-tenant state: operational, needs attention, or catalogued—not live. ServAI never turns a logo into a connection claim.

OperationalAdmitted and health passing
Needs attentionConfiguration, health or entitlement needs action
Catalogued—not liveNo admitted customer connection
MariaDB + Data Intelligence Role Pack

Start with data scope—not a connector logo.

We will establish route state, requirements, human ownership and data boundaries before treating the connection as ready.

Start a connection assessmentExplore the Role Pack