How agents are stored (Enterprise)

Overview

In the Enterprise tier, agent definitions, configuration, and run state are stored in a way that supports isolation, auditability, and data residency requirements.

Storage model

Agent definitions and configuration – Stored per organisation in a dedicated namespace. Each organisation’s agents are logically isolated; configuration (tasks, integrations, schedules) is not shared across tenants.
Run state and execution data – Each agent run produces logs, findings, and task outcomes. These are stored with organisation and agent identifiers so they can be queried per workspace and retained according to your policies.
Artifacts – Outputs such as reports, generated files, or audit trails are stored in organisation-scoped storage with access controlled by your workspace roles.

Multi-tenancy

Data is partitioned by organisation (tenant). No cross-tenant access is possible at the storage or API layer.
Agent code and custom logic run in isolated execution environments; runtime memory and disk are not shared between organisations.

Enterprise agreements can specify where data is stored (e.g. region or jurisdiction). We support configurable deployment regions so that agent definitions, run data, and artifacts remain within your chosen geography where offered.

Retention and lifecycle

Retention for run logs and artifacts is configurable per organisation (within plan limits).
When an agent is removed or an organisation is closed, data is purged according to our Privacy and data processing terms.

Overview

In the Enterprise tier, agent definitions, configuration, and run state are stored in a way that supports isolation, auditability, and data residency requirements.

Storage model

Agent definitions and configuration – Stored per organisation in a dedicated namespace. Each organisation’s agents are logically isolated; configuration (tasks, integrations, schedules) is not shared across tenants.
Run state and execution data – Each agent run produces logs, findings, and task outcomes. These are stored with organisation and agent identifiers so they can be queried per workspace and retained according to your policies.
Artifacts – Outputs such as reports, generated files, or audit trails are stored in organisation-scoped storage with access controlled by your workspace roles.

Multi-tenancy

Data is partitioned by organisation (tenant). No cross-tenant access is possible at the storage or API layer.
Agent code and custom logic run in isolated execution environments; runtime memory and disk are not shared between organisations.

Data residency (Enterprise)

Retention and lifecycle

Retention for run logs and artifacts is configurable per organisation (within plan limits).
When an agent is removed or an organisation is closed, data is purged according to our Privacy and data processing terms.