Security, by responsibility.

Choose who operates the infrastructure. Keep model access and workflow permissions explicit. Review the record of what ran.

01 / Who operates what

Two deployment options. Clear ownership.

On Cloud, we operate a virtual machine for your instance. With a customer-managed deployment, you provide the infrastructure. Your team chooses the connected systems and model account in both.

Scroll sideways to compare both deployment options.

Responsibilities for each Runtara deployment option
Responsibility	Runtara-managed Cloud	Customer-managed
Infrastructure	Runtara provisions and manages a VM for your instance.	You provide and manage infrastructure in your cloud or on-premises.
Hosting location	Hosted data stays in-region in the EU.	You choose the location and network configuration.
Business-system access	You choose the connections and their permissions.	You choose the connections and their permissions.
Model account and bill	Your credentials, your chosen endpoint, your provider bill.	Your credentials, your chosen endpoint, your provider bill.
Runtime updates	Runtara operates the hosted instance.	You apply supplied updates on your infrastructure, with routine update assistance included in Enterprise.

On Cloud, Runtara processes data on your behalf. Review the data processing agreement and deployment terms for the arrangement you will use.

02 / Bound the workflow

Every external action has a declared path.

The authored workflow compiles to WebAssembly. It requests named host calls; the runtime checks each request against the connection and scope declared for that step.

Workflow execution boundary

01 / INPUTDocuments and records
Data enters the workflow.
02 / SANDBOXCompiled workflow
No direct filesystem, network, or credential access.
03 / HOST CALLRuntime checks scope
Only declared connections and resources are permitted.

Permitted request → Configured system or model endpointUndeclared request → Denied and recorded

The execution boundary

A workflow cannot reach an arbitrary host or resource. Each external effect passes through the runtime's declared host-call interface.

Inspect an execution example

RUNTIME / SANDBOXAMBIENT ACCESS / NONE

PreventsWorkflow logic inheriting the host process's authority

Read invoice filefile.read / RUN INPUT

Fetch PO-4471erp.purchase_order.get / PO-4471

Call modelmodel.invoke / CUSTOMER ENDPOINT

Reach undeclared hostvendor-admin.internal / DENIED

WORKFLOW ARTIFACTinvoice-run.wasmHASH / 8F3A7C21

Would fail only ifA runtime maintainer changed the host binary to expose a capability the workflow did not request; that change would be visible in the build diff.

The model's tool set

The model chooses from tools fixed when the workflow is authored. Adding a capability requires a workflow edit, review, and a new compiled binary.

Inspect a model capability example

AI STEP / INVOICE-EXTRACTCOMPILED

PreventsA model discovering or acquiring tools at run time

Compiled tool set4 AVAILABLE

document.readRead the current invoice

purchase_order.lookupRead PO-4471

goods_receipt.lookupRead GR-8832

exception.holdHold line 04 for a person

Model requestDENIED

vendor.bank_account.update

Not present in the compiled tool set. No call was made.

To add that capabilityedit workflow → review diff → compile new binary

Would fail only ifThe reviewed workflow itself granted the additional tool.

03 / Review what happened

Evidence follows the work.

Your instance database keeps the context, actions, and decisions together. Inspect an individual run without assembling its history from separate exports.

INPUT

What the step received

Inspect the source values and inputs used at that point in the run.

ACTION

What the system returned

Follow machine events and the outputs of calls to connected systems.

DECISION

Who approved the next step

Review the human response and timestamp alongside the resulting action.

View an example audit query

Illustrative invoice run INV-0847: one query returns the machine events, approval, and ERP write.

AUDIT / INV-08475 EVENTS

QueryONE STATEMENT

SELECT e.occurred_at, COALESCE(u.display_name, e.actor_type) AS actor,
       e.event_type, e.input_data, e.output_data
FROM workflow_runs AS r
JOIN workflow_run_events AS e ON e.run_id = r.id
LEFT JOIN users AS u ON u.id = e.actor_user_id
WHERE r.reference = 'INV-0847'
ORDER BY e.occurred_at ASC;

03 MAY · 09:41systemrun.receivedINV-0847.pdfrun created

03 MAY · 09:43modelextract.completedinvoice document6 lines · €23,610

03 MAY · 09:46systemmatch.completedPO-4471 · GR-8832line 04 held · €1,240

26 MAY · 15:18K. Nowakapproval.recordedline 04 · €1,240approved

26 MAY · 15:27systemerp.postedapproved invoiceBusiness Central · 200 OK

SourceInstance PostgreSQL · one result set · no log export

04 / Your infrastructure

Customer-managed deployment

Deploy in your cloud or on-premises. Your team provisions, operates, secures, and backs up the infrastructure, and applies the software updates we supply. Enterprise includes routine update assistance and agreed operational support, with responsibilities defined in your proposal.

Review the connected data paths

Your workflows use the systems and model endpoints you configure. Where you use Runtara's hosted gateway, interface requests and configuration or authentication data may transit Runtara infrastructure, as described in the deployment terms.

Fully air-gapped environments

A fully air-gapped installation has no route to Runtara infrastructure. Updates are delivered as artifacts for your team to apply. Model endpoints and business systems must be reachable within the permitted environment.

Read the deployment terms →

05 / Security review

Documentation for your security review.

Enterprise includes architecture and data-flow documentation, security questionnaire assistance, and a review of deployment responsibilities. We help your team understand how Runtara fits your environment and internal requirements.

Current SOC 2 status

Runtara does not currently have a SOC 2 report. SOC 2 is on our roadmap. The documentation and assistance we provide today support your review; they are not an independent audit opinion.

Scope matters for every deployment

Any future SOC 2 report would apply only to the services and controls within its stated scope. It would not automatically cover your cloud or on-premises infrastructure. Your access controls, network, backups, and operating procedures remain your responsibility and part of your own security assessment.

Bring your technical questions.

Review the AGPL-3.0 runtime source, or ask us for architecture documentation, data flows, and answers to your security questionnaire.

Discuss your deployment