Agent DB

Agent DB gives Reaktors persistent SQLite storage. As an administrator, you create and manage databases from the Agent DB page in the sidebar. Developers reference these databases by ID in their App settings.

Viewing Databases

The Agent DB page lists all databases in your organization with the following columns:

Column	Description
Database ID	The identifier developers use in code and App settings
Name	Human-readable name
Description	Optional description of the database's purpose
Created At	Creation timestamp
Created By	User who created the database
Size	File size of the database

Use the search bar to filter by name, description, or database ID.

Creating a Database

1. Click + Create Database at the top right.
2. Enter a Name (e.g. chat-db, knowledge-base).
3. Enter an optional Description.
4. Click Create.

The platform generates a unique database ID. Provide this ID to the developer or enter it directly in the App Instance settings when configuring a Reaktor that requires a database. Multiple Reaktors can share the same database by using the same ID.

Deleting a Database

Click Delete on a database row and confirm. This permanently removes the database file and all its contents.

warning

Deletion is irreversible. Verify that no running App Instances reference the database before deleting. Reaktors that reference a deleted database will fail at runtime.

Transferring Databases Between Instances

Agent DB supports exporting and importing databases between Operaide instances. This is useful for migrating data from development to production, creating backups, or synchronizing databases across deployments.

Exporting a Database

Export sends a copy of the database to a remote Operaide instance.

1. Click the ... menu on a database row and select Export.
2. Enter the Sync URL of the target instance. This is the target database's sync URL, visible on the Agent DB page of the remote instance.
3. Enter an API Key for the target instance. The key must belong to a user with the Agent Database Importer role on the target.
4. Click Export.

The platform creates a snapshot of the database and uploads it in chunks to the remote instance. Progress is shown in real time. You can cancel an ongoing export at any time.

Importing a Database

Import downloads a database from a remote Operaide instance and overwrites the local copy.

1. Click the ... menu on a database row and select Import.
2. Enter the Sync URL of the source database on the remote instance.
3. Enter an API Key for the source instance. The key must belong to a user with the Agent Database Exporter role on the source.
4. Click Import and confirm.

warning

Import overwrites the local database. The previous contents are replaced entirely. There is no merge — the remote database replaces the local one.

Transfer Details

• Chunked and resumable — large databases are transferred in chunks. If a transfer is interrupted, it resumes from the last successful chunk.
• Integrity verification — file hashes are verified after assembly to detect corruption.
• Non-blocking snapshots — exports use SQLite hot backups, so the database remains usable during transfer.
• Progress tracking — transfers show 0-100% progress. Transfers that stall are cleaned up automatically after 24 hours.

Permissions

Permission	Description	Default Roles
Access Agent Databases	View the database list	App Manager
Create Agent Database	Create new databases	App Manager
Edit Agent Database	Edit database name and description	App Manager
Delete Agent Database	Delete databases	App Manager
Export Agent Database	Export to a remote instance	Agent Database Exporter
Import Agent Database	Import from a remote instance	Agent Database Importer

SuperAdmin users can access databases across all organizations. All other roles are scoped to the current organization.

Common Mistakes

• Using different database IDs across Reaktors that should share data. When an App has multiple Reaktors that operate on the same data (e.g. the Chat App's chat-api, message-api, and assistant-api), enter the same database ID in every Reaktor's settings.
• Deleting a database while App Instances still reference it. Check App Instance settings before deleting.
• Forgetting the API key role for transfers. Export requires the Agent Database Exporter role on the source instance's API key. Import requires the Agent Database Importer role on the target instance's API key. These are separate from the App Manager role.