Published on
How much does hosting an application cost when you pay in dollars or in reais?
A small application with PostgreSQL costs US$ 12 on Heroku and US$ 13 on Render, which becomes R$ 67.84 and R$ 73.49 on a Brazilian card at the 11/05/2026 PTAX rate (R$ 5.4621) plus 3.5% IOF, while the equivalent scenario on Zenifra costs R$ 41.80 in reais, with no exchange rate and no IOF. For larger projects the gap depends on each provider's equivalent plan, and this guide shows the math for three project sizes with the source, date, and exchange rate behind every number.
How we did the math
All three scenarios share the same shape: an always-on web application and a managed PostgreSQL database. For each provider we picked the plan closest in memory, because memory weighs the most on price and is what usually runs out first as an application grows. Dollar prices were read from the official pages on 11/06/2026, and Zenifra prices came from the public plan catalog, the same one behind the site calculator, on the same day.
To convert, we used the PTAX selling rate for 11/05/2026, published by the Central Bank of Brazil: R$ 5.4621 per dollar. On top of the converted amount comes the 3.5% IOF, the rate for international purchases with credit, debit, or prepaid cards (Decree 6,306/2007, article 15-B, item VII, as amended by Decree 12,499/2025). In practice the card issuer also adds its own spread to the rate, so the real bill tends to land a little above what you see here.
Amounts are monthly. Database disk, outbound traffic, and usage-based CPU stay out of the tables and are discussed further down, because each provider charges for them differently. The source for each number is linked below.
Scenario 1: MVP with a 512 MB application and PostgreSQL
This is the project that just left the drawing board: an API or a site with a backend, a few users, and a small database. Even so, the application has to stay on all the time, without sleeping, so the first visit of the day does not wait for the platform to wake the process up.
| Provider | Plans used | Price in dollars | Converted at PTAX | With 3.5% IOF |
|---|---|---|---|---|
| Heroku | Basic (0.5 GB) + Postgres Essential-0 | US$ 12.00 | R$ 65.55 | R$ 67.84 |
| Render | 0.5c-512mb + Postgres 0.1c-256mb | US$ 13.00 | R$ 71.01 | R$ 73.49 |
| Railway | 0.5 GB of RAM for the application and 0.5 GB for the database, billed by usage | From US$ 10.00, plus CPU | From R$ 54.62 | From R$ 56.53 |
| Vercel | Pro + 2 GB function in São Paulo + Neon with 0.25 CU | About US$ 46.06, plus active CPU | About R$ 251.58 | About R$ 260.39 |
| Zenifra | Basic (0.5 vCPU, 512 MB) + DB-Starter (0.3 vCPU, 256 MB) | Not applicable | R$ 41.80 in reais | R$ 41.80, no IOF |
Heroku Basic stays always on, but it allows only one dyno per process type, so it cannot scale horizontally. Postgres Essential-0 uses shared memory. On Render, the 256 MB database is the smallest paid plan. On Railway, the amount shown is memory only, at US$ 10 per GB per month; CPU (US$ 20 per vCPU per month) and volumes (US$ 0.15 per GB per month) are added by usage, and the US$ 5 Hobby subscription becomes usage credit.
Vercel has no always-on instance: a function bills provisioned memory while it serves requests and CPU only while the code runs. To reach a comparable number, we assumed a 2 GB function, the smallest option on the Pro plan, active 24 hours a day in São Paulo (region gru1, US$ 0.0183 per GB-hour), and a Neon PostgreSQL with 0.25 CU and scale-to-zero turned off, at US$ 0.106 per CU-hour. That adds up to US$ 20 for Pro, which becomes US$ 20 of credit, plus US$ 6.72 of memory above the credit and US$ 19.35 for the database. It is an estimate: with little traffic the billed memory goes down, and with heavy traffic active CPU goes up.
On Zenifra, the same scenario uses the Basic and DB-Starter plans, R$ 29.90 plus R$ 11.90. PostgreSQL disk is billed separately at R$ 0.20 per GB per month. The Static plan (0.1 vCPU, 128 MB), at R$ 5.90, is for static sites; an application with a backend starts at Basic.
Scenario 2: small API with 1 GB and a small PostgreSQL
Here the product already has paying customers. The application needs 1 GB of memory so it does not restart for lack of RAM during peaks, and the database moves past the smallest plan to have enough memory to keep the most frequent queries cached.
| Provider | Plans used | Price in dollars | Converted at PTAX | With 3.5% IOF |
|---|---|---|---|---|
| Heroku | Standard-2X (1 GB) + Postgres Essential-0 | US$ 55.00 | R$ 300.42 | R$ 310.93 |
| Render | 1c-2g (there is no 1 GB option) + Postgres 0.5c-1g | US$ 44.00 | R$ 240.33 | R$ 248.74 |
| Railway | 1 GB of RAM for the application and 1 GB for the database, billed by usage | From US$ 20.00, plus CPU | From R$ 109.24 | From R$ 113.07 |
| Vercel | Pro + 2 GB function in São Paulo + Neon with 0.25 CU | About US$ 46.06, plus active CPU | About R$ 251.58 | About R$ 260.39 |
| Zenifra | Premium (1 vCPU, 1 GB) + DB-Basic (1 vCPU, 1 GB) | Not applicable | R$ 112.80 in reais | R$ 112.80, no IOF |
At this size, Railway is practically tied with Zenifra before CPU is counted, and that is an honest result of the math: whoever bills exact usage tends to be cheap while consumption is low and predictable. The difference shows up in CPU, which costs US$ 20 per vCPU per month on Railway, and in the fact that a dollar bill changes every month with the exchange rate.
On Heroku, the price jump comes from the dyno: Basic tops out at 0.5 GB, and Standard-2X costs US$ 50 on its own. The database stays on Essential-0, with shared memory, which favors Heroku in this comparison. On Render, since there is no 1 GB instance, the next step is already the 2 GB one, at US$ 25. On Vercel, the smallest function already has 2 GB, so the estimate does not change from scenario 1.
On Zenifra, the scenario uses Premium and DB-Basic, R$ 62.90 plus R$ 49.90, with PostgreSQL disk at R$ 0.20 per GB per month.
Scenario 3: SaaS with two 1 GB instances and a 4 GB PostgreSQL
A SaaS in production runs at least two application instances, so a deployment or a failure in one of them does not take the service down, and it needs a database with enough memory to keep the most used data cached.
| Provider | Plans used | Price in dollars | Converted at PTAX | With 3.5% IOF |
|---|---|---|---|---|
| Heroku | 2 × Standard-2X + Postgres Standard-0 (4 GB) | US$ 150.00 | R$ 819.32 | R$ 847.99 |
| Render | 2 × 1c-2g + Postgres 1c-4g | US$ 105.00 | R$ 573.52 | R$ 593.59 |
| Railway | 2 GB of RAM for the application and 4 GB for the database, billed by usage | From US$ 60.00, plus CPU | From R$ 327.73 | From R$ 339.20 |
| Vercel | Pro + two 2 GB functions in São Paulo + Neon with 1 CU (about 4 GB) | About US$ 130.82, plus active CPU | About R$ 714.55 | About R$ 739.56 |
| Zenifra | 2 × Premium + DB-Premium (2 vCPU, 2 GB) | Not applicable | R$ 255.70 in reais | R$ 255.70, no IOF |
| Zenifra with an 8 GB database | 2 × Premium + DB-Enterprise (8 vCPU, 8 GB) | Not applicable | R$ 614.80 in reais | R$ 614.80, no IOF |
One caveat here: Zenifra has no 4 GB PostgreSQL plan. DB-Premium has 2 GB, and the next one, DB-Enterprise, has 8 GB. That is why the table shows both rows. If your database fits in 2 GB, the scenario costs R$ 255.70. If it needs more memory, DB-Enterprise brings the total to R$ 614.80, below Heroku and the Vercel estimate with IOF, but above Render and the Railway floor.
On Vercel, the math uses US$ 53.44 of memory (two 2 GB functions active all month, of which US$ 20 comes out of the Pro credit) and US$ 77.38 for a 1 CU Neon PostgreSQL with scale-to-zero turned off. In a real SaaS, active CPU comes on top and depends on traffic.
Zenifra paid PostgreSQL plans also accept one to six instances, billed per instance, which goes into the math if you need replicas.
What the tables do not show
Converting at PTAX keeps the comparison fair, but a card bill has other components. Before deciding on the table number alone, consider four points.
- Exchange rate on the billing day: the bill uses the rate of the day the purchase is processed, not the day you did the math. If the dollar rises 5% from one month to the next, the bill in reais rises 5% with no change to the application.
- Bank spread: besides IOF, the card issuer applies its own conversion rate, which is usually above PTAX. That amount varies by bank and is not in the tables.
- Database disk: Render charges US$ 0.30 per GB per month for Postgres, Neon US$ 0.35 per GB per month, Railway US$ 0.15 per GB per month for volumes, and Zenifra R$ 0.20 per GB per month for PostgreSQL. For a 10 GB database, that is US$ 3.00, US$ 3.50, US$ 1.50, and R$ 2.00, respectively.
- Variable usage: Railway and Vercel bill by consumption, so the real amount depends on traffic. To compare, run the application for a few weeks and check the provider usage dashboard instead of relying only on the pricing page estimate.
Where each provider runs its servers
Price is not everything. If the application and the database are far from users, every request pays the network round trip, and every database query pays again if the two sit in different regions. Heroku, Render, and Railway have no region in Brazil. Vercel can run functions in São Paulo, and that is the region used in the estimate.
| Provider | Regions | Closest to São Paulo |
|---|---|---|
| Heroku | United States and Europe (Common Runtime) | United States |
| Render | Oregon, Ohio, Virginia, Frankfurt, and Singapore | Virginia |
| Railway | US West, US East (Virginia), EU West, and Southeast Asia | US East (Virginia) |
| Vercel | Functions in several regions, including São Paulo (gru1) | São Paulo, for functions |
| Zenifra | São Paulo | São Paulo |
On Vercel, the Neon PostgreSQL runs in the region chosen for the database, which needs to be close to the function. Check the regions available on Neon before setting up the project.
What if the company pays in dollars by wire transfer, without a card?
The 3.5% rate used in the tables applies to international card purchases. When a company pays for a foreign service by bank wire, the exchange operation is a different one, and taxation depends on the type of operation and how the company is set up. Before doing the math with that path, confirm with your accountant which taxes and rates apply to your case.
On Zenifra the question does not come up: the charge is issued in reais by a Brazilian company, and payment is made by PIX, boleto, or card, with no exchange operation.
Which costs do not show up in the plan price?
The three that weigh the most are database disk, usage-based CPU, and outbound traffic. None of them is in the headline price of the plans compared above, and each provider charges for them differently, which makes comparing by plan price misleading as the project grows.
Database disk is the most predictable: you pay per GB stored, every month, even if the database is idle. The table shows each provider’s published price and the example of a 10 GB database, a common size for a product with a few thousand users.
Usage-based CPU shows up on providers that bill by consumption. On Railway, each vCPU used all month costs US$ 20, on top of memory. On Vercel, functions in São Paulo pay US$ 0.221 per hour of active CPU, plus provisioned memory. On plans with a fixed instance, such as Render, Fly.io, and Zenifra, CPU is already in the instance price, and it only changes when you change plans.
Outbound traffic is the hardest to predict, because it depends on response sizes and how many people visit. Before choosing, check each provider’s pricing page for how much traffic the plan includes and how much each GB above it costs, and estimate from the average size of your pages and API responses.
| Provider | Database disk | Database with 10 GB | CPU billed separately? |
|---|---|---|---|
| Render | US$ 0.30 per GB (Postgres) | US$ 3.00 | No, included in the instance |
| Railway | US$ 0.15 per GB per month (volume) | US$ 1.50 | Yes, US$ 20 per vCPU per month, by usage |
| Fly.io | US$ 0.28 per GB used (Managed Postgres) | US$ 2.80 | No, included in the machine |
| Neon (Postgres used with Vercel) | US$ 0.35 per GB per month | US$ 3.50 | On Vercel, active CPU at US$ 0.221 per hour in gru1 |
| Zenifra | R$ 0.20 per GB per month (PostgreSQL) | R$ 2.00 | No, included in the plan |
Foreign provider prices were read from the official pages on 11/06/2026. On Zenifra, the PostgreSQL disk price comes from the public storage catalog and is the same one the calculator uses. Dollar amounts still get exchange rate and IOF on the bill.
How much does the exchange rate change the bill from one month to the next?
Enough for the same bill to swing close to 10% in a few months, with no change in usage. The table takes the PTAX selling rate published by the Central Bank of Brazil on four recent dates and converts, with the 3.5% card IOF, the Render and Heroku scenarios in this guide.
Between 10/05/2026 and 11/05/2026, PTAX went from R$ 4.9859 to R$ 5.4621. The MVP on Render went from R$ 67.09 to R$ 73.49, R$ 6.40 more per month; the SaaS on Render, from R$ 541.84 to R$ 593.59, R$ 51.75 more. Nothing changed in the application: only the exchange rate.
| PTAX date | PTAX selling rate | Render MVP (US$ 13) | Heroku MVP (US$ 12) | Render SaaS (US$ 105) |
|---|---|---|---|---|
| 08/05/2026 | R$ 5.1154 | R$ 68.83 | R$ 63.53 | R$ 555.92 |
| 09/04/2026 | R$ 5.1253 | R$ 68.96 | R$ 63.66 | R$ 556.99 |
| 10/05/2026 | R$ 4.9859 | R$ 67.09 | R$ 61.92 | R$ 541.84 |
| 11/05/2026 | R$ 5.4621 | R$ 73.49 | R$ 67.84 | R$ 593.59 |
The real bill uses the rate on the day the bank processes the purchase, with the issuer’s spread on top, so actual amounts tend to land a bit above the table. For budgeting, use an exchange rate margin or ask your finance team which rate they plan with. On Zenifra, the amount in reais is the plan price, and it only changes when you change plans.
How do I estimate my application’s cost in reais?
Build your scenario in the Zenifra calculator, with the same plans you would use in production, and compare it with your current bill converted at the month’s exchange rate. The scenario links in this guide already open the calculator with the application, instances, and database filled in, and you adjust from there.
The steps take a few minutes:
- Open the calculator and, in the first project, choose the Plan by the memory your application uses today. An API with a backend starts at Basic (0.5 vCPU, 512 MB); Static is for static sites only.
- Set the number of instances. For production, two instances keep a deployment or a failure from taking the service down.
- Choose the usage type: Monthly for what stays on all the time, Hourly for staging and tests, Yearly for long commitments.
- Click + Add database, choose PostgreSQL and the plan by memory, and enter the persistent storage in GB. Remember that database disk is billed even when the project is stopped.
- If the application uses a cache, a queue, or the AI API, add each one. For AI, enter the input and output tokens per day.
- Read the result: the monthly total is the amount in reais, with no IOF. To keep it, use Export PDF.
On the current provider’s side, add up the plan, disk, usage-based CPU, and traffic from your last bill, convert at the month’s PTAX, and add the 3.5% IOF. Compare both totals for the same project size, not each provider’s cheapest plan.
Is hourly billing cheaper than monthly?
It is, for anything that is not on all month. On Zenifra, the Basic plan costs R$ 0.05 per hour or R$ 29.90 per month. Up to 598 hours in the month, hourly is cheaper; above that, monthly pays off. Since a month has about 730 hours, a production application that is always on stays on monthly.
A staging environment on for 8 hours a day, over 22 business days, adds up to 176 hours. On Basic, that is R$ 8.80 for the month, against R$ 29.90 monthly. DB-Starter costs R$ 0.018 per hour, so the staging database over the same 176 hours comes to R$ 3.17 (R$ 3.168 exact). Database disk keeps being billed while the project is stopped.
With hourly billing, Zenifra adds up the project’s hours in the cycle and rounds the total up to the full hour. With monthly billing, the project is reserved for the month at a fixed price, even if you pause it.
When paying in dollars still makes sense
If most of your users are in the United States or Europe, a region close to them is worth more than the exchange rate savings. Heroku, Render, and Railway have regions in both places.
If your company already earns in dollars, exchange rate swings stop being a risk, because revenue and cost move together. And if the project is mostly a Next.js frontend with little backend, Vercel is still a natural choice, because it maintains the framework.
Finally, exact usage billing can be cheaper for applications with low and irregular traffic, as Railway shows in scenario 2. Do the math with your real consumption before deciding.
In short
In dollars, the price on the plans page is only the start: add the exchange rate of the day, the 3.5% card IOF, and the bank spread. In scenarios 1 and 2, Heroku and Render came out between 1.6 and 2.8 times the Zenifra price in reais. In scenario 3, the answer depends on how much memory the database needs, because Zenifra has no 4 GB plan. Railway came close to Zenifra when CPU usage is low, and Vercel came out higher because of the minimum function memory.
To do the math with your own scenario, the Zenifra calculator shows the cost in reais per hour, month, or year, with current catalog prices.