Truo Deploy
deploy your containers, no server to manage
Push your docker-compose, your images or your git repository and the platform deploys, exposes and maintains it. You describe the stack, we operate the VM that runs it.
$ git push truocloud main
→ building the application…
→ configuring domain and TLS…
✓ deployed to production
COMPATIBILITY
Native Compose
Run your docker-compose without adapting it: volumes, networks and dependencies between services.
ISOLATION
One VM per client
Your environment runs in its own VM: its own kernel and Docker daemon, not shared with other clients.
DOMAINS
Automatic TLS
Connect your domains and the certificate is issued and renewed on its own, via the node's gateway.
MANAGEMENT
Self-service panel
Deploys, logs, environment variables and domains from the TruoCloud panel.
HOW IT WORKS
From your repository to production in 3 steps
A self-service deployment flow, without managing operating systems or servers.
Connect your code
Upload your docker-compose, point to your images or connect your git repository.
Configure
Set environment variables, domains and services from the panel. TLS is included.
Deploy and monitor
One-click deploys, live logs and redeploys whenever you need them, without touching a server.
USE CASES
For the stacks that force you to run a server today
If it runs in containers, it runs on TruoCloud CaaS.
Managed databases are out of scope: you can run Postgres or MySQL inside your own compose, but that runs without support and without managed backups. If you want a managed database, with backups and a dedicated endpoint, that's DBaaS.
APIs, web apps and workers
Deploy your services from a docker-compose without provisioning or maintaining a separate VPS.
Multi-service environments
App, database, cache and queue in the same isolated environment, with their own volumes.
The managed alternative
The same as installing Docker by hand on a VPS, but with the panel, TLS and isolation already solved.
COMPATIBILITY AND TLS
Your compose as-is, with domain and certificate handled
Truo Deploy runs real Docker, not a layer that resembles it: the same docker-compose.yml you use on your machine, with no translation into a proprietary format. You add your domain and the certificate is issued and renewed on its own.
docker-compose with no changes
The file you already have, with your services, volumes and networks. No proprietary manifests to learn and no half-supported subset of the format.
Or a Dockerfile
If you'd rather build from source, the image is built on your own virtual machine.
Automatic certificate
Add the domain, point the DNS and the certificate issues itself. Renewal is ours too: there's no cron job you forgot about.
TLS terminates at the edge
The gateway handles HTTPS and routes to your container by host name. You publish no ports and manage no certificates inside the VM.
Several domains per app
Add and remove domains from the panel whenever you want, and each one gets its own certificate.
No agent inside your containers
Nothing to install in your image. Your application doesn't know it runs here, so taking it elsewhere isn't a project.
Where our scope ends
Databases are out: a managed database is DBaaS. You can run Postgres, MySQL or Redis inside your own compose, but they run without support and without managed backups. And support covers the platform — the machine, the gateway, TLS, the panel and provisioning — not the application you deploy.
Your environment is yours alone
Every client gets its own VM. Nothing is shared with other tenants: no kernel, no Docker daemon, no network.
- ●
Own kernel
Your environment shares no kernel with any other client.
- ●
Exclusive Docker daemon
Your containers run on a daemon dedicated only to your VM.
- ●
Private network
No direct exposure: only your domains publish traffic outward.
- ●
Data that travels with you
Your volumes and databases live in your VM and are backed up along with it.
PLANS
Your environment's size follows your workload
You pick the size of the VM your stack runs on. The bigger it is, the cheaper the gigabyte of memory.