Use cases

What you can build with Convoy Cloud.

The same set of primitives, shaped around the work you actually do. Pick the path that matches your team and we handle the rest.

01 · Ship and scale with zero infrastructure overhead

Ship Production-Ready Apps & Services

Problem

Deploying into production means wiring together pipelines, servers, networking, security, kubernetes, scaling rules, rollback logic, and so much more before you ship a single line of product code.

Solution

Deploy any application as a containerized workload from your source code or an image. Your app lands on a secure, highly available, fully-managed runtime with production features like auto-scaling and fine grained observability built in.

  • Deploy from a repo or a container image, build with a Dockerfile or buildpacks
  • Auto-scaling, observability, alerting, private networking and internal service discovery built in
  • Deploy through progressive environments and health gates with zero downtime and automatic rollbacks
feat: add user auth
maina3f1c09
Pushedmain · a3f1c09
BuildingDockerfile · 14s
Pushingregistry.convoy-tech.com
Deployedmy-app.convoy-tech.com
my-app.convoy-tech.com
02 · Full-stack visibility of everything, everywhere, all the time

Observability as a Service

Problem

Bootstrapping and managing observability into applications and self managed infrastructure wastes crucial engineering resources and adds cognitive load. Most teams end up with a loosely centralised picture and accumulate unnecessary technical debt in the process.

Solution

Every Convoy resource ships with full observability wired in. Convoy Observability (our managed observability offering) provides fine-grained metrics and logs for all resources in a centralised interface. A highly configurable alerting engine allows you to build an SRE framework within your team without the overhead of managing your own observability stack.

  • Zero-setup, industry standard observability into every Convoy resource
  • Alerts to catch issues in production before they impact users
  • No additional cost
Metrics24h
cpu42%
mem68%
req/s1.2k
Logs
12:04:32infoGET /api/apps 200 12ms
12:04:31infoGET /healthz 200 2ms
12:04:28warnPOST /deploy 429 rate limited
12:04:25infoGET /api/metrics 200 8ms
12:04:22errPOST /webhook 500 timeout
12:04:19infoGET /api/apps 200 14ms
12:04:15infoGET /healthz 200 1ms
12:04:11warnGET /api/logs 408 timeout
12:04:32infoGET /api/apps 200 12ms
12:04:31infoGET /healthz 200 2ms
12:04:28warnPOST /deploy 429 rate limited
12:04:25infoGET /api/metrics 200 8ms
12:04:22errPOST /webhook 500 timeout
12:04:19infoGET /api/apps 200 14ms
12:04:15infoGET /healthz 200 1ms
12:04:11warnGET /api/logs 408 timeout
03 · Serverless on-demand code execution for nanoservices

Build serverless backends

Problem

Persistent long-running workloads are unnecessary and cost inefficient for many nanoservices. Yet they need to run on a highly available runtime that can securely and seamlessly integrate with the other services in your stack.

Solution

Convoy Functions are ephemeral workloads that execute on-demand. Concurrency management, 5-20ms cold-starts, and fully managed observability out of the box allow you to focus on iterating on your product.

  • Run your code on-demand from anywhere with no idle cost, billed per execution
  • Scale to 100s of concurrent executions with zero infrastructure overhead
  • Develop a highly-available backend with minimal cognitive load
HTTP
Public endpoint
Cron
Scheduled
handler
export default
async (req: Request) => {
const body = await req.json();
return Response.json({ ok: true });
}
0 instancestraffic spike
idlescale upservingscale down
04 · Reclaim engineering time spent keeping clusters alive

Migrate off Kubernetes

Problem

Your infrastructure, operations, and kubernetes setup are consuming significant engineering resources you could be spending on building features. Yet you still need a highly available, secure, and fully managed runtime to run your workloads on.

Solution

With Convoy, your workloads get the same production-grade features without the overhead.

  • Containerized workloads on Convoy Apps provide full portability and no vendor lock-in
  • Production-grade ingress, autoscaling, observability, RBAC, and other enterprise grade features come out of the box
  • No idle cost, capacity is allocated and billed on demand

Before

Ingress routing
TLS / cert-manager
HPA autoscaler
Longhorn storage
Cluster upgrades
Rollback logic
Alert rules
RBAC & policies
Node capacity

After

my-app
Live
HTTPS + custom domain
Auto-scales with traffic
Auto-rollback on failure
Full-stack observability
Team access & roles
05 · Give your agents a real cloud to operate inWaitlist

AI-Native Cloud Control Plane

Problem

Your agents can make API calls but the cloud was not built for them. APIs designed for humans mean agents have to deal with auth sessions, scrape web interfaces, interpret ambiguous errors, and hit rate limits that were sized for people clicking buttons.

Solution

Convoy ships a dedicated platform agent. ACP, the Agent Communication Protocol, is the interface your development agents connect to directly. It exposes the full Convoy primitive set in a structured, agent-native way: deploy services, spawn sandboxes, inspect health, tail logs, scale or terminate workloads.

  • ACP gives dev agents structured access to every Convoy primitive
  • Every cloud API is built agent-first, not retrofitted
  • The platform agent facilitates a declarative agent-native interface for agents to interact with the cloud
Agent
Autonomous · LLM-driven
ACPAgent Communication Protocol
convoy-agent · tool surface
Apps
Functions
Sandbox

Same control plane · same isolation · same billing