Vertra Cloud Plans and Limits

Vertra Cloud is a Brazilian application hosting platform (PaaS): deploy from GitHub or a zip file, isolated containers, managed databases, file storage, snapshots, a CLI, and a VS Code extension. This page gathers, in one place, every public number of the platform — price, memory, vCPU, projects, and API limit per plan. The values below are the same ones used by the platform in production. Prices are in Brazilian reais, billed monthly.

​

How much does each Vertra Cloud plan cost?

Plans range from R$0 (Free, currently “suspended”) to R$191.99/month (Enterprise-32, 32 GB of RAM). Memory is the only thing apps and databases consume — there’s no per-hour or per-request charge. The project count cap only exists on Free (1 app, no databases). From Economy up, there’s no count cap — the real limit is the plan’s RAM: a creation is refused with INSUFFICIENT_MEMORY once the plan’s RAM runs out, so a 100 MB app fits 10 times on a Pro plan. All plans include Vertra Shield, the platform’s traffic protection. When an application is paused, the dashboard shows the reason and the remaining time. The bandwidth limits by memory, automatic TLS certificates, and 99.99% SLA also apply to all plans. The “API requests/day” column above only applies to calls authenticated with an API key (dashboard usage doesn’t count) and resets at midnight in the Brasília time zone. The same limit also has a per-minute window: Details on both windows, response headers, and error codes are in API Limits.

​

How much vCPU does an application actually get?

The vCPU column above is the per-application cap on the plan. An application with 2 GB of RAM or more gets the plan’s entire vCPU; below 2 GB, it gets 1/3 of the plan’s vCPU, with a floor of 1 vCPU — except on plans whose vCPU is already below 1 (Free, Economy, Pro), where the application gets the plan’s entire vCPU regardless. More RAM never results in less vCPU.

​

What does the Free plan include?

The Free plan exists to test and evaluate the platform before using it in production: 1 application (databases can’t be created on Free), 100 MB of RAM “free”, and 1,000 API requests per day. Free also doesn’t include the features a production application normally needs:

• No web publishing — the application doesn’t get a *.vertraweb.app subdomain (available from Pro up)
• No file manager and no advanced metrics (Pro up)
• No daily or manual backups (Scale up)
• Projects inactive for more than 30 days are automatically deleted, with email warnings on days 7, 23, and 27

​

Which features does each plan unlock?

Every feature has a minimum plan, and it applies to the resource’s owner — inviting someone on a higher plan into a workspace doesn’t unlock the feature. On Pro the subdomain is assigned at random by the platform; choosing the name requires Scale or higher. Publishing an application to the web requires at least 512 MB of RAM allocated to it.

​

How do I connect AI tools to Vertra Cloud?

Connect your compatible agent through the MCP server to operate your account’s resources.

​

Which languages and versions does Vertra Cloud support?

The platform builds and runs applications on ten runtimes. Each one has a recommended version, a latest version (often the same one) and older versions you can pin by number — in the wizard, in the Config tab, in VERSION or through the API.

​

Which databases are managed?

There are four managed engines, all with mandatory TLS and certificates (CA, server, and client) generated automatically by the platform. The port is unique per database — not the engine’s default — and is shown on the database page. See how to connect.

​

What are the limits of the Data tab?

The Data tab browses and edits database content through the dashboard or the API, without exposing the password or the connection string, and requires the Intermediary plan or higher. Below that plan, the API responds with PLAN_RESTRICTED_FEATURE (403). Reading applies to any workspace member; writing and the SQL console are owner or admin only. Administrative commands and arbitrary code execution are refused in the Redis and MongoDB console.

​

What are the deploy and resource limits?

Network bandwidth is proportional to allocated RAM: 50 Mbit at 100 MB, 100 Mbit at 256 MB, 200 Mbit at 512 MB, 400 Mbit at 1,024 MB, 800 Mbit at 2,048 MB, and 1,600 Mbit at 4,096 MB.

​

Deploys-per-hour limit

Counts as a deploy: creating an application, uploading a zip, deploying via GitHub (manual or by push), reinstalling dependencies, and changing the build command. Restarting and stopping don’t count. A GitHub push that arrives past the limit is ignored and logged in the activity history.

​

Next steps