Cloud infrastructure an AI agent can operate
VPS, containers, databases and load balancing. All over API, predictable and with clear permissions, so whoever provisions and runs the infrastructure can be your agent, not just a person clicking.
The premise
Less and less infrastructure is provisioned by a person with a mouse
Whoever spins up a server, deploys a container or creates a database today is not always someone in a panel: often it is a program doing it over API. Most clouds were designed for the first case.
TruoCloud starts from the opposite question: what does an agent need to operate this infrastructure without friction and without breaking anything. That decides what we build and in what order.
We do not sell GPUs or our own inference. We sell the primitives —compute, containers, data, network— that applications and agents use to run, designed to be consumed safely over API. Truo AI is a separate consumption layer, under the same account and the same invoice.
What holds it up
The pillars, with their actual status
Each one states what backs it. The ones that are still direction rather than product are not in this table.
Public API
api.truo.cloud/v1 with a published OpenAPI, SDK, CLI and local MCP. It is day-to-day management: signing up for a service still goes through the cart.
Declarative and predictable
Fixed-size plans and idempotent provisioning. An agent can ask for a resource and reason about the result.
Real isolation
Every service runs isolated: a dedicated VM per customer on Truo Deploy, a dedicated endpoint and TLS on DBaaS.
Rebuildable
Stateless services treat configuration as the source of truth and the machine as disposable. If something fails, it gets rebuilt.
Safe for agents
A key is scoped to specific services, inherits the permissions of whoever created it, and cannot create other keys or users. Destructive calls require human confirmation bound to the exact arguments.
Local MCP
truo mcp serve exposes one toolbox per family, read-only by default, generated from the OpenAPI. The remote MCP does not exist yet and we do not promise it.
How we publish
Four states, and none of them means whatever we want
Every service in the catalog carries one of these four states on its own page. It is the rule that stops us from selling as finished what is not.
| State | Public price | Self-service | SLA |
|---|---|---|---|
| Available | Yes | Yes | Yes |
| Beta | Yes | Yes | No |
| Early access | No | No | No |
| Coming soon | No | No | No |
A service in Beta is billed but carries no availability commitment, and its page names the concrete limitation that keeps it in Beta.
Where it runs
The infrastructure, without euphemisms
We say it plainly because it is the fact this industry dresses up the most, and because the privacy policy states it the same way.
Compute in the United States and Canada
That is where the machines running your services are. There is no presence in the European Union.
Edge plane on a global network
Object storage, transactional email and image processing are served from a globally distributed edge network.
Backups in the United States, off-site copy in Canada
Backups live apart from the service they protect, with a second copy in another jurisdiction.
Who invoices
The entity behind the brand
TruoCloud is a brand of Truobox SpA, a Chilean company. It is who issues the invoice and who the contract is with.
- Legal name
- Truobox SpA
- Tax ID (RUT)
- 77.545.997-2
- Registered address
- Agustinas 1022, oficina 1001, Comuna de Santiago, Región Metropolitana, CP 8320000, Chile
- Governing law
- Republic of Chile
The full agreement is in the Terms of Service, along with the other eight policies.