CloudPloy

Security

Least privilege for humans and agents.

Scoped tokens, container isolation, SSL by default, and cost checks before spend. We don't invent enterprise checklists we don't ship.

Scoped API tokens

Tokens are limited to read, deploy, provision, or destroy. Hand an agent only the ability it needs. Rotate or revoke from team settings.

SSH and secrets stay on your side of BYO

When you bring your own server, you own the box and the cloud account. We connect for deploys and management; we do not mark up or resell that compute.

Container isolation

Apps run in isolated containers on the server. One bad release does not own the whole machine by default.

Automatic SSL

Let's Encrypt certificates are issued and renewed for custom domains you attach.

Spend checks before provision

provision_server checks plan limits. estimate_cost and list_provider_credentials exist so an agent can confirm cost and a cloud connection before it spends.

Your AWS bill, your account

Servers we launch run in your AWS account and AWS bills you directly. CloudPloy never stops or destroys a server over a balance.

Where do I report a vulnerability?

Email legal@cloudploy.com or hello@cloudploy.com with "security" in the subject. Do not open a public issue with exploit details.

Is MCP safe for autonomous agents?

Safer than a god-mode SSH key. Scope the token tightly. Prefer read + deploy for day-to-day; reserve provision and destroy for humans or tightly supervised agents.