← Back to blog

Published on

Where should a small business host its management system with support in Portuguese?

Host it with a provider that has servers in Brazil, bills in reais and offers support in Portuguese, and choose between a VPS you manage yourself (Locaweb, KingHost, UOL Host, Hostinger) or a platform that already includes a managed database with backups, such as Zenifra, where a Basic application with a db-starter PostgreSQL and 10 GB of disk costs R$ 43.80 per month. AWS, Azure and Google Cloud also have a São Paulo region, but Portuguese-language support is either a paid add-on or missing from the standard technical support. This guide covers what an ERP, a finance system or an inventory tool needs to run safely, compares providers based on what each official site said on Nov 6, 2026, works out the monthly cost in reais, and ends with a security and LGPD checklist written for business owners who do not work in tech.

What a management system needs to run well

A management system holds the most sensitive information a company has: issued invoices, accounts payable and receivable, customer records with CPF and address, inventory, payroll and sales history. So before looking at prices, it helps to understand the five pieces every ERP, finance system or inventory tool needs working at the same time. The first is a relational database, such as PostgreSQL or MariaDB, which makes sure an entry is never left half-written when two people edit the same order. The second is the application itself, the program employees open in the browser.

The third piece is backup. Replicas and mirrored disks protect you from a machine failure, but not from someone deleting a customer by mistake or from a spreadsheet import that overwrites the inventory. Only a copy taken before the mistake fixes those cases, and it needs a known schedule and a defined retention period. The fourth piece is secure access: HTTPS on the system address, strong passwords and two-factor authentication for administrators and, ideally, a way to make the login screen visible only from the office network.

The fifth piece is the domain, such as system.yourcompany.com.br, which gives the team an address that is easy to remember and lets you change providers without telling everyone a new one. On top of all this sits the LGPD, Brazil’s Law No. 13,709/2018, which applies to any company that processes data about individuals, including customers and employees. The law does not say which provider to use, but it requires security measures and defines responsibilities, which the LGPD section below covers.

In practice, the question “where to host” turns into two questions. Who will take care of each of these pieces day to day, you or the provider? And how much does it cost per month, in reais, with no exchange rate surprises? The next sections answer both with numbers taken from official pages.

  • A relational database (PostgreSQL or MariaDB) with an encrypted connection.
  • Automatic backups with a known schedule, a retention period and a clear way to restore.
  • Secure access: HTTPS, strong passwords, two-factor authentication and, if possible, IP restriction.
  • A custom domain pointing to the system.
  • LGPD care for customer and employee data.

A ready-made cloud ERP or your own hosted system

There are two paths, and neither is best for everyone. On the first, the company subscribes to a ready-made ERP sold as a service (SaaS): it pays a monthly fee per user or per module, uses it in the browser and never thinks about servers, databases or backups, because the vendor handles all of that. For a company that only needs to issue invoices and track cash and inventory the way the system already does, this is usually the simplest path, and buying hosting makes no sense.

On the second path, the company runs a system it owns: software custom-built by a developer, an older system that currently sits on an office computer, or an open source ERP such as Odoo or ERPNext. Here hosting is your decision, and this guide was written for that case. What you gain is control: the data lives in a database you can export whenever you want, the system can be adapted to how the company works and the cost does not grow with every new user. The price is that someone has to install, update and monitor it.

Odoo and ERPNext are the two most cited open ERPs, and their licenses deserve attention. According to Odoo’s official documentation, Odoo 18 Community Edition is licensed under the LGPL version 3, while the Enterprise Edition uses the Odoo Enterprise Edition License v1.0, a proprietary license. ERPNext’s official GitHub repository publishes the project under the GPL version 3. In short, the open edition of Odoo and ERPNext can be installed on your own server, while Odoo Enterprise depends on the vendor’s commercial terms.

Each one requires a different database. Odoo’s installation documentation says it uses PostgreSQL. ERPNext’s official README describes an installation that includes MariaDB and creates a password for the MariaDB root user. That detail matters on managed databases: on Zenifra, the plans documentation states that the database user has no root or superuser access, only elevated access to operate the database. Before choosing, test the installer of the system you plan to use against a managed database and check that it works without those privileges.

PathWho handles the server and backupsWhen it makes senseSource (Nov 6, 2026)
Ready-made ERP (SaaS)The ERP vendorYour process fits what the system already doesThe chosen vendor’s contract
Odoo CommunityYou or the platform it runs on; PostgreSQL databaseYou want an open, adaptable ERP with no license costLGPLv3 license, official Odoo documentation
Odoo EnterpriseDepends on the vendor offer you buyYou need the Enterprise Edition modulesOdoo Enterprise Edition License v1.0
ERPNextYou or the platform; default install with MariaDBYou want an open ERP on the Frappe stackGPLv3 license, official repository
Your own systemYou or the platform; database of your choiceCustom-built or legacy company softwareYour contract with whoever built it

Who has servers in Brazil, bills in reais and supports Portuguese

The table below gathers what each provider states on its own pages on Nov 6, 2026. VPS prices are the ones advertised on the product page, and several of them apply only to long contracts with a higher renewal price. At Locaweb, the VPS 1 GB Linux costs R$ 15.90 per month on a 24-month contract and renews at R$ 23.92. At Hostinger, KVM 1 costs R$ 29.99 per month on a 24-month contract (R$ 87.99 without the discount) and renews at R$ 59.99. Always compare the renewal price, because that is what stays on the bill from the third year on.

Traditional Brazilian providers sell servers (VPS or cloud server): you get a machine with root access and install the operating system, database, web server and certificate yourself. The big clouds, AWS, Azure and Google Cloud, have a São Paulo region, but Portuguese-language technical support is another story. AWS states that its support works in Chinese, English, Japanese and Korean, and that Technical Account Managers can speak Portuguese starting with the Enterprise Support plan, which costs at least US$ 5,000 per month. Azure supports nine languages, Portuguese included, on the Developer (US$ 29 per month), Standard (US$ 100) and ProDirect (US$ 1,000) plans. Google Cloud lists English, Japanese, Mandarin, Korean and French for Customer Care, with no Portuguese.

On Brazilian invoices (nota fiscal), we only record what the official source states. Locaweb’s help center explains that the invoice is available under Customer Center, Payments, History. KingHost’s help center says invoices are issued under the LWSA name and can be downloaded from the dashboard. Hostinger states in its own help center that it does not issue Brazilian invoices and that its invoice works as proof of purchase. For the others, check with sales before signing up if your accounting depends on it.

ProviderProduct and advertised priceRegion in BrazilCurrencyPIX and boletoSupport in Portuguese
LocawebVPS 1 GB Linux, R$ 15.90/month on 24 monthsYes, infrastructure in BrazilReais, taxes includedBoleto with PIX QR code, card and Itaú direct debitYes, 24/7, according to the page
KingHostVPS 4GB, R$ 32.90/monthYes, national infrastructureReaisBoleto, card and PIXYes, 24/7, according to the page
UOL HostCloud Server 1 GB, R$ 65.90/monthNot stated on the product pageReais, fixed priceNot stated on the product page24/7 support and WhatsApp service
HostingerVPS KVM 1, R$ 29.99/month on 24 monthsYes, South America: BrazilReaisPIX and boleto among payment methods24h support, site in Portuguese
AWSsa-east-1 region (São Paulo); priced per serviceYesPer contractPer contractPortuguese only via a Technical Account Manager on Enterprise Support (min. US$ 5,000/month)
AzureBrazil South region (São Paulo state); support sold separatelyYesPer contractAzure.com accepts cards unless invoicing is arrangedYes, on paid plans from US$ 29 to US$ 1,000/month
Google Cloudsouthamerica-east1 region (Osasco, SP)YesPer contractPer contractNo: Customer Care without Portuguese
ZenifraBasic R$ 29.90/month + PostgreSQL db-starter R$ 11.90/monthYes, infrastructure in BrazilReais, no IOFPIX, boleto and cardYes, by email and WhatsApp

The column that makes the biggest difference is not in the table: what comes ready. On a VPS, the price is for the machine, and the database, backups, security updates and certificate are on you. On Zenifra, PostgreSQL or MariaDB is managed, with automatic backups included, and the application is deployed from GitHub or a Docker image. The next section breaks down that split of work.

VPS or managed platform: who does what

A VPS price looks unbeatable until you list what comes inside it: a virtual machine with an operating system and root access. Everything else has to be installed and maintained by someone on your team or a hired technician. That includes PostgreSQL or MariaDB, the web server, the HTTPS certificate and its renewal, operating system security updates, the backup routine and the place where the copies are stored, since a copy on the same server disappears along with it.

Locaweb, for example, includes a free snapshot for restoration with its VPS and offers ready-made images with PostgreSQL and MariaDB, according to the product page. That helps you get started, but configuring, updating and backing up the database remain your responsibility. For a company with a trusted technician, this model works well and is the cheapest per gigabyte of memory.

On a managed platform, the split is different. On Zenifra, you deploy the application from a GitHub repository or a Docker image, and the database is created in the Console with automatic backups, TLS and its own address. There is no operating system to update and no certificate to renew. In return, you have no root access to the machine, which can rule out systems that need to install components on the server or require a database superuser.

If the company has nobody to look after a server, the number that matters is not just the monthly fee. It is the fee plus a technician’s hours each month, plus the risk of finding out on the day of the problem that the backup had not run for weeks.

TaskVPS or cloud serverZenifra
Install and update the operating systemYouNot applicable: the application runs in a managed container
Install and configure the databaseYouCreated in the Console, PostgreSQL 15 to 18 or MariaDB 10 and 11
Database backupsYou build the routine and store the copiesAutomatic, included in the plan, 3 to 30 days
HTTPS certificateYou install and renew itIssued automatically after DNS validation
Restrict access by IPYou configure the firewallAllowlist and blocklist in the Console, from Premium Plus up
Root access to the machineYesNo

How much a small ERP costs on Zenifra

The figures below come from Zenifra’s public catalog, checked on Nov 6, 2026 at /v1/project/plans, /v1/project/database/plans and /v1/project/storage/plans, on monthly billing. The HTTP plan sets the application’s CPU and memory; the database plan sets the CPU and memory of each database instance; database disk is billed separately, per GB on each instance. PostgreSQL disk costs R$ 0.20 per GB per month. MariaDB always runs with 3 instances (one primary and two replicas), so the plan is billed 3 times, and the public calculator prices its disk at the catalog’s persistent storage rate, R$ 0.44 per GB per month, on each instance.

Scenario 1 fits a lightweight custom system used by a few people at a time. Scenario 2 fits an open ERP or a system that needs more memory and IP-based access control, a feature that starts at Premium Plus. Scenario 3 shows the same size as scenario 2 with MariaDB. The 10 or 20 GB of disk is just an example; a small ERP usually takes far less at first, and the disk can be increased later on hourly billing.

ScenarioApplicationDatabaseDatabase diskMonthly total
1. Lightweight custom systemBasic (0.5 vCPU, 512 MB): R$ 29.90PostgreSQL db-starter (0.3 vCPU, 256 MB): R$ 11.9010 GB × R$ 0.20 = R$ 2.00R$ 43.80
2. Open ERP with IP restrictionPremium Plus (2 vCPU, 2 GB): R$ 119.90PostgreSQL db-basic (1 vCPU, 1 GB): R$ 49.9020 GB × R$ 0.20 = R$ 4.00R$ 173.80
3. Same size with MariaDBPremium Plus: R$ 119.90MariaDB db-starter, 3 instances × R$ 11.90 = R$ 35.7010 GB × R$ 0.44 × 3 = R$ 13.20R$ 168.80

All prices are in reais, paid by PIX, boleto or card, with no IOF. Hourly billing is also available: Basic costs R$ 0.05 per hour, which adds up to R$ 36.00 over 720 hours, so for a system that stays on all month the R$ 29.90 monthly contract is cheaper. Hourly billing pays off for tests and for environments that are turned off at night.

If the system stores attachments, such as order PDFs, XML files of issued invoices or product photos, they can go to Armazém, Zenifra’s object storage, at R$ 0.18 per GB per month with the first 5 GB free. Armazém is available to every organization. Before you sign up, build your own scenario in the calculator: it shows the monthly total using the same catalog billing uses.

Backups: what is included and what stays with you

On Zenifra, PostgreSQL, MariaDB, Analytics, Key‑Value and Queues have automatic backups included in the plan at no extra cost, and the space the copies use is included too. Cache has no backup, because it keeps data only in memory. Frequency and retention depend on the database plan, and the times are fixed. The table below reproduces the backups documentation, with times converted to Brasília time (UTC−3).

Rotation works like this: when a new backup finishes, the oldest one beyond the plan’s count is removed. If backups stop for any reason, older ones are not deleted early. A stopped database keeps getting copied on schedule. Backups are stored on Zenifra infrastructure in Brazil, with access restricted to the Zenifra team. If a project is deleted by mistake, its copies are kept for the plan’s retention period, and you can still recover the database by contacting support within that window.

Restores are not yet available from the Console or to an exact point in time: you ask support, by WhatsApp or by email at support@zenifra.com, giving the project ID, the database type, the date and time of the backup, and whether the restore should go to a new project (the default) or the current one. Restoring into the current project only happens with written confirmation from the organization owner. Support’s response commitment is up to 2 business days, which is why the documentation itself recommends keeping your own exports.

In practice, for an ERP: use at least db-basic if the company cannot lose half a day of entries, because it takes two copies a day. Keep a weekly pg_dump or mariadb-dump stored outside the provider and test restoring it now and then, so you find out before the problem whether the file is good.

Database planBackups 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

Security checklist before putting company data online

Most incidents in small systems do not come from sophisticated attacks, but from reused passwords, accounts shared between employees and admin screens open to the whole internet. The items below use only features that Zenifra’s documentation and plans page confirm. They work as a script for talking to whoever will set up the system, even if you do not do the setup yourself.

Two points deserve attention. The first is two-factor authentication: on Zenifra it uses an authenticator app (TOTP), such as Google Authenticator, Authy, Microsoft Authenticator or 1Password, and there are no backup codes; if the phone is lost, access is recovered through support@zenifra.com. Turn it on for more than one administrator so the company does not depend on a single device.

The second is IP-based access control, listed as IP blocking on the plans page. From Premium Plus up, a public project can have an allowlist (only the listed IPs get in) and a blocklist (IPs blocked even if they are on the allowlist), with up to 10 entries each, in IPv4 CIDR format. Changing the lists does not restart the system, and the Console stays reachable if you lock yourself out by mistake. Note that the HTTPS certificate for a custom domain is not issued while access is restricted by IP, so adjust the Network Access section for the certificate to be issued.

  • Turn on two-factor authentication under Account > My account > Security for every administrator.
  • Use passwords of 12 to 64 characters, with uppercase, lowercase, a number and a special character, as the Console requires.
  • Do not share logins: create an organization, invite each person and give them only the permissions they need.
  • Check the login history for the last 7 days under Account and keep login and password-change notifications on.
  • Keep the database password and other keys in project environment variables, such as DATABASE_URL, never in code.
  • Connect to the database with the Console URI, which already turns TLS on (sslmode=require); do not switch it to sslmode=disable.
  • On Premium Plus or higher, restrict the system to the office and VPN IPs with the allowlist.
  • Run workers and internal routines as private projects, which receive no internet traffic.
  • Restrict organization API Keys by IP when an automation runs from a fixed address.
  • Do not write passwords, tokens or personal documents to application logs.
  • If you suspect unauthorized access, change the password: that ends every session and connected integration on the account.

LGPD: what Brazil’s data protection law asks of companies that store customer data

Brazil’s General Data Protection Law (LGPD), Law No. 13,709/2018, applies to the processing of personal data, meaning any information about an identified or identifiable individual. Processing includes collecting, using, storing and deleting. In practice, the customer records, employee records and purchase history in your ERP are covered. The law calls the party that makes decisions about processing the controller, and the party that processes data on the controller’s behalf the processor. For the data your company collects, your company is the one deciding.

Three articles weigh on how you choose and set up hosting. Article 46 requires processing agents to adopt technical and administrative security measures that protect data from unauthorized access and from destruction, loss or alteration. Article 48 requires the controller to notify the national authority and the data subject of a security incident that may cause relevant risk or harm. Article 37 asks controllers and processors to keep records of their processing operations.

The law does not forbid storing data outside Brazil, but Article 33 only allows international transfers in the cases it lists, such as countries with adequate protection or specific contractual clauses. A provider with servers in the country avoids that analysis for the stored data. Article 18 gives data subjects rights such as confirmation that processing exists, access, correction and deletion of unnecessary data, so the system has to let you find and fix a person’s record. Article 41 requires appointing a data protection officer, and the same article lets the national authority set exemptions based on company size.

Zenifra’s security documentation makes the split clear: the deployed application remains responsible for defining the legal basis, minimization, retention and deletion of the data it collects. The platform provides controls such as organization permissions, 2FA, TLS and backups in Brazil; what goes into each record and how long it is kept is your company’s decision. This text is not legal advice: for your case, talk to the lawyer or accountant who works with the company.

Step by step: from the system to your company address on Zenifra

The steps below follow Zenifra’s documentation. If a developer or technician will do the work, send them this list along with the link to each document. Sign-up asks for a CPF or CNPJ, a mobile number and an address in Brazil, and hourly billing lets you test before committing to a monthly contract.

Start with the database. In the Console sidebar, click Create project, choose PostgreSQL (or MariaDB), select the plan and billing mode, give it a name of 6 to 32 characters and create it. The connection string follows the format postgresql://app:<password>@postgresql-<project-id>.managed.zenifra.com:<port>/app?sslmode=require, and the full password only shows at creation or after a rotation, so store it right away. For automatic failover, use more than one PostgreSQL instance.

Then deploy the application as an HTTP project, from a GitHub repository or a Docker image. Under Environment Variables, create DATABASE_URL with the database URI. Always use the host shown in the Console, because the certificate is issued for that name and connections by IP fail validation. To point your domain, open the project, click Edit, go to Custom Domains, click Add, enter the domain and create the records the table shows at your DNS provider: CNAME and TXT for subdomains such as system.yourcompany.com.br, or an A record for the root domain.

  • Create an account and organization in the Console (CPF or CNPJ, mobile number and address in Brazil).
  • Create the database under Create project > PostgreSQL or MariaDB, choosing the plan and billing mode.
  • Copy the connection URI and store the password, which only shows at creation.
  • Deploy the application as an HTTP project from GitHub or a Docker image.
  • Create the DATABASE_URL environment variable with the Console URI.
  • Under Edit > Custom Domains, add the domain and create the DNS records shown.
  • Wait for the HTTPS certificate line to show active; on projects with IP restriction, adjust Network Access for the certificate to be issued.
  • On Premium Plus, set up the IP allowlist under Edit project > Network Access.

What is the cheapest cloud to host a small business management system?

Looking only at the machine price, the cheapest option is a Brazilian VPS on a long contract: on Nov 6, 2026, Locaweb advertised a VPS 1 GB at R$ 15.90 per month over 24 months and Hostinger its KVM 1 at R$ 29.99 per month over 24 months. That price does not include a managed database, off-server backups or security updates, which stay with you.

With a managed database and backups included, Zenifra starts at R$ 43.80 per month (Basic + PostgreSQL db-starter + 10 GB of disk), in reais and with no lock-in on hourly billing. If the company does not need anything custom, a ready-made SaaS ERP can cost less than any hosting, because the server is already part of the subscription.

Does the system’s data stay in Brazil?

On Zenifra, yes: the database plans state infrastructure in Brazil, and backups are stored on Zenifra infrastructure in Brazil, with access restricted to the Zenifra team, according to the backups documentation. Locaweb, KingHost and Hostinger also advertise infrastructure or a data center in Brazil for their VPS plans.

On the big clouds, data stays in the region you choose: sa-east-1 on AWS, Brazil South on Azure and southamerica-east1 on Google Cloud are in São Paulo. Also check where backup copies live and which auxiliary services the system uses, such as email delivery and file storage.

Can I pay for hosting with PIX or boleto?

Yes, with providers that bill in reais. On Zenifra, payment is by PIX, boleto or card, in reais with no IOF, and the balance added to the organization pays for applications, databases and AI. KingHost accepts boleto, card and PIX; Locaweb accepts boleto (which can be paid with the PIX QR code), card and Itaú direct debit; Hostinger shows PIX and boleto among its payment methods.

On the big clouds, payment methods depend on the contract. Azure’s support page, for example, says Azure.com only accepts credit or debit cards unless invoicing has been arranged. A card charge in a foreign currency carries 3.5% IOF on the purchase.

Can I try it before committing?

On Zenifra, yes, with hourly billing: the application on Basic costs R$ 0.05 per hour and PostgreSQL on db-starter R$ 0.018 per hour, plus disk. Credit can be added by PIX, from R$ 5, without registering a card. Sign-up asks for a CPF or CNPJ, a mobile number and an address in Brazil.

Use the test to check that the system runs and, before loading the company’s real data, choose the database plan with backups in mind: for an ERP, db-basic takes two copies a day.

When is another option a better fit than Zenifra?

When the system needs root access to the machine, a database superuser or components installed on the server, a VPS is a better fit, because Zenifra provides none of the three. That applies to installers that require the MariaDB root user and to legacy systems that only run on Windows Server, which Locaweb offers on VPS, for example.

It is also worth looking elsewhere when the company needs self-service restores or point-in-time recovery, which Zenifra does not offer yet, or when the process fits a ready-made SaaS ERP. And if your accounting requires an invoice from the provider, confirm that with any company’s sales team before signing up.

Estimate my system’s cost 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.