Convoy Cloud
REST for humans, ACP for agents. Both land on the same platform, route through the same control plane, and provision the same Convoy products.
Five primitives behind one workspace, one observability stack, and one API. Start with the one you need.
Every planned primitive, its current status, and the rationale behind it. No vaporware, no guessing when.
On-demand cloud machines for agents and builders, with templates, SSH, sleep, wake, and destroy flows.
Usage accrues by the minute with a 10-minute minimum, so small experiments stay small on the bill.
WhatsApp and Telegram bridges that can hand commands to a sandbox or app shell when you are away from your laptop.
Durable background jobs with retries, dead-letter handling, and metrics in the same workspace.
Cron-grade schedules for handlers that should wake up, run, and scale back down without a server.
03 · The shape of the work
The same four moves for every primitive: apps, functions, databases, sandboxes. Learn it once, apply it everywhere.
Point Convoy at a repo, image, function, database, or sandbox template. No YAML to write before you've even started.
Source becomes a runnable workload, Dockerfile or Buildpack, your choice, with build logs streaming live.
Public URL, isolated account boundary, TLS, secrets, autoscaling, and instant rollback. Wired in, not glued together.
Logs, metrics, alerts, events, and billing all roll back into the same account, on the same timeline.
04 · Inside the account
Apps, functions, databases, observability, and sandboxes share the same account, the same billing, and the same event stream. You don't stitch them together, they ship that way.
Hard isolation
Every account is fully isolated from every other. Cross-account traffic is blocked at the platform level, not by convention.
Metered in LKR
Per-minute resource accrual with a 10-minute floor. No fixed plans, no seat tax. PayHere mandate, invoiced every 14 days.
Unified event log
Deploys, alerts, member actions, admin actions, one tenant-scoped stream. 365-day retention, live over WebSocket.
Wired together
Apps, functions, and databases discover each other inside the same account boundary. Observability and events are shared, not bolted on.
05 · Why this exists
Convoy Cloud is shaped around three convictions about how modern software actually gets built.
Dashboard, CLI, GitHub, REST, sandbox templates. The same surfaces work whether a person is shipping or an agent is.
No fixed plans, no procurement theatre. Resources accrue in LKR per minute, with a 10-minute floor, and stop the moment the work does.
Apps, functions, databases, observability, and sandboxes share one account, one event log, one bill. The integration is the platform.
No fixed plans, no quantized tiers. Resources are billed by the minute in USD. Closed beta — join the waitlist to get early access.
For hobby projects and side experiments.
For teams shipping production workloads.
For larger teams and regulated workloads.
per vCPU-core / hour
per GiB memory / hour
Sample config
1 vCPU · 1 GiB · 2 replicas · 24×7
All prices are tied to Sri Lankan Rupees (LKR) and converted using live exchange rates. Rates are indicative and may fluctuate.
Convoy Cloud
Right-size your infrastructure from day one. Go to production with advanced features and zero complexity as you launch fast and scale with confidence.