HostMídia in Brazil: managed WordPress pricing and JetBackup restoration

Who HostMídia may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

Brazilian Portuguese.

Control panel

cPanel; the tutorial presents Portuguese labels and JetBackup 5. Account locale to confirm.

Support

Documentation and channels in Portuguese; Help Desk with on-call cover and priority for emergencies outside office hours. French and English not established.

A managed offer for a team retaining control

HostMídia offers a distinct managed WordPress hosting range in Brazil. It mainly interests teams wanting to retain access to files, database and email in cPanel while being able to call on the provider when installation, an update or a security incident exceeds their skills. The page advertises a WordPress manager, daily copies and a malware cleanup service. This is a useful combination for a small or medium business with a website manager that does not want to maintain a server itself.

This profile covers WordPress I through IV in the Brazilian managed catalog. General web hosting plans, virtual servers and the website builder are different products. The offer is presented in Portuguese and Brazilian reais. The privacy policy identifies Ditcom Internet Ltda. in São Paulo; the infrastructure page mentions São Paulo and Orlando. This supports describing the market as Brazilian without inferring that every installation, backup and mailbox will physically be in Brazil.

For an existing website, the first decision concerns business continuity. A team able to recover files but losing quote-request messages has restored only part of the service. Inventory the website, database, mailboxes, DNS zones and external services separately. The decisive factors are confirmed retention for the plan, the ability to recover a component without overwriting the rest of the account and availability of a Portuguese-speaking contact during an outage. Public sources differ on retention: this is a decision point from the outset.

Brazilian prices: distinguish the first charge from renewal

The rows below give, for each term, the initial public amount followed by the reference amount for the same cycle. Amounts are in BRL for hosting, recorded on November 10, 2026. The first figure is the cards’ introductory price; the second is an estimate based on the base rate and renewal discount displayed for longer cycles. These estimates are not invoice amounts.

WordPress I: 1 month, BRL 69.99 then 69.99; 3 months, BRL 209.97 then 209.97; 12 months, BRL 587.92 then 755.89; 24 months, BRL 1,007.86 then 1,343.81; 36 months, BRL 1,259.82 then 1,763.75.

WordPress II: 1 month, BRL 109.99 then 109.99; 3 months, BRL 329.97 then 329.97; 12 months, BRL 923.92 then 1,187.89; 24 months, BRL 1,583.86 then 2,111.81; 36 months, BRL 1,979.82 then 2,771.75.

WordPress III: 1 month, BRL 189.99 then 189.99; 3 months, BRL 569.97 then 569.97; 12 months, BRL 1,595.92 then 2,051.89; 24 months, BRL 2,735.86 then 3,647.81; 36 months, BRL 3,419.82 then 4,787.75.

WordPress IV: 1 month, BRL 349.99 then 349.99; 3 months, BRL 1,049.97 then 1,049.97; 12 months, BRL 2,939.92 then 3,779.89; 24 months, BRL 5,039.86 then 6,719.81; 36 months, BRL 6,299.82 then 8,819.75.

For twelve-, twenty-four- and thirty-six-month cycles, the page advertises discounts of 30%, 40% and 50% respectively on the first payment, then 10%, 20% and 30% at renewal relative to the base schedule. The discount rate is not a locked price: the provider’s terms allow changes to promotions and rates among other things. For annual WordPress I, two cycles at the recorded amounts total R$1,343.81 before domain, options and any taxes. The card at R$34.99 per month requires immediate payment of R$1,259.82 for three years. Rounding of monthly equivalents makes the published totals preferable.

The cards advertise free domain registration for the first year from an annual cycle upward, for .com.br, .com, .net or .org. Ask whether transfers also qualify and which rate applies at expiry. The domain may need renewal before the hosting cycle ends. Clause 3.10 requires an adult holder to have a Brazilian CPF tax identifier, or a CNPJ for a company. If you do not have this identifier, confirm account eligibility and accepted documents before initiating migration. Final tax amounts and accepted payment methods for a foreign holder are not established. To obtain a usable budget, request separate hosting and domain lines with dates, plus the renewal treatment for email and any options.

Choose by workload and scope, not website count

WordPress I: 1 website, 20 GB SSD, CPU / RAM: 1 / 2 GB, processes / inodes: 20 / 200,000.

WordPress II: 2 websites, 40 GB SSD, CPU / RAM: 2 / 4 GB, processes / inodes: 30 / 400,000.

WordPress III: 3 websites, 60 GB SSD, CPU / RAM: 3 / 6 GB, processes / inodes: 40 / 600,000.

WordPress IV: 4 websites, 80 GB SSD, CPU / RAM: 4 / 8 GB, processes / inodes: 60 / 800,000.

The first two tiers display 200 and 400 GB of monthly traffic; IV displays 800 GB. For III, the card states 600 GB and the comparison 800 GB. Do not budget usage above 600 GB before obtaining the applicable account value. The dedicated IP advertised for IV and priority support advertised for III and IV may matter more than the fourth website. CPU, memory and process figures belong to the range; they describe neither per-request performance nor capacity reserved for each website. For three clients with incompatible needs, evaluate three separate accounts instead of filling one plan.

Space also serves email and ancillary files depending on account configuration. Count thumbnails, cache files, logs and messages, then measure working space required to unpack an archive. Small files can exhaust the inode quota while the disk is far from full. For a store, measure responses of pages that cannot be cached: cart, checkout and administration. The provider describes LiteSpeed, LSCache and CloudLinux; no store throughput, response time or cache benefit was measured in this profile.

The page cites PHP versions up to 8.4, MariaDB or MySQL, phpMyAdmin and SSH or Git access. Ask about the engine and version actually assigned, effective SSH access and how scheduled tasks run. On a migrated website, then check theme dependencies, PHP extensions and email sending. A website may display its home page while its importer or subscription task is broken.

Portuguese support and WordPress responsibilities

Sales pages, terms and tutorials are in Brazilian Portuguese. The restoration guide shows translated cPanel menus with the JetBackup name in English. This provides a workflow reference; account language settings and French or English assistance have not been established. According to the terms, telephone and chat are open on weekdays from 9 to 18 except national holidays; confirm the time zone with the provider. The Help Desk accepts requests every day. Outside office hours, on-call cover prioritizes urgent incidents. A ticket can therefore be accepted at any time while a configuration request waits for regular service to resume. The catalog reserves priority advanced support for offers III and IV without a numerical resolution deadline on this page.

The managed range page advertises help installing or updating WordPress, plus malware cleanup. However, the general terms limit third-party code correction and place application maintenance under the customer’s responsibility. Clarify who intervenes if a plugin causes an update to fail, a custom theme triggers an error or administrator accounts are compromised. Advertised cleanup alone does not guarantee content restoration, identification of the intrusion vector or correction of vulnerable code.

A useful ticket provides the domain, incident time with time zone, last change, error codes and last known date the function worked. State the visitor impact and whether production may be overwritten or an isolated copy is needed. Keep logs before making corrections, remove credentials and personal data from extracts, then retain the ticket number to coordinate provider and maintainer. When the failure involves payment or shipping, specify the complete operation that fails instead of simply saying the website is slow.

Recover a website with JetBackup and an independent copy

Editorial illustration based on the official documentation. — Illustration by BlogPasCher.Open full-size illustration ↗

The product page advertises daily copies on external servers for fourteen days, covering files, emails and databases, with free restoration. It does not specify the number of permitted restorations. Section 9 of the general terms mentions seven days, and a support guide about compromised cPanel also cites seven days. The difference may reflect document scope; public documentation is insufficient to establish fourteen-day coverage for a particular account. Ask for the applicable rule before designing the recovery plan. The terms also list R$50 for partial recovery and R$150 for a full account when the plan does not include restorations. These generic fees are not presented as the rates for the four managed plans. In the meantime, do not depend on recovery to D−14. External to the server does not necessarily mean in another region, accessible outside the account or retained after cancellation.

On an active account, HostMídia’s JetBackup 5 tutorial says to search for JetBackup 5 in cPanel, open the home directory and select a date and files to restore. A root website’s folder is generally public_html; another domain may have a different path. For the database, note its name in the WordPress configuration without exposing the password, then select the corresponding point in the databases section. Export the current state before starting a restoration. If production receives orders, test recovery on a private destination if possible; an older copy can remove orders recorded since then. The official example restores files and database from the same date. If only one plugin was replaced by mistake, first examine whether its files can be recovered or its known version reinstalled without rolling back the database containing recent orders.

Before any production recovery, export the current state and retain the timestamps of the latest writes. For a full restoration, check which other websites, mailboxes and settings are in scope. On the destination, check administration, media, permalinks and the failing function. For a store, also compare identifiers and statuses of orders newer than the restored point. The procedure documents panel actions without establishing a restoration time or actual availability of every point. Store encrypted copies outside the account and regularly test recovery on a separate destination with email and payment outputs disabled. The terms give a window from 22 to 6 for generation with the cPanel backup tool and a 48-hour deadline for removing the created archive. Check the time zone and account rule. They also specify a SQL import limit of 100 MB through phpMyAdmin; for a larger database, validate the import method before an incident.

Migrate to HostMídia and prepare departure

The migration page advertises free service for accounts up to 10 GB and 200,000 inodes. Above that, the team requires an assessment of procedures and costs. A source panel other than cPanel may require manual migration and prior review. The free threshold does not match WordPress I’s disk quota: a 15 GB account can fit on the destination while exceeding the published threshold. Give the provider separate web and email volumes, database sizes and the domain list, then verify that accepted scope includes messages, aliases, redirects and scheduled tasks.

Plan an initial copy, a destination test and a final synchronization before changing DNS. Use a private test address or local resolution; check the certificate, forms, redirects and email before changing public records. For a store, limit new writes during final synchronization and designate the authoritative database at resumption. If email stays with a third party, retain its MX, SPF and DKIM; if email moves, validate receipt from an external address and handle messages reaching the old server during propagation. Set a rollback condition and how long the source will remain available.

On departure, keep an independent archive of files and database, mail exports and a DNS record. Section 16 of the terms announces immediate data deletion after cancellation confirmation; subsequent recovery depends on technical feasibility and costs R$300 if possible. This differs from free restorations on an active account. The same section provides, under its listed conditions, a limited refund of the unused period on certain cycles after forty-five days. Rely neither on a full refund for a long cycle nor on a final recovery after closure. Validate exports and independent domain control before triggering this step.

AI: separate management tools from generation

The WordPress manager described on HostMídia’s page installs, manages and updates the CMS. The HostMídia website builder is presented separately with templates and visual editing. These pages do not establish that the four managed offers include a generative assistant writing in the WordPress editor, creating images or modifying pages on request. An installer and caching mechanism do not imply model access either. If this feature is part of the specification, ask for the tool’s exact name, where it appears and whether the intended plan grants access.

A creation tool can be chosen separately with its own pricing and rules. Before selecting a module, check whether it produces editable WordPress blocks, theme-specific elements or pages dependent on an external service. An agency delivering a website must be able to identify who owns the account and what remains after transfer. On a working copy, open content with an editor account, then check reading and editing without connecting to the external service where possible. This check is more valuable than a general portability claim. If content includes internal documents or customer information, also assess which elements pass through the tool and under what conditions.

For a store rarely changing its pages, an extra license may outweigh time savings. For a small team publishing often, first decide who reviews generated prices and promises, who approves visuals and how to return to the previous version. This profile identifies no model, quota, generation language or price for WordPress AI included in these plans. The pricing budget should therefore assume nothing for this item.

Decide using verifiable criteria

WordPress I is a relevant comparison point for a single website if its media, email and temporary files leave headroom. WordPress II is justified when a second website or additional resources are needed. For III and IV, quantify the difference made by support priority, capacity and, for IV, the dedicated IP. A more expensive catalog does not solve slow code or a poorly defined recovery deadline. If the main risk is losing data since the last order, first invest in backup frequency and the ability to restore that data elsewhere.

Before choosing the provider, assemble a short operations sheet: domain and account owners, cycle and renewal, location of each component, restoration trigger and authorization process. Obtain written confirmation of seven or fourteen days, recovery capabilities by database and folder, email retention and limits for the intended plan. For WordPress III, add the traffic cap. If answers are vague and the project requires a precise duration or location, keep another host in the comparison and validate an independent recovery route.

Finally, define acceptance testing suited to the website. A brochure website must respond at its main addresses, send a form and let the team publish a correction. A store must additionally process an order using the payment provider’s test mode on an isolated copy, check notifications to test recipients and rerun a scheduled task without duplication. A business also hosting its email must be able to recover archives without depending on the account hosting them. This testing turns “managed” into concrete decisions: who is called, what they can change and how much data the organization can afford to lose.

Prepare your site

• Choose a backup tool and prepare recovery
• WordPress migration, staging and imports: choose the right tool
• Unmet WordPress requirements: check PHP and MySQL or MariaDB