← Back to blog

Published on

VPS or managed platform: which is cheaper for an application in Brazil?

On server price alone, a VPS is almost always cheaper: Hostinger charges R$ 29.99 a month for 4 GB of RAM in Brazil (on the 24-month plan) and Vultr US$ 20 for 4 GB in São Paulo, or R$ 113.07 on a card with the PTAX rate and 3.5% IOF. Once maintenance hours come in (updates, TLS, backups, monitoring and incidents), the result flips: at 4.25 hours a month and an hour worth R$ 50, the same VPS goes above R$ 242.49, while a 1 GB application with managed PostgreSQL on Zenifra comes to R$ 164.80, and this guide lists every assumption so you can redo the math with your own numbers.

How the comparison was made

All VPS prices come from each provider’s official pages, or from the official public API in Vultr’s case, read on 11/06/2026. For each provider, we picked the region closest to Brazil that the provider itself offers and recorded the monthly price. Dollar amounts were converted at the PTAX selling rate of 11/05/2026, R$ 5.4621, and euro amounts at the euro PTAX rate on the same day, R$ 6.1323, both published by Brazil’s Central Bank.

On top of the converted amount comes the 3.5% IOF tax, the rate for international purchases with credit, debit or prepaid cards (Decree 6,306/2007, art. 15-B, item VII, as amended by Decree 12,499/2025). The card issuer’s spread is not in the tables and usually pushes the real statement a little higher. Hostinger appears with the price in reais from its Brazilian page, with no conversion.

On the managed platform side, we used Zenifra’s plans from the public catalog on the same day, in reais. Zenifra bills in reais, by PIX, boleto or card, with no IOF. The goal is not to say one model is always better, but to show the point where each one starts to pay off, with math you can redo using the value of your own time.

Official VPS prices and the region closest to Brazil

The table shows an entry plan and a 4 GB plan, where available, which is enough to run a Node.js application with PostgreSQL on the same server. The region column shows where the plan was priced: four of the seven providers have a region in Brazil, and the other three are in the United States.

Provider and planResourcesRegion pricedOfficial priceConverted at PTAXWith 3.5% IOF
Hetzner CPX112 AMD vCPU, 2 GB, 40 GB NVMeAshburn, USA€ 17.99/month, excl. VATR$ 110.32R$ 114.18
Hetzner CPX213 AMD vCPU, 4 GB, 80 GB NVMeAshburn, USA€ 32.49/month, excl. VATR$ 199.24R$ 206.21
Contabo Cloud VPS 44 vCPU, 8 GB, 100 GB SSDUS East (New York)€ 4.40/month effective on a 24-month term (the page also shows € 5.50)R$ 26.98R$ 27.93
DigitalOcean Basic1 vCPU, 1 GiB, 25 GiB SSDNew York, Atlanta or RichmondUS$ 6/monthR$ 32.77R$ 33.92
DigitalOcean Basic2 vCPU, 4 GiB, 80 GiB SSDNew York, Atlanta or RichmondUS$ 24/monthR$ 131.09R$ 135.68
Vultr Cloud Compute1 vCPU, 1 GB, 25 GBSão PauloUS$ 5/monthR$ 27.31R$ 28.27
Vultr Cloud Compute2 vCPU, 4 GB, 80 GBSão PauloUS$ 20/monthR$ 109.24R$ 113.07
AWS Lightsail2 vCPU, 1 GB, 40 GB SSDSão Paulo (sa-east-1)US$ 7/monthR$ 38.23R$ 39.57
AWS Lightsail2 vCPU, 4 GB, 80 GB SSDSão Paulo (sa-east-1)US$ 24/monthR$ 131.09R$ 135.68
Hostinger KVM 11 vCPU, 4 GB, 50 GB NVMeBrazilR$ 29.99/month on the 24-month plan (R$ 719.76 upfront); full price R$ 87.99; renews at R$ 59.99/monthAlready in reaisAlready in reais
Oracle Cloud Always FreeAmpere A1: 2 OCPUs and 12 GB in total; 200 GB of block storageSão Paulo or Vinhedo, if it is the account’s home regionFreeR$ 0.00R$ 0.00

Hetzner has servers in Germany, Finland, Singapore and the United States (Ashburn and Hillsboro), and charges different prices per network zone: Ashburn prices are higher than the European ones. Contabo states that the displayed price is the effective monthly rate of a 24-month subscription including applicable taxes, and that Cloud VPS 4 has a setup fee on monthly contracts. DigitalOcean has no region in South America. Vultr lists São Paulo among its regions and the plan is available there.

On Lightsail, the page lists a single price per bundle, and São Paulo plans get half the data transfer allowance of the others. Hostinger runs a data center in Brazil; the R$ 29.99 price depends on paying 24 months upfront, and renewal is R$ 59.99 a month. On Oracle Always Free, instances must be created in the account’s home region, may be unavailable due to capacity ("out of host capacity" error), and instances idle for 7 days may be reclaimed by Oracle.

What the VPS price does not include

A VPS gives you a virtual machine with an operating system and root access. Everything that turns that machine into a production environment is up to you, and part of it has a price too. Before comparing the table figure with a managed platform, add the items below to your scenario.

  • Server backup: on Hetzner, automatic backups are extra, starting at € 1.1980 a month; on DigitalOcean, 20% of the Droplet price for weekly backups or 30% for daily; on Lightsail, snapshots cost US$ 0.05 per GB per month. Hostinger includes weekly backups. A machine backup does not replace a database backup: a consistent pg_dump, stored off the server, is a separate task.
  • Database: on a VPS, PostgreSQL runs on the same server and shares CPU and memory with the application. If you prefer a managed database from the same provider, the price goes up: on Lightsail, the 1 GB standard managed database costs US$ 15 a month, and a US$ 7 VPS with that database comes to US$ 22, or R$ 124.37 on a card.
  • Traffic: Hetzner includes 1 TB a month on US plans and bills the excess; DigitalOcean and Lightsail have per-plan allowances, and Lightsail in São Paulo gives half the allowance; Contabo advertises unlimited traffic under a fair use policy.
  • TLS certificate, reverse proxy, firewall, deploys, logs and alerts: all of this is software you install, configure and maintain. Next.js itself, for example, recommends putting a reverse proxy such as nginx in front of the server instead of exposing it directly to the internet.
  • Contract: the lowest Contabo and Hostinger prices depend on long terms, and Hostinger renews above the promotional price.

Added together, these items change the order of the table. A cheap VPS with no automatic backup, a small traffic allowance and a 24-month contract can cost more than a slightly pricier VPS that already includes backups and bills by the hour. Do the math with what you will actually buy, not with the lowest price on the page.

Total cost of ownership: the maintenance hours

The cost that does not show up on the VPS invoice is the time of whoever looks after it. To make that cost visible, we built a monthly estimate for a small web application with PostgreSQL on the same server, maintained by someone who already knows Linux administration. These are our assumptions, not measurements: if you automate more, use fewer hours; if the server is critical or the team is still learning, use more.

TaskHours per month (assumption)What it covers
Security updates for the OS, Node.js and PostgreSQL1.00Apply patches, restart services, check the application came back
TLS certificate0.25Check automatic renewal and the reverse proxy after updates
Backups1.00Maintain the dump script and the off-server copy, and test one restore a month
Monitoring and alerts0.50Review disk, memory, false alerts and growing logs
Incidents1.00Monthly average of outages, full disks, hung processes or brute-force attacks
Amortized initial setup0.506 hours of installation and hardening spread over 12 months
Total4.25

On a managed platform, maintenance does not drop to zero. You still update the code’s dependencies, review alerts, follow deploys and handle database migrations. For the comparison, we count 1 hour a month on that side.

It is also worth looking beyond the average. A VPS with no replica that loses its disk or gets compromised can take a whole day to come back, and that cost lands all at once, not spread as 1 hour a month. If your application earns money by the hour while it is up, include that risk in your estimate.

The full math with three hourly rates

The formula is simple: monthly cost = server price + maintenance hours × the value of your hour. That value is not a market price: it is what one hour of the person who would do this work is worth to you or to the company. We used R$ 0 (personal project, free time), R$ 50, R$ 100 and R$ 150. On the VPS side, the 4 GB Vultr in São Paulo and the Hostinger KVM 1 in Brazil, the two 4 GB options with a region in the country. On the managed side, Zenifra with Premium (1 vCPU, 1 GB) and DB-Basic (1 vCPU, 1 GB) with 10 GB of disk, and with Basic (0.5 vCPU, 512 MB) and DB-Starter with 2 GB.

ScenarioServer per monthHoursHour at R$ 0Hour at R$ 50Hour at R$ 100Hour at R$ 150
Vultr São Paulo, 2 vCPU and 4 GB, on a cardR$ 113.074.25R$ 113.07R$ 325.57R$ 538.07R$ 750.57
Hostinger KVM 1, 4 GB, 24-month planR$ 29.994.25R$ 29.99R$ 242.49R$ 454.99R$ 667.49
Hostinger KVM 1 at renewalR$ 59.994.25R$ 59.99R$ 272.49R$ 484.99R$ 697.49
Zenifra Premium + DB-Basic + 10 GBR$ 114.801.00R$ 114.80R$ 164.80R$ 214.80R$ 264.80
Zenifra Basic + DB-Starter + 2 GBR$ 42.201.00R$ 42.20R$ 92.20R$ 142.20R$ 192.20

With the hour at R$ 0, the VPS wins comfortably, and Hostinger delivers 4 GB of RAM for less than the smallest managed scenario. That is the honest answer for someone who has time and enjoys running servers. The break-even comes early: comparing Hostinger on the 24-month plan with the Premium + DB-Basic scenario, the managed platform becomes cheaper once your hour is worth more than R$ 26.10; at the renewal price, from R$ 16.86. Against Vultr, which costs almost the same as the managed scenario, the break-even sits below R$ 1 an hour.

The resources are not identical, and that needs to be clear. On the 4 GB VPS, the application and PostgreSQL share 4 GB; in the managed scenario, there is 1 GB for the application and 1 GB for the database, kept apart. If your application truly needs a lot of memory, the VPS gives you more RAM per real. Managed database disk is billed at R$ 0.20 per GB per month, and database backups are included in the plan.

What the managed platform includes on Zenifra

On Zenifra, the application is deployed from a GitHub (or Forgejo) repository or from an OCI image. The platform installs dependencies according to the runtime, runs the build and start commands and publishes the new version on every push to the branch, tag or release, depending on the update mode you choose. Each build is recorded under Build logs, with the output of every command, and the history keeps up to 30 builds or 30 days. To roll back, you deploy a stable commit again by its SHA, from the Console or the CLI.

HTTPS is included on every plan. For a custom domain, you create the DNS records the Console shows, and the certificate is issued automatically after validation, usually within a few minutes. Application logs are available on every plan, arrive live in the Console and can be kept in the organization’s Armazém with Log history. From Premium up, the project gets CPU, memory and HTTP traffic metrics and the health check, which calls the configured path every 60 seconds and can alert by e-mail.

The managed database (PostgreSQL 15 to 18, MariaDB or Valkey) requires TLS connections with certificate validation, and has automatic backups included in the plan, with no charge for the space. The table below comes from the backups documentation. Restores are requested from support, which restores into a new project by default; there is no restore from the Console yet and no point-in-time recovery, and support commits to replying within 2 business days.

Database plansBackups per dayTimes (Brasília)Kept for
db-starter103:007 days
db-basic203:00 and 15:007 days
db-premium203:00 and 15:0014 days
db-enterprise303:00, 11:00 and 19:0030 days

What stays with you: the code and its dependencies, migrations, your own pg_dump exports of critical data (the documentation recommends this extra layer) and log retention, if you need history. There is also no root or superuser access to the managed database; the user has enough elevated access to operate the database normally.

Latency: why the region matters more than the price

Every request from a user in Brazil has to reach the server and come back, and every database query makes the same trip between the application and PostgreSQL. The farther the server, the longer each round trip, and that time multiplies by the number of requests on a page and the number of queries in a route. We do not publish millisecond figures because they depend on the user’s carrier and on each provider’s network path, which change over time.

What the price table does let us say is where each option is located. Vultr, Lightsail, Hostinger and Oracle have a region in Brazil, as does Zenifra. Hetzner, Contabo and DigitalOcean only offer regions outside South America, and the closest ones are on the US East Coast. For a Brazilian audience, a server in the United States works, but every round trip crosses the continent.

The reliable way to decide is to measure. Create an hourly instance with the provider you are evaluating (Hetzner, DigitalOcean and Vultr bill by the hour or by the second), deploy a simple route and measure from where your users are with curl -o /dev/null -s -w "%{time_connect} %{time_starttransfer}\n" https://your-server/health, at different times of day. Then delete the instance. If the database will live somewhere else, also measure the query from the application by logging its duration.

ProviderRegion in BrazilRegion used for pricing
HetznerNoAshburn, Virginia (USA)
ContaboNoUS East, New York (USA)
DigitalOceanNoNew York, Atlanta or Richmond (USA)
VultrYesSão Paulo
AWS LightsailYesSão Paulo (sa-east-1)
HostingerYesBrazil
Oracle CloudYesSão Paulo or Vinhedo
ZenifraYesBrazil

When a VPS is the better choice

A VPS wins when your administration time is cheap or already paid for. If you already run servers with Ansible or scripts, if the team has an infrastructure person, or if the project is personal and learning Linux is part of the goal, the hours in the table drop a lot, and the server price becomes the deciding factor. In that scenario, Hostinger, Contabo and Oracle Always Free are hard to beat on RAM per real.

It also wins when you need something a platform does not offer: root access, a service listening on ports and protocols outside HTTP, software installed at the system level, a process that keeps state on local disk, or many small services sharing a single machine. Memory-hungry workloads that tolerate living on a single machine, such as a read database for internal analytics or a test environment, are also cheaper on a large VPS.

Finally, a VPS is predictable on a long contract. Whoever pays 24 months of Hostinger or Contabo knows the cost for the next two years, as long as they plan for the renewal price. The managed platform wins when the application is business-critical, when nobody on the team wants to be woken up by a full disk, and when the hour of whoever would do the maintenance is worth more than the price difference.

Decision checklist

Answer the questions below before you sign up. Each "yes" in the first half pulls toward a VPS; each "yes" in the second half pulls toward a managed platform.

  • Does someone on the team already administer Linux and have time set aside for it every month?
  • Does the application need root access, protocols outside HTTP or software installed on the system?
  • Is the project personal or for learning, so the time spent on the server costs you nothing?
  • Do you need a lot of RAM per real and accept the application and the database on the same machine?
  • Does the application earn money while it is up, so an outage of a few hours has a real cost?
  • Do you want database backups with a defined retention without writing and testing scripts?
  • Does the team prefer to deploy with a push to GitHub, with build logs and rollback by commit?
  • Are your users in Brazil, and do you want the server and the database in the country, paying in reais with no IOF?
  • In any case: is the region in Brazil or close to your users, and have you measured latency from there?

If the answers came out split, a common approach is to separate the pieces: keep on the VPS whatever needs root or a lot of memory, and run the web application and the production database on a managed platform. Before deciding, put your scenario in the Zenifra calculator and compare it with the VPS invoice plus the hours you estimated.

What is the cheapest VPS with a server in Brazil?

Among the paid providers surveyed, Hostinger KVM 1 costs R$ 29.99 a month with 1 vCPU and 4 GB of RAM, on the 24-month plan paid upfront (R$ 719.76), and renews at R$ 59.99 a month. In dollars, Vultr’s smallest option in São Paulo costs US$ 5 a month with 1 GB, or R$ 28.27 on a card with IOF.

Oracle Always Free charges nothing for Ampere A1 instances (2 OCPUs and 12 GB in total), and the São Paulo and Vinhedo regions exist. The condition is creating the instances in the account’s home region, and Oracle may reclaim instances idle for 7 days.

Do I have to pay IOF when buying a VPS abroad?

If you pay for an international purchase with a credit, debit or prepaid card, yes: the rate is 3.5%, under Decree 6,306/2007, art. 15-B, item VII, as amended by Decree 12,499/2025. That is why the tables show both the converted price and the price with IOF.

Besides IOF, the statement uses the exchange rate on the processing date and the issuing bank’s spread. When a company pays by bank remittance, taxation depends on the type of operation; check with your accountant. On Zenifra, billing is in reais, by PIX, boleto or card, with no foreign exchange operation.

What is the lowest cost to start without a VPS?

On Zenifra, the smallest application setup with PostgreSQL is the Basic plan (0.5 vCPU, 512 MB) with DB-Starter, for R$ 41.80 a month plus database disk. For testing, hourly billing comes to R$ 0.068 an hour for both. Sign-up asks for a Brazilian CPF or CNPJ, a mobile number and an address in Brazil.

That setup suits MVPs and small projects, with no health check or metrics, which start at Premium. Static, at R$ 5.90, is for static sites only.

Can I move from a VPS to a managed platform later?

Yes, and the most common path has two parts: first the application, then the database. The application goes from the GitHub repository to an HTTP project with the same build and start commands, and PostgreSQL moves with pg_dump on the VPS and pg_restore into the managed database.

Keep the VPS running until you validate the application on the new URL and switch DNS. Zenifra’s migration guide has the cutover-day checklist, with TTL reduction and a final data copy, and shows how the application should connect to the database with validated TLS.

Is a VPS with PostgreSQL on the same server safe for production?

It can be, as long as you treat the server as production: security updates applied, PostgreSQL with no port open to the internet, a firewall, SSH access by key only, database backups stored off the server and a tested restore.

The weak point is the single machine. If the disk fails or the server is compromised, the application and the database go down together, and recovery depends on the last backup you kept somewhere else. With a managed database, automatic backups are stored outside the instance, and paid PostgreSQL plans accept 1 to 6 instances, with automatic failover when there is more than one.

Compare your VPS cost with an app and database in the calculator

We respect your privacy

We use essential cookies to run this site. Measurement and marketing cookies, such as Google Ads, are only enabled when you accept all cookies. Read our cookie policy.