Aviato / docs

How Aviato fits together

A shared vocabulary for workspaces, projects, environments, connectors, and collections.

View Markdown
ConceptWhat it means
WorkspaceYour team, membership, subscription, and shared administration.
ProjectOne connected application and its configuration.
EnvironmentAn isolated connection within a project, such as production or staging. Members can also run their own development environment, and CI can open preview environments.
Database connectorThe service that runs next to your database and enforces data access.
CollectionA database table, MongoDB collection, or custom collection exposed by a plugin.
RecordAn item in a collection, identified by its primary key.
ActionA named operation defined by your development team.
PluginYour application code extending the connector through a language SDK.
MCP clientAn AI application connecting to the connector through Model Context Protocol.

The connector and the control plane

The database connector connects to your data sources. Your browser and authorized MCP clients request records from that connector. It applies permissions, runs operations, and queues audit events.

The control plane manages sign-in, workspaces, roles, connector configuration, approvals, and audit services. It does not connect directly to a self-hosted database. Some features send selected data through the control plane; see data flow.

Connector and AI agents

Aviato's database connector is infrastructure you deploy. An AI agent is a client, such as an assistant using MCP, which sends requests to it. Connecting an AI agent does not grant unrestricted database access.

Environments are separate

A record ID is only meaningful within its collection and environment. A customer numbered 42 in staging is not the same record as customer 42 in production. Check the environment selector before editing, running actions, or reviewing an approval.

Permissions follow the request

Workspace roles provide baseline access. Custom project roles can narrow it. MCP scopes further constrain what an AI client can do. A plugin using the connector's Data API operates under the caller's permissions.

From a collection to an audited change

The record guide walks through a real connected Customers collection. A teammate opens a row, saves an edit through the connector, and checks the resulting event in record activity and the audit log. The screenshots use a disposable database with fictional example data.

Edit on GitHub

On this page