Platform features

Steps, owners and conditions are configuration, readable by the people who own the process.

A running process keeps the version it started on; new runs use the new version.

The approver sees the step, its inputs, the proposed action and the governing policy, and can approve, amend or reject.

The runtime retries a failed step and escalates to a person when confidence or policy requires it.

Specialised agents cover eight business domains, from finance and legal to supply chain and procurement.

An agent inherits only the permissions of the step it runs, for the duration of that step.

Model, prompt and policy versions are pinned and recorded, so every behaviour change is attributable.

Model usage runs through the platform gateway or through your own provider contract, billed at cost.

Policies carry authorship and history; you can diff two versions, promote one to production and roll back a change without touching process code.

Policies are scoped, so business units, regions or subsidiaries hold different limits under one platform.

A change reaches production only when the test suite passes the thresholds you set, compared version against version.

A wrong output in production is promoted into the test suite with one action, together with its inputs.

Inputs, outputs, cost, model version and approvals of every run are written to an immutable trace.

Cost is attributed per process, per team and per model, so budget reviews use measured numbers.

Trace retention is a policy setting, aligned to your records-management rules.

Traces export to your SIEM or data warehouse for long-term analysis.

Who may read traces, and which fields they see, is decided by the control plane.

Ask a running process a question by voice or text, under the same permissions you hold in the console.

Answers are retrieved under the asker's permissions, so a question never reveals data the person cannot already see.

Carol answers in English, Italian and German, including mixed-language questions about the same process.

Carol works in Microsoft Teams and Slack through the existing connectors, not only in the console.

A conversation keeps the process it is about, so follow-up questions do not need to repeat identifiers.

Connectors for 16 enterprise systems cover ERP, CRM, collaboration and document platforms.

Custom connectors are built under the Scale plan for systems outside the catalogue.

Connector credentials are held in the control plane and never exposed to agent prompts or process definitions.

[DA COMPILARE]

Development, staging and production hold separate credentials and separate limits.

Moving a policy or process version from staging to production is an explicit, recorded step.

Managed hosting runs in Switzerland or the European Union, with data-residency options on enterprise plans.

Enterprise plans deploy the platform into your own tenancy, under your operating responsibilities.

Untrusted content is isolated from instruction context, and tool access is authorised by policy rather than by model output.

Redaction rules run before any request leaves the environment.

Model routing can be restricted by jurisdiction, so data stays within the legal regions you allow.

Users and service accounts authenticate through your identity provider; roles map to policy, not to individual scripts.