Skip to main content

Compliance

Deployment Options

Where agents and data run is agreed per project. Most implementations use Multibot-managed cloud infrastructure; other arrangements can be discussed when your requirements need them.

Conceptual data handling: selected fragments move from a document tray into a container, past a retention hourglass and a region marker, to a checked record.

Options to discuss

Availability depends on the components and providers each workflow needs.

Managed cloud

Multibot operates the agents and integrations on managed cloud infrastructure.

Customer-controlled components

Some components, such as connectors or data stores, can run in your environment where agreed.

Provider and region choices

Model and hosting providers, and where possible regions, are chosen to meet your requirements.

How the decision is made

During scoping, with your IT and data protection leads.

01

Requirements

Data residency, security and integration needs.

02

Options

What each component allows.

03

Trade-offs

Cost, maintenance and capability.

04

Agreement

Documented architecture before build.

Clarity before build

You know where each part of the workflow runs.

  • Document which components run where.
  • List the providers that process data.
  • Agree how updates are deployed.

Common questions

It depends on the models and services the workflow needs. We will tell you what is possible for your case rather than promise a full on-premise deployment by default.

We choose the model and provider for each task during scoping, based on the language, accuracy, latency and data-handling requirements. The workflow is not tied to one provider, so a step can be changed later if the agreed requirements change.

Discovery call

Start with the work that slows you down.

Bring us a process, a recurring enquiry or a pile of documents. We will explore where agents fit and what a useful implementation needs.

Book a discovery call