Security model

Deployment responsibilities

On Cloud, Runtara operates 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.

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

Execution controls

Runtara runs each workflow in a WebAssembly sandbox. The authored workflow compiles to WebAssembly and has no direct access to files, the network, or credentials. It requests named host calls, and the runtime checks each request against the connection and scope declared for that step.

The execution boundary

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

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.

Audit evidence

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

• What the step received. The source values and inputs used at that point in the run.
• What the system returned. Machine events and the outputs of calls to connected systems.
• Who approved the next step. The human response and timestamp alongside the resulting action.

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;

Customer-managed and air-gapped 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

An air-gapped deployment has no network route to the public internet in either direction. 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; because model calls always use your own credentials and endpoint, AI steps can run against a model endpoint you operate inside it.

Read the deployment terms

Security review and SOC 2

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.