> ## Documentation Index > Fetch the complete documentation index at: https://docs.vertracloud.app/llms.txt > Use this file to discover all available pages before exploring further. # Vertra Cloud Plans and Limits > Price, RAM, vCPU, projects, and API limit for every Vertra Cloud plan, from Free to Enterprise-32. 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. | Plan | Price/month | RAM | vCPU | Projects | API requests/day | | ------------------ | ----------: | ------------: | ---: | ------------------: | ---------------: | | Free ("suspended") | R\$0 | 100 MB "free" | 0.25 | 1 app, no databases | 1,000 | | Economy | R\$1.99 | 256 MB | 0.3 | Limited by RAM | 5,000 | | Pro | R\$5.99 | 1,024 MB | 0.5 | Limited by RAM | 20,000 | | Scale | R\$10.99 | 2,048 MB | 1 | Limited by RAM | 86,400 | | Intermediary | R\$18.99 | 3,072 MB | 1.5 | Limited by RAM | 115,200 | | Enterprise-4 | R\$23.99 | 4,096 MB | 2 | Limited by RAM | 144,000 | | Enterprise-6 | R\$35.99 | 6,144 MB | 3 | Limited by RAM | 180,000 | | Enterprise-8 | R\$47.99 | 8,192 MB | 4 | Limited by RAM | 216,000 | | Enterprise-12 | R\$71.99 | 12,288 MB | 5 | Limited by RAM | 324,000 | | Enterprise-14 | R\$83.99 | 14,336 MB | 5.5 | Limited by RAM | 378,000 | | Enterprise-16 | R\$95.99 | 16,384 MB | 6 | Limited by RAM | 432,000 | | Enterprise-18 | R\$107.99 | 18,432 MB | 6.5 | Limited by RAM | 486,000 | | Enterprise-20 | R\$119.99 | 20,480 MB | 7.5 | Limited by RAM | 540,000 | | Enterprise-22 | R\$131.99 | 22,528 MB | 8.5 | Limited by RAM | 594,000 | | Enterprise-24 | R\$143.99 | 24,576 MB | 9 | Limited by RAM | 648,000 | | Enterprise-26 | R\$155.99 | 26,624 MB | 9.5 | Limited by RAM | 702,000 | | Enterprise-28 | R\$167.99 | 28,672 MB | 10.5 | Limited by RAM | 756,000 | | Enterprise-30 | R\$179.99 | 30,720 MB | 11.5 | Limited by RAM | 810,000 | | Enterprise-32 | R\$191.99 | 32,768 MB | 12 | Limited by RAM | 864,000 | 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](/api-reference/limitations#bandwidth-limits), 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: | Plan | Requests/min | | ----------------------------------- | -----------: | | Free | 30 | | Economy | 60 | | Pro | 120 | | Scale | 180 | | Intermediary | 240 | | Enterprise-4 | 300 | | Enterprise-6 | 300 | | Enterprise-8 | 300 | | Enterprise-12 through Enterprise-32 | 480 | Details on both windows, response headers, and error codes are in [API Limits](/api-reference/limitations#api-request-limits). The site's pricing page has the full feature comparison and checkout. ## 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. | Plan | Plan vCPU | App with \< 2 GB RAM | App with ≥ 2 GB RAM | | ------------- | --------: | -------------------: | ------------------: | | Free | 0.25 | 0.25 | 0.25 | | Scale | 1 | 1 | 1 | | Intermediary | 1.5 | 1 | 1.5 | | Enterprise-4 | 2 | 1 | 2 | | Enterprise-32 | 12 | 1 | 12 | ## What does the Free plan include? The Free plan is currently **"suspended"**. It stays documented here for reference, with 100 MB of RAM "free", but it isn't available right now — start on Economy or above. 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. | Feature | Minimum plan | | -------------------------------------------- | ------------ | | Web publishing (`*.vertraweb.app` subdomain) | Pro | | File manager | Pro | | Advanced metrics | Pro | | Choose the subdomain name | Scale | | Daily and manual backups | Scale | | Custom domain | Intermediary | | Database data manager (Data tab) | Intermediary | | Auto-deploy via GitHub webhook | Intermediary | | Workspaces and commit system | Enterprise | 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](/mcp) 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. | Language | Recommended | Latest | Other versions | | ---------- | -------------------- | -------------- | ------------------------- | | JavaScript | Node.js 22.18.0 | Node.js 24.5.0 | 20.18.0 | | TypeScript | Node.js 22 + ts-node | Node.js 22 | 18, 20 | | Python | 3.13 | 3.13 | 3.12, 3.11 | | Go | 1.23 | 1.23 | 1.22, 1.21 | | Rust | 1.86 | 1.87 | 1.85 | | Java | Temurin JRE 21 | 21 | 17 | | Bun | 1.2.2 | 1.2.2 | 1.1.0 | | PHP | 8.3 | 8.3 | 8.2 | | Ruby | 3.3 | 3.4 | 3.2 | | Static | — | — | HTML, CSS, and JavaScript | ## Which databases are managed? There are four managed engines, all with mandatory TLS and certificates (CA, server, and client) generated automatically by the platform. | Database | Version | User | TLS | Authentication | | ---------- | ------- | --------------------------------- | -------- | ---------------------------------- | | PostgreSQL | 17 | `postgres` (database `postgres`) | Required | Password + client certificate | | MongoDB | 8.0.11 | `default` (auth database `admin`) | Required | Password + client certificate | | Redis | 7 | `default` | Required | Password + client certificate | | MySQL | 8.0 | `root` (database `default`) | Required | Password + X509 client certificate | The port is **unique per database** — not the engine's default — and is shown on the database page. See [how to connect](/databases#how-do-i-connect-to-each-engine). ## 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). | Limit | Value | | ----------------------------------------------------------- | ------------------------- | | Rows, documents, or keys per page | 200 | | Operation timeout (including SQL console) | 10 s | | Rows returned by the SQL console | 200 by default, 1,000 max | | Size of SQL sent to the console | 64 KB | | Size of the console result | 5 MB serialized | | Write body (row, document, key value) | 1 MB | | Items in a Redis collection (list, set, zset, hash, stream) | 1,000 | | Concurrent console queries per database | 1 | | Rate limit — SQL console | 30/min per user | | Rate limit — other data routes | 120/min per user | 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? | Limit | Value | | -------------------------------------------- | ------------------------------------------------------ | | Maximum deploy `.zip` size | 100 MB | | Maximum dependency installation time | 15 minutes | | Maximum build command time (`build_command`) | 10 minutes | | Storage for an application | 10 GB fixed, regardless of RAM | | Storage for a database | 6 GB + 1 GB per 512 MB of RAM, rounded to whole GB | | Exposed ports per application | 1 (port 80) | | Minimum RAM for an application | 100 MB (512 MB to publish to the web) | | Environment variables per application | 25 (key up to 100 characters, value up to 1,000) | | Custom domains per application | 1 | | Application, database, or workspace name | 50 characters | | Tree depth in the file manager | 6 levels | | Minimum interval between subdomain changes | 5 minutes | | Database reset (destructive) | 1 per hour | | Manual snapshot creation | 1 every 5 minutes per project, 10 per hour per account | | Plan downgrade | 1 every 3 hours | 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. | Plan | Deploys/hour | | --------------------- | -----------: | | Free | 5 | | Economy | 10 | | Pro | 20 | | Scale | 40 | | Intermediary | 60 | | Enterprise (any tier) | 60 | ## Next steps The step-by-step for your first deploy, from login to the app going live. Connect Claude, Cursor, or Codex to your account to investigate and operate it. How remaining days are converted when you switch plans. Resource and request limits of the public API.