← Back to blog

Published on

What is the most affordable hosting in reais for freelancers with an application and a database?

On Zenifra, an application with a backend and PostgreSQL costs R$ 41.80 per month (Basic with DB-Starter, plus R$ 0.20 per GB of disk), in reais, by PIX, boleto, or card, with servers in Brazil; for demos and staging, hourly billing comes to R$ 0.068 per hour for both. Vercel, Netlify, and Render also have free plans, but Vercel Hobby is for personal, non-commercial use, Render Hobby is described as being for personal projects and prototypes, and Netlify Free pauses projects when the 300 monthly credits run out; this guide compares the four with data from the official pages on 11/06/2026 and shows how much to charge the client for hosting.

What a freelancer pays on Zenifra

For a freelancer, the starting point is putting a complete project online, with a backend and a database, paying in reais and only for what you use. The plans below are the smallest of each type in the public catalog on 11/19/2026.

ResourceSmallest plan and price
HTTP projectBasic: 0.5 vCPU, 512 MB of RAM, 5 GB of ephemeral storage, a subdomain with HTTPS, CDN, and real-time logs; R$ 29.90 per month or R$ 0.05 per hour
Static siteStatic: 0.1 vCPU and 128 MB of RAM; R$ 5.90 per month or R$ 0.01 per hour
PostgreSQLDB-Starter: 0.3 vCPU, 256 MB of RAM, disk set at creation, and a daily backup kept for 7 days; R$ 11.90 per month or R$ 0.018 per hour, plus R$ 0.20 per GB of disk
Valkey Cachecache-starter: 0.5 vCPU and 512 MiB of RAM, with data in memory only; R$ 34.90 per month or R$ 0.06 per hour
Valkey Queuequeue-starter: 0.5 vCPU, 512 MiB of RAM, 5 GB of persistent storage, and a backup every 24 hours; R$ 44.90 per month or R$ 0.08 per hour
Armazém5 GB free to store files; above that, R$ 0.18 per GB per month

Signing up asks for a CPF or CNPJ, a Brazilian mobile number, an address in Brazil, and email confirmation. Credit is added by PIX, from R$ 5, or boleto, from R$ 30, with no international card. The platform does not shut down the project for lack of traffic, so the first visit of the day does not wait for the application to wake up.

Deployments can come from a GitHub repository or a Docker image, and PostgreSQL is connected to the application through an environment variable with the connection URI. The walkthrough is in the site quickstart.

What freelancers use hourly billing for

The most common use is showing work. A demo for the client to approve before the contract, or a proof of concept that needs a database, stays online with a public address only for the hours it is running: 10 hours of Basic with DB-Starter cost R$ 0.68, plus disk. A static portfolio stays online all month on Static, for R$ 5.90.

Another use is staging. Before publishing the final version in the client environment, you deploy the application with hourly billing, share the URL, and stop the project once the feedback arrives. Since the project does not sleep while it is running, the client does not hit a waiting screen when opening the link.

Finally, hourly billing is a good way to learn the full stack: application, PostgreSQL, cache, and queue in the same console, with real-time logs, without setting up a server or configuring certificates, paying only for the hours you study.

How it compares with Vercel, Netlify, and Render

Vercel, Netlify, and Render are the first options many freelancers think of for free hosting. The table summarizes what the official pricing pages say about each free plan, read on 11/06/2026, and how Zenifra bills the same use.

PlatformFree planWhat the plan includesCommercial useWhen the limit is reached
VercelHobby4 hours of active CPU, 360 GB-hours of memory, 1 million invocations, and 100 GB of transfer per monthNo: Hobby is for personal, non-commercial useStays at the plan caps, with no option to buy extra usage
NetlifyFree300 credits per month, spent on production deploys (15 each), bandwidth (20 per GB), compute (10 per GB-hour), and requests (2 per 10 thousand)The pricing page does not sayThe project is paused until the next cycle, and every project on the account is paused
RenderHobbyFree web service with 512 MB of RAM, free Postgres with 256 MB of RAM and 100 connections, free Key Value with 25 MB, and 5 GB of bandwidthHobby is described as being for personal projects and prototypesThe pricing page says the free plan has limitations, without listing them
ZenifraNone; hourly billingBasic at R$ 0.05 per hour and DB-Starter at R$ 0.018 per hour, plus disk; 5 GB free on ArmazémThe Terms of Use do not restrict it to personal useNo quota: the hours used are billed in reais

The point that matters most to a freelancer is commercial use. A site delivered to a client is commercial use, so on Vercel it needs the Pro plan, at US$ 20 per month with US$ 20 of usage credit, paid in dollars on a card.

On Netlify, the Free plan runs on credits: each production deploy costs 15 of the 300 monthly credits, so 20 deploys already use up the quota before bandwidth and compute are counted. When the quota runs out, every project on the account is paused until the next cycle, unless you change plans. The Personal plan costs US$ 9 per month, with 1,000 credits.

On Render, the Hobby workspace costs US$ 0 per month plus the compute used, and the free web service and Postgres instances carry a note that limitations apply. For teams deploying production apps, Render points to the Pro workspace, at US$ 25 per month plus compute.

Vercel, Netlify, and Render are still good choices for frontends and prototypes. The difference on Zenifra is having an always-on application and managed PostgreSQL with servers in Brazil, billed in reais, with no exchange rate or IOF.

When to switch from hourly billing to the monthly plan

Hourly billing is the cheapest while the project stays on for only part of the time. On Basic, an hour costs R$ 0.05, so up to 598 hours in the month it is cheaper than the R$ 29.90 monthly plan; since a month has about 730 hours, an always-on application belongs on the monthly plan.

In practice, it is time to review the plan when one of these signs shows up:

  • the project will stay on all month, in production with real customers;
  • you want to follow CPU and memory, which start at Premium;
  • the application needs more memory or autoscaling during traffic peaks;
  • the database needs more space or backups kept for longer.
PlanResourcesMonthly price
StaticFor static sites: 0.1 vCPU, 128 MB of RAM, and autoscaling availableR$ 5.90
Basic0.5 vCPU, 512 MB of RAM, 5 GB of ephemeral storage, and autoscaling availableR$ 29.90
DB-StarterPostgreSQL with 0.3 vCPU and 256 MB of RAM, disk set at creation, and a daily backup kept for 7 daysR$ 11.90 plus R$ 0.20 per GB of disk

Static is the smallest plan, made for static sites. For an application with a backend and a database, the base plan is Basic, with 512 MB: Basic with DB-Starter costs R$ 41.80 per month, plus disk.

Plans can be billed by the hour, month, or year. For a staging environment that stays online for only a few days, hourly billing is usually cheaper. Payment is in reais, by PIX, boleto, or card, with no IOF.

How to bill clients in reais without IOF on your side

When the client hosting runs on a platform billed in dollars on your card, the exchange rate and the 3.5% IOF on international purchases land on you. You charge the client in reais, but you pay an amount that changes every month with the rate and also carries the tax, which eats into the margin of a fixed-price contract.

With hosting billed in reais, each client cost is predictable. On Zenifra, you can keep each client projects in their own organization and switch between them with the same login, and each organization billing stays inside it. That makes it clear how much each client costs per month, and the amount goes into your quote with no exchange rate surprise.

Another option is for the client to have their own organization and pay for hosting directly, by PIX, boleto, or card, with you invited by email to run the deployments. Before closing the contract, agree with the client on who pays for hosting and check with your accountant how to record that pass-through.

How much should you charge the client for hosting?

Charge the real cost of the project’s infrastructure, with a margin for your time looking after it, and keep it separate from the development fee. Mixing the two makes the client think hosting is free, and the problem shows up when the project grows and the cost goes up.

To get the real cost, build the scenario in the calculator with the plans the project will use in production. For an application with a backend and PostgreSQL, the starting point is Basic with DB-Starter. The table shows a typical budget for a small system, with values from the public catalog.

The domain is not in this math: it is registered and paid at the registrar chosen by the client or by you. The HTTPS certificate for the platform subdomain is already included.

ItemPlan or usagePer month
ApplicationBasic (0.5 vCPU, 512 MB), monthlyR$ 29.90
DatabasePostgreSQL DB-Starter (0.3 vCPU, 256 MB)R$ 11.90
Database disk5 GB at R$ 0.20 per GBR$ 1.00
FilesArmazém: 5 GB free; above that, R$ 0.18 per GB per monthR$ 0.00 up to 5 GB
Infrastructure totalR$ 42.80

From there, add your margin and the maintenance time you agree on with the client: updates, keeping an eye on logs, restoring a backup when needed. Write into the contract that the hosting fee follows the plan and that a plan change, due to growth, adjusts the monthly fee.

How to build the hosting budget step by step

A clear budget avoids the hard conversation six months later. It shows the client what is being paid, why, and what makes the amount change.

  • List the project components: application, database, cache, queue, files, scheduled jobs, and the AI API, if any.
  • Choose each component’s plan by memory and expected usage at launch, not by the worst case you can imagine.
  • Build the scenario in the calculator and export the PDF to attach to the proposal.
  • Separate the infrastructure amount from your maintenance work, on different lines.
  • Decide who pays the platform: you, passing the cost through, or the client, directly in their own organization.
  • Agree on the trigger for a plan change, for example memory near the limit for several days or the need for a second instance.

Do I need a separate staging environment?

For client projects, yes: it is where the client approves changes before they reach production, and where you test a database migration without risking real data. What you do not need is to pay production prices for an environment that sits idle most of the time.

The cheapest way is hourly billing for staging. On the Basic plan, an hour costs R$ 0.05; an environment on for 8 hours a day, over 22 business days, adds up to 176 hours and comes to R$ 8.80 for the month. The staging database on DB-Starter, over the same hours, comes to R$ 3.17 (R$ 3.168 exact), and its disk keeps being billed while the project is stopped. With hourly billing, the cycle’s total hours are rounded up to the full hour.

Another option is to stop the staging project between approval rounds: a stopped project is not charged for compute, only for storage.

If the project is on GitHub, Preview environments create a temporary URL for each pull request, with the plan and time to live you set. It is the most direct way to show the client a specific change before merging it into the main code, and the environment is removed when the pull request closes.

Whatever the path, never point staging at the production database. Use a copy with test or anonymized data, and keep each environment’s variables separate in the corresponding project.

When should you move up from Basic to a bigger plan?

When the application starts needing more memory or features that only exist on the higher plans. Premium (1 vCPU, 1 GB) costs R$ 62.90 per month and adds the custom HTTP subdomain. Premium Plus (2 vCPU, 2 GB) costs R$ 119.90 per month and adds IP blocking, useful for internal systems that should only be reached from the client’s network.

The most common signs are restarts from running out of memory at peaks, response time growing with the number of users, and the need for a second instance to stay up during deployments. Before moving up, check that the bottleneck is not a slow database query, which an index fixes at no cost.

On the database side, DB-Basic (1 vCPU, 1 GB) costs R$ 49.90 per month and keeps two backups a day for 7 days, against one backup a day on DB-Starter. For a client that depends on the system to invoice, that difference is usually worth the price.

Paid application plans also accept more than one instance and auto-scaling. Instead of jumping straight to a bigger plan, it is sometimes better to keep Basic with two instances: the cost doubles, from R$ 29.90 to R$ 59.80 per month, but the application stays up during deployments and if one instance fails. For that to work, keep sessions in the database or the cache, not in process memory.

Database, files, and backups: what to agree on with the client

What causes the most trouble after delivery is not the code, it is the data. Agree with the client, before going to production, where the database and files live, how often backups run, and who requests a restore when something goes wrong.

On Zenifra, managed databases have automatic backups included in the plan at no extra cost, and the frequency depends on the plan. DB-Starter has one backup a day, kept for 7 days. DB-Basic has two a day, kept for 7 days. Restores are requested from support and, by default, go to a new project, so the current database is not changed until you decide to switch the connection.

Platform backups protect against accidental deletion and corrupted data, but the documentation itself recommends keeping your own exports of critical data with pg_dump and testing the restore from time to time. For a client that invoices through the system, include that routine in the maintenance contract.

Files uploaded by users, such as photos, PDFs, and attachments, should not live on the application disk, which can be discarded on every deployment. Use Armazém, which is S3-compatible: 5 GB are free and, above that, pricing is per GB stored. Every file starts private and can be shared through a link that lasts 7 days, or made public only when you choose that file, such as catalog images.

Finally, put in writing who has access to what. The client should access the organization with their own login, and your access should be what you need to maintain the project. Never share one account’s password between two people.

Delivery checklist for the client

Delivering a project also means delivering its operation. Before closing the work, go through this list with the client, ideally in writing:

  • The domain points to the project, HTTPS is active, and the platform subdomain is no longer the published address.
  • Environment variables are set in the project, and no password was left in the code or the repository.
  • The database is on the right plan, with disk sized and automatic backups checked.
  • The client knows where to see the logs and whom to call when something stops.
  • Who pays the platform is defined, and the payment method (PIX, boleto, or card) is set up in the right organization.
  • The client’s access to the organization was created with their own login, and your access was adjusted to what the contract says.
  • The repository is in an account the client can access, with automatic deployment set up on the agreed branch.

Can I start a client project without a card?

Yes. Signing up asks for a CPF or CNPJ, a Brazilian mobile number, an address in Brazil, and email confirmation, and the organization credit is added by PIX or boleto, in reais. With hourly billing, you put the application and PostgreSQL online for the demo and for staging, paying only for the hours used, R$ 0.068 per hour with Basic and DB-Starter, plus disk.

When the project goes to production, the monthly plan is usually cheaper, and payment stays by PIX or boleto. A card is optional and works as an automatic backup for postpaid charges when the credit is not enough.

The credit belongs to the organization and covers everything it uses: applications, databases, files, and the AI API. PIX goes from R$ 5.00 to R$ 5,000.00 per top-up, and boleto from R$ 30.00 to R$ 49,999.99. The AI API is prepaid and stops when the credit runs out, which avoids an unexpected bill at the end of the month.

Can the client pay for hosting directly?

They can, and it is often the best arrangement. The client creates their own organization, pays the credit by PIX or boleto in reais, and invites you by email to operate the projects. Each person signs in with their own login and only the access they need.

That way, the infrastructure account is in the name of whoever uses the system, and you do not need to pass amounts through. If the contract ends, the client removes your access, and the project stays online with no migration.

If you serve several clients, keep each one in a separate organization. With the same login, you switch between organizations in the Console, and each client’s projects, databases, AI keys, and billing stay isolated inside their organization.

In short

For demos and staging, Zenifra hourly billing puts an application and PostgreSQL online with no sleeping, paying only for the hours used, in reais and with no international card. When the project becomes production for a client, an application with PostgreSQL starts at R$ 41.80 per month (Basic with DB-Starter), plus disk.

If the work is only a personal frontend or a prototype, the Vercel, Netlify, and Render free plans also do the job, as long as you follow each one's usage rules and limits.

Create an account in the Console

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.