Product
AI-native deploy. Your cloud account first. Flat plan for the control plane, compute billed by your cloud provider.
Connect Claude Code, Cursor, or any MCP client with OAuth. Sign in through your browser, then use the tools allowed by your CloudPloy team role.
See MCP setupConnect a fresh server over SSH (Ubuntu 22.04+ or Debian 12+), or attach AWS with your own IAM. You own the cloud account. CloudPloy deploys onto it.
How pricing worksNixpacks builds Node, Python, Go, Rust, Ruby, Java, PHP, Deno, and static sites. WordPress and Laravel stay as one-click presets when you want them.
How it worksFree covers one small server forever. Starter, Pro, or Scale covers a bigger control plane. Servers we launch run in your AWS account and AWS bills you directly; BYO servers are paid to their provider.
See plansNew release comes up, traffic switches, old release drains.
Let's Encrypt certificates issued and renewed for you.
Per-app secrets, custom domains, and routing from the console or API.
read, deploy, provision, destroy. Hand an agent only what it needs.
estimate_cost and list_provider_credentials before spend. Plan limits cap server count and size.
Same capabilities over HTTP for scripts and agents.
No. Nixpacks covers Node, Python, Go, Rust, Ruby, Java, PHP, Deno, and static sites. WordPress and Laravel are first-class presets, not the whole product.
You pay the monthly plan for the control plane. Compute is billed by your provider: AWS for servers we launch in your account, or whoever hosts the server you bring.
Yes, if the token has the provision ability and your plan allows it. See /mcp.