Your cloud
The runtime and agent run in your AWS, Azure or GCP account.
- Your team sets network and identity controls
- Connect the runtime to your existing logs and cost controls
- Choose a hosted model or one you serve privately
Deployment & data control
We build the agents. You choose whether the platform runs in your cloud, on your own infrastructure or in a Koru-managed environment. You also choose which models they call.
Discuss your deployment requirementsThree ways to run
The runtime and agent run in your AWS, Azure or GCP account.
Run on your hardware or in your data centre, including air-gapped environments.
We host and operate the deployment when you want us to handle the infrastructure.
The decision behind the decision
A customer-cloud deployment keeps the runtime and its records in your account. If that agent calls a hosted model, the selected request data goes to that provider. For a workflow with no permitted external egress, run an open-weight model inside your environment.
Review security and data handling| Choice | Where agent records live | Model path |
|---|---|---|
| Your cloud | Your account | Your selected provider or private model |
| Your infrastructure | Your network | Local model for no-egress workflows |
| Managed by Koru | Koru-managed environment | Agreed provider or private model |
Ownership
Koru Runtime is the platform that runs them. We define its deployment, access and ongoing terms in the engagement, so your team knows what it owns and what Koru operates.
A useful first conversation
Bring the workflow people actually follow, including the workarounds. We will trace where it gets stuck. Then we will agree on the approvals and one result to measure after launch.
Talk directly with the engineers who build the agent.