Product
AI-native deploy. Your cloud account first. Flat plan for the control plane, prepaid credits for compute we provision.
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 any Ubuntu box over SSH, 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. Credits pay for servers we provision. BYO servers never touch your credit balance.
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 get_account before spend. Auto-refill optional. 7-day grace if balance hits zero.
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 on servers you bring yourself is never billed through CloudPloy credits.
Yes, if the token has the provision ability and your plan and credit balance allow it. See /mcp.