Infrastructure and security
What sits under every service
Where it runs, how it is isolated, backed up and operated.
Where it runs
Three planes, two countries
Compute in the United States and Canada
VPS, containers and databases run there.
Edge plane on a global network
Objects, transactional email and images are served from the edge.
Backups in the United States, off-site copy in Canada
Kept apart from the service, with a second copy in another jurisdiction.
Compute and isolation
One virtual machine per customer
One VM per customer or service
Truo Deploy and every database run on their own VM.
NVMe storage
Across all compute and databases.
General or Dedicated
General shares the CPU; on Dedicated the cores belong to your VM.
Network
Networking included on every VPS
IP
Dedicated IPv4
Exclusive to your VM, no shared NAT.
Firewall
Rules in the network
Up to 20 per IP, from the panel.
Mitigation
Volumetric attacks
Filtered in the network, at no cost. Not a replacement for a WAF.
Traffic
Unmetered
No transfer quota and no overage charges.
Load balancing with managed HTTPS. We issue and renew the certificate. Load Balancer →
Data and backup
What is backed up, and where
PostgreSQL with managed backups
With pgBackRest, encrypted off the server, 7-day retention.
Security
Encryption and permissions per service
- Live
Managed TLS
A per-service CA on DBaaS; certificates that renew themselves.
- Live
Scoped API keys
Scoped to permissions and services; a key cannot create other keys.
- Partial
Human confirmation on destructive calls
The local MCP requires it before running a destructive action.
Operations
Panel, API, CLI and MCP
Panel
Create, scale and restore without opening tickets.
Public API v1
REST with a published OpenAPI spec.
SDK and CLI
Generated from the OpenAPI, published on npm.
Local MCP
truo mcp serve, read-only by default.
Sign-up for new services still goes through the cart.
Every service publishes its state. Available, Beta, Early access or Coming soon, on its own page.
What each state means →