Published on
How do you host WordPress in Brazil on a managed platform and pay in Brazilian reais?
Deploy the official WordPress image as an HTTP project, connect a managed MariaDB over TLS, and keep /var/www/html on persistent storage. On Zenifra, the official template setup (Premium plan, 10 GB of disk, and a MariaDB 11 db-starter with 3 instances and 10 GB) costs R$ 116.20 per month on the monthly contract, or R$ 0.164 per hour of runtime plus disk, in reais and with no IOF tax; this guide covers the template and manual steps, the full cost breakdown, and a fair comparison with WordPress.com, shared hosting, and a VPS, using sources read on November 6, 2026.
The short answer: managed WordPress, in reais, with the full breakdown
To host WordPress in Brazil on a managed platform and pay in Brazilian reais, deploy the official WordPress image as an HTTP project, connect a managed MariaDB database over TLS, and keep the /var/www/html directory on persistent storage. On Zenifra, the official template setup (Premium plan, 10 GB of disk, and a MariaDB 11 db-starter with 3 instances and 10 GB) costs R$ 116.20 per month on the monthly contract, paid by PIX, boleto, or card, with no currency exchange and no IOF tax.
This guide is for people who already run a site, blog, or store on WordPress and want to leave shared hosting or a VPS they have to manage on their own. It starts with what WordPress itself requires, according to the official documentation, and shows how each item becomes a setting on Zenifra: the image, the plan, the persistent disk, the database, the environment variables, the TLS connection, and the custom domain. The steps follow the official WordPress template configuration in the Console and the templates, MariaDB, and connection pages of the Zenifra documentation, with no invented shortcuts.
The comparison is honest about price too. For a simple blog, WordPress.com costs less than Zenifra’s template setup: the public WordPress.com plans API, queried from Brazil, lists the Personal plan at R$ 144 per year. The reason to choose Zenifra is not being the cheapest WordPress on the market; it is control over the image and the PHP version, a MariaDB database with three instances and automatic backups, hourly billing for tests, and the same account for the company’s other applications, databases, and AI.
Zenifra prices come from the public plan, database, and storage catalogs, checked on November 6, 2026 and published in Brazilian cents. Dollar prices were converted at the PTAX selling rate of November 5, 2026 (R$ 5.4621), plus the 3.5% IOF tax on international card purchases (Decree 6,306/2007, art. 15-B, item VII, as amended by Decree 12,499/2025).
What WordPress needs to run
The official WordPress requirements page is short: the server should provide PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, and HTTPS support. Apache or Nginx are the recommended web servers, but any server with PHP and MySQL will do. The same page notes that WordPress still works with PHP 7.4 and MySQL 5.5.5 in legacy environments, but those versions have reached end of life and may expose the site to security vulnerabilities. On November 6, 2026, the official WordPress version API reported 7.1.4 as the current release.
When WordPress runs in a container, three concerns appear that shared hosting usually hides. The first is files: the official image documentation explains that the initial install comes from the image and, after that, WordPress manages itself inside /var/www/html, where wp-config.php and the wp-content folder with uploads, plugins, and themes live. If that directory is not persistent, everything is gone when the instance restarts. The second is the site URL: WordPress stores the address under Settings > General, in the WordPress Address (URL) and Site Address (URL) fields, always with https:// and without a trailing slash.
The third concern is the database. The official image reads the connection from the WORDPRESS_DB_HOST, WORDPRESS_DB_USER, WORDPRESS_DB_PASSWORD, and WORDPRESS_DB_NAME variables, and the database named in WORDPRESS_DB_NAME must already exist, because the container does not create it. If the database requires TLS, as Zenifra’s managed MariaDB does, WordPress needs the secure connection flags, which get their own section below. The image documentation also warns that it cannot send emails by itself: password recovery and forms depend on an SMTP plugin configured with your email provider.
| Requirement | What the official source says | How it works on Zenifra |
|---|---|---|
| PHP | 8.3 or greater (wordpress.org/about/requirements) | Set by the official image tag; the template uses docker.io/wordpress:7.1.4-php8.5-apache, with WordPress 7.1.4 and PHP 8.5 |
| Database | MariaDB 10.11+ or MySQL 8.0+ | Managed MariaDB, versions 10 and 11 (default 11), 3 fixed instances, automatic failover, and mandatory TLS |
| HTTPS | HTTPS support | HTTPS included in HTTP plans and a certificate issued automatically for the custom domain |
| Web server | Apache or Nginx recommended | The apache variant of the official image, listening on port 80 |
| Files | wp-config.php and wp-content live in /var/www/html after the first install | 10 GB of persistent storage at /var/www/html, replicated in three copies |
| Site URL | WordPress and site addresses with https:// and no trailing slash | A *.clients.zenifra.com address, or a custom domain configured before finishing the install |
| The official image does not send email | An SMTP plugin with your email provider |
How WordPress is set up on Zenifra
There are two projects. The first is an HTTP project created from the official docker.io/wordpress:7.1.4-php8.5-apache image, which ships WordPress 7.1.4 with PHP 8.5 and Apache and serves on port 80. The second is a managed MariaDB database, with the app user and the app database created by the platform. The application finds the database through the WORDPRESS_DB_* environment variables, and the connection always uses TLS with certificate validation.
Persistent storage is required. The template uses 10 GB at /var/www/html, and the Zenifra documentation warns that media uploads, plugins, and themes live in that directory and that, without it, everything is lost on restart. Persistent storage data is replicated in three copies, which protects against a server failure but not against a file deleted or corrupted by the site itself. The directory cannot be changed after creation, and capacity can increase (with hourly billing only) but can never decrease.
The template’s default plan is Premium, with 1 vCPU and 1 GB of RAM, 1 instance, and hourly billing. Premium is the first plan with CPU, memory, and request metrics, a healthcheck, and a custom subdomain, which helps you see whether the site needs more. The plan guide says to move up to Premium Plus (2 vCPU and 2 GB) when a CMS with many plugins needs more than 1 GB per instance; it is also the first plan with IP allow and deny lists, useful for keeping a test copy reachable only from the company network. Keep 1 instance: multiple instances require extra shared-media configuration in WordPress.
On the database side, the template recommends MariaDB 11 on the db-starter plan, with 10 GB of storage. Managed MariaDB has 3 fixed instances (1 primary that receives reads and writes and 2 replicas that can take over if it fails), InnoDB as the default engine, versions 10 and 11, and storage from 1 GB to 250 GB. On db-starter, the automatic backup runs once a day at 06:00 UTC (03:00 in Brasília), and each copy is kept for 7 days at no extra cost; restores are requested from support.
- Application: HTTP project, docker.io/wordpress:7.1.4-php8.5-apache image, port 80, 1 instance, Premium plan with hourly billing.
- Files: 10 GB of persistent storage at /var/www/html.
- Database: managed MariaDB 11 on db-starter, with 3 instances and 10 GB, matching the official requirement (10.11 or greater).
- Connection: WORDPRESS_DB_HOST, WORDPRESS_DB_USER, WORDPRESS_DB_PASSWORD, WORDPRESS_DB_NAME, and WORDPRESS_CONFIG_EXTRA with the TLS flags.
- Address: *.clients.zenifra.com at first, and a custom domain with an automatic certificate for production.
The quick path: the WordPress template in the Console
WordPress is in the public Templates catalog as an official Zenifra template, marked “Requires a database”; in the catalog checked on November 6, 2026, it showed as updated that same day. The template page offers two paths. Deploy creates the project with all of the author’s recommendations after a confirmation that shows an automatic name and a summary of plan, billing, access, instances, and persistence. Customize opens project creation with the recommendations filled in so you can review them before creating.
The current template revision sets the docker.io/wordpress:7.1.4-php8.5-apache image, port 80, 10 GB of persistent storage at /var/www/html, the Premium plan with hourly billing, and 1 instance, and it recommends a MariaDB 11 on db-starter with 3 instances and 10 GB. For WordPress, the most complete path is Customize, because that is where the Create a database with the project option appears. The option starts unselected and, when selected, creates the MariaDB and the application in a single operation, with the database created first; if any step fails, Zenifra reverts everything created in that operation. Variables the author linked to the connection data are filled in automatically, stay read-only, and sensitive values remain masked. Deploy creates only the application, so you would need an existing MariaDB.
- 1. Open Templates from the Console menu.
- 2. In Public templates, use Official or Most used and open the WordPress card to review the author, revision, application, port, persistence, variables, and defaults.
- 3. Click Customize.
- 4. Review the name, description, plan, billing mode, number of instances, and data capacity.
- 5. Select Create a database with the project and check the suggested database: MariaDB 11, db-starter, 3 instances, and 10 GB.
- 6. Check the WORDPRESS_DB_HOST, WORDPRESS_DB_NAME, WORDPRESS_DB_USER, WORDPRESS_DB_PASSWORD, and WORDPRESS_CONFIG_EXTRA variables and fill in any that are not linked to the database.
- 7. Review the summary of both resources and their costs, then click Create project.
The template keeps the application, port, HTTP type, persistent folder, and set of expected variables fixed; plan, billing, access, instances, and capacity can be changed. To create both resources, your account needs the project.create and database.create permissions in the organization. After creation, the application and the database are independent: deleting one does not delete the other, and changing the database password requires updating the application variable by hand.
The project records the template and the revision used, but future changes to the template do not alter your site. That is good for stability, and it means WordPress updates still happen from the WordPress dashboard itself.
Manual step by step: managed MariaDB and the HTTP project
The manual path gives the same result with control over every field. Before you start, have a verified account, permission to create projects in the organization (project.create), and credit or a saved card for the chosen plans. Create the database first, because the application needs its host, port, and password.
For MariaDB: in the Console, click Create project and select MariaDB Database. Choose the plan, starting at db-starter, and the billing model: hourly, monthly, or yearly. Give the project a name of 6 to 32 characters using lowercase letters, numbers, and hyphens, choose the version (MariaDB 10 or 11), and set storage between 1 GB and 250 GB, keeping in mind that it can grow but never shrink and that changes are only available with hourly billing. Click Create Project and store the password, which is shown only once, together with the host in the mariadb-<project-id>.managed.zenifra.com format, the port, the app user, and the app database.
For the application: in the Console, click + Create Project, choose HTTP, and fill in the fields in the table, the same as in the official template. The name follows the same 6-to-32-character rule and also defines the *.clients.zenifra.com address. In the Environment variables step, add the five variables in the block below with the MariaDB data, and use the host shown in the Console, never the IP address. To match the template, create the MariaDB 11 on db-starter with 10 GB of storage.
WORDPRESS_DB_HOST=<mariadb-host>:<port>
WORDPRESS_DB_USER=app
WORDPRESS_DB_PASSWORD=<mariadb-password>
WORDPRESS_DB_NAME=app
WORDPRESS_CONFIG_EXTRA=define('MYSQL_CLIENT_FLAGS', MYSQLI_CLIENT_SSL | MYSQLI_CLIENT_SSL_VERIFY_SERVER_CERT);| Field | Official template value |
|---|---|
| Project source | OCI Image |
| Image | docker.io/wordpress:7.1.4-php8.5-apache |
| Registry | Public, no authentication |
| Plan | Premium (1 vCPU and 1 GB RAM); Premium Plus or larger for sites with many plugins or more traffic |
| Billing | Hourly (switch to monthly or yearly if the site will stay online all the time) |
| Port | 80 |
| Instances | 1 (multiple instances require extra shared-media configuration) |
| Persistent storage | Yes, 10 GB, directory /var/www/html |
Review the estimated cost and click Create Project. When it finishes, the Console opens the project page with the public address. Open the URL and complete the WordPress installation (language, site title, and admin user). To validate the disk, upload an image to the media library, pause and resume the project, and confirm the image is still there. If the application does not respond, check the project logs, the configured port, and the troubleshooting guide.
The 7.1.4-php8.5-apache tag pins the version of the first install and the PHP version, which meets the official requirement of PHP 8.3 or greater. After the first install, WordPress core updates itself inside /var/www/html from its own dashboard, so the tag mainly defines PHP and Apache from then on. Before switching to a newer PHP tag in the future, test the site and its plugins on a copy.
For tests, hourly billing is the cheapest; for continuous use, compare it with monthly in the cost section. Deleting the project, under Projects > Delete, is permanent and erases its storage.
Database TLS, site URL, and custom domain
Zenifra’s managed MariaDB accepts only TLS connections, which is why the WORDPRESS_CONFIG_EXTRA variable is not optional. The official image documentation explains that this variable’s value is evaluated inside wp-config.php; Zenifra’s template uses that to define the MYSQL_CLIENT_FLAGS constant. In the WordPress code reference, the wpdb::db_connect function reads that constant and passes the flags to the mysqli connection. With MYSQLI_CLIENT_SSL | MYSQLI_CLIENT_SSL_VERIFY_SERVER_CERT, WordPress connects over TLS and validates the certificate and the server name.
Zenifra’s connection page lists the errors you get when that is missing. Without TLS, the database rejects the connection with Access denied even with the right password. With MYSQLI_CLIENT_SSL alone, the connection is encrypted but accepts any certificate. Using the IP instead of the Console host, validation fails with messages such as Cannot connect to MySQL using SSL or does not match host name, because the certificate is issued for the mariadb-<project-id>.managed.zenifra.com name. In all of these cases WordPress shows its database connection error page; the project logs help find the cause.
The URL is the second most common reason installs break. The Zenifra documentation recommends configuring the custom domain before finishing the installation, so the site URLs are born with the final address. If you need to change it later, the WordPress documentation offers two ways: change the fields under Settings > General, or define WP_HOME and WP_SITEURL in wp-config.php, which then take precedence over the values in the database. Old links stored in posts keep pointing to the previous address; the same documentation recommends a search and replace that respects serialized data, such as WP-CLI’s search-replace or plugins built for it.
To connect the domain, open the project, click Edit and, under Custom domains, click Add, enter the domain, and save. The Console shows the DNS records table: for subdomains such as www, a CNAME plus the validation TXT records; for the root domain, a single A record on @ (on Cloudflare, with the proxy off, as DNS only). Once DNS points correctly, the HTTPS certificate is issued automatically. Each project accepts up to 20 domains, on public HTTP projects only. As for HTTPS behind a proxy, the official image documentation says no extra variables are needed: the image adds X-Forwarded-Proto handling to wp-config.php when any of its configuration variables is set.
How much does hosting WordPress on Zenifra cost per month?
With the official template setup, the total is R$ 116.20 per month on the monthly contract: R$ 62.90 for the Premium plan, R$ 4.40 for the application’s 10 GB of disk, R$ 35.70 for the db-starter MariaDB (3 instances at R$ 11.90), and R$ 13.20 for the database disk (10 GB on each of the 3 instances). On hourly billing, the template default, the application and the database cost R$ 0.164 per hour of runtime, plus disk. Everything is in reais, paid by PIX, boleto, or card, with no IOF tax.
Each line comes from the public catalog in cents. Premium costs 6290 cents per month, 11 per hour, and 65790 per year. Persistent storage costs 44 cents per GB per month (528 per year); on an HTTP project, the persistent volume is billed for its full capacity, once. db-starter costs 1190 cents per month, 1.8 per hour, and 13090 per year, per instance, and MariaDB always uses 3 instances, so the price is multiplied by 3. The Console cost summary and the calculator show database storage per GB on each instance: the template’s 10 GB become 30 GB billed, R$ 13.20 per month.
The billing model changes the total. Running all 720 hours of the month on hourly billing, the template setup costs R$ 135.68; on the monthly contract, R$ 116.20; on the yearly contract, R$ 1,261.80 per year. That is why the template’s hourly billing suits tests, temporary copies, and the early days of a site, while a monthly or yearly contract pays off once the site stays online all the time. The cycle’s total hours are rounded up to the next full hour. On hourly billing, with everything paused, compute charges stop and only the disk remains: R$ 17.60 per month (R$ 4.40 for the application and R$ 13.20 for the database).
As the site grows, cost rises in known steps. The larger scenario swaps Premium for Premium Plus (2 vCPU and 2 GB), which the plan guide recommends when a CMS with many plugins needs more than 1 GB per instance: with the same disk and database, it comes to R$ 173.20 per month, R$ 214.88 for 720 hours on hourly billing, or R$ 1,919.80 per year. Before moving up, check memory in the Premium metrics; restarts with logs that stop abruptly are the out-of-memory sign described in the plan guide.
| Item | Configuration | Catalog price | Monthly | Hourly, 720 h | Yearly |
|---|---|---|---|---|---|
| WordPress application | Premium, 1 instance | R$ 62.90/month, R$ 0.11/h, R$ 657.90/year | R$ 62.90 | R$ 79.20 | R$ 657.90 |
| Application disk | 10 GB persistent at /var/www/html | R$ 0.44 per GB/month (R$ 5.28 per GB/year) | R$ 4.40 | R$ 4.40 | R$ 52.80 |
| MariaDB 11 database | db-starter, 3 fixed instances | R$ 11.90/month, R$ 0.018/h, R$ 130.90/year per instance | R$ 35.70 | R$ 38.88 | R$ 392.70 |
| Database disk | 10 GB on each of the 3 instances (30 GB) | R$ 0.44 per GB/month per instance | R$ 13.20 | R$ 13.20 | R$ 158.40 |
| Template total | R$ 116.20 | R$ 135.68 | R$ 1,261.80 | ||
| Larger scenario: Premium Plus instead of Premium | Premium Plus (R$ 119.90/month, R$ 0.22/h, R$ 1,315.90/year), same disk and database | R$ 173.20 | R$ 214.88 | R$ 1,919.80 |
The Console shows the total before you confirm. On the monthly contract, plan, instances, and storage stay fixed for the period, and stopping the project does not reduce the contracted amount; storage above the allowance is charged at creation. The organization’s credit, in reais, is used first; without enough credit, the charge goes to the saved card. In the calculator, choose Premium with 10 GB of persistent storage and, for the database, a db-starter MariaDB with 10 GB to reproduce the table.
When is Zenifra not the best choice for WordPress?
When you just want a site online without touching anything. If the idea is not to pick an image, not to think about file backups, not to configure email delivery, and not to watch the disk, WordPress.com or a host with managed WordPress fits better and, based on the reais price list from the WordPress.com API, costs less: Personal comes to R$ 144 per year.
There are other cases where another option works better. If you need SFTP/SSH, WP-CLI, and a staging site ready to go, without building anything, WordPress.com Business has them. If you are opening a store and want the WooCommerce extensions already installed, there is Commerce. If you want several WordPress instances serving at the same time, you need extra shared-media configuration, and that takes work. And if your site rarely changes, you can generate static pages and publish them on Zenifra’s Static plan, at R$ 5.90 per month, keeping in mind that Static does not run WordPress, PHP, or a database.
Zenifra makes sense when WordPress is one piece of a larger setup: the company already runs APIs, databases, queues, or automations on the platform and wants everything on the same bill in reais; the site needs a PHP extension that no ready-made plan offers; the team wants to control wp-config.php and the PHP version; or the team needs to spin up copies of the site for a few hours to test plugins and updates, paying only for the hours used.
After the first deploy: updates, backups, email, and plugins
Updates: the official image documentation says the default configuration follows WordPress and keeps automatic updates enabled. Because core, themes, and plugins live in /var/www/html, they are updated from the WordPress dashboard, and the persistent disk keeps the result. Changing the image tag changes PHP and Apache, but it does not reinstall the WordPress already on disk. The Zenifra documentation recommends keeping WordPress, themes, and plugins up to date.
Backups: MariaDB has automatic backups included (on db-starter, one per day with 7 days of retention), but the application’s persistent storage is not part of that routine. It is replicated in three copies, which does not protect against a plugin that deletes or corrupts files. Back up the database and the wp-content folder regularly, as the documentation asks. One route is a backup plugin that sends copies to S3-compatible storage, such as Zenifra’s Armazém, where the first 5 GB are free; another is a Scheduled Job that exports the database with mariadb-dump or mysqldump and stores the file in Armazém.
Email: the official image does not send emails, so password recovery, comment notifications, and contact forms only work after you install an SMTP plugin and configure it with the email provider you already use. Test delivery right after installing, before you depend on it.
Plugins that need PHP extensions: the official image ships no extensions beyond those WordPress needs. To add others, build your own image from the official one, as the image documentation shows, publish it for linux/amd64 to a registry, and use that image in the project; for a private registry, Zenifra accepts credentials. The same method works to adjust php.ini directives such as upload_max_filesize, by copying an .ini file to $PHP_INI_DIR/conf.d/.
FROM docker.io/wordpress:7.1.4-php8.5-apache
COPY custom.ini $PHP_INI_DIR/conf.d/What is the cheapest way to try WordPress on Zenifra?
WordPress needs MySQL or MariaDB, and MariaDB starts at db-starter, with 3 instances (R$ 35.70 per month on monthly billing, plus disk). The application uses the template’s default plan, Premium, with 1 vCPU and 1 GB.
The cheapest way to try it is hourly billing, which is already the template default: R$ 0.164 per hour of runtime for the application and the database, plus disk. Create the MariaDB and the application, test what you need, and delete both when you are done, keeping in mind that deletion is permanent and erases storage. The free 5 GB in Armazém work for storing site backups. Sign-up asks for a CPF or CNPJ, a mobile number, and an address in Brazil.
Can I use PostgreSQL instead of MariaDB?
Not with standard WordPress. The official requirements page lists only MariaDB 10.11 or greater and MySQL 8.0 or greater, and Zenifra’s template uses managed MariaDB 11. Zenifra’s managed PostgreSQL is for other applications, not for WordPress.
Templates follow the same rule: a template only lets you choose engines the author declared compatible, and the possible list is PostgreSQL, MariaDB, and ClickHouse. For WordPress, the template recommends MariaDB 11, the default version, which meets the official requirement of 10.11 or greater. If your organization needs a cheaper database, db-starter is already the smallest paid MariaDB plan.
How do I move an existing WordPress site to Zenifra?
Create the new install on Zenifra from the template and bring the content over with WordPress’s own tools: Tools > Export, on the old site, generates a WXR file with posts, pages, custom post types, comments, custom fields, categories, tags, and users; Tools > Import > WordPress, on the new site, imports that file and can download and import attachments if you check the option to import file attachments. Themes and plugins are reinstalled from the dashboard.
For a full copy, of files and database, the WordPress migration documentation says to start by backing up everything. If the domain and URLs stay the same, you only need to copy files and database and adjust the connection details; on Zenifra, those details come from the WORDPRESS_DB_* variables instead of editing wp-config.php. The old database dump can be imported into the managed MariaDB from a client outside Zenifra, while the database’s public access is on (the default), connecting over TLS to the host shown in the Console. For the files, the official image documentation points to another path: place wp-content under /usr/src/wordpress in your own image, which is copied to /var/www/html on the first startup.
If the URLs change, for example because you tested on the *.clients.zenifra.com address before pointing the domain, follow the order in the WordPress documentation: change the URLs under Settings > General or with WP_HOME and WP_SITEURL, and run the search and replace with a tool that respects serialized data, such as WP-CLI’s search-replace. Keep the old site online until the domain’s DNS points to Zenifra and the HTTPS certificate shows as active in the Console.