Skip to content

Local AI and external models

Run selected models locally. Add an external provider only for the tasks and information you explicitly allow.

Choose where the work runs.

Local and hybrid are explicit architecture choices. The diagrams show proposed request routing—not live access to your systems.

Illustrative architecture
Your controlled environment
01 / ContextApproved
company records

The information this workflow is allowed to use.

02 / ControlWorkflow
& routing rules

Access checks, task boundaries and review steps.

03 / Local modelYour local
AI system

Selected models run on your infrastructure.

Optional external routeFrontier model API

Disabled in this mode

Local only

Model processing stays local.

The workflow uses local models and the approved records available in your environment. External model calls are disabled for this route.

When hybrid is useful

When an external model helps

Some tasks may benefit from a frontier model. Using an API means sending information to another provider. We make that decision visible in the workflow design.

  1. 01

    Choose permitted tasks and providers.

    Define which workflows can call an external service and which must remain local.

  2. 02

    Limit what can leave.

    Specify allowed fields, minimize the payload, and apply the required redaction and approval checks.

  3. 03

    Test and record the route.

    Validate blocked paths, log the relevant actions and agree provider retention and data-handling terms.

Keep exploringExplore permissions and review