Hostinger or SiteGround: backups, staging and costs after promotions

Analysis of official documentation, with no testing on a paid account.

Differences that change choice

Understanding what a backup protects

A useful backup must be recent, accessible and restoreable in the right place. Check the files and database covered, frequency and recovery modalities. Find the copy that contains the modification to recover and the person able to restore it.

In SiteGround, the documentation describes staging especially for GrowBig, GoGeek and Cloud. Check your offer before making it an acquired criterion. For Hostinger, also choose the plan whose functions correspond to the chosen maintenance process.

Test an update before the actual site

On a fictional test copy, update a plugin that affects a form. Check submission, receipt and any integrations. Then examine what deployment replaces: files only, the database or the whole site. A store receiving orders between the two stages needs an appropriate procedure.

If DNS is managed elsewhere, some records must remain managed by that provider. Do not inadvertently move email services when changing the zone. The website host and domain manager may be different services.

Compare a budget that lasts

Record the price after the promotion, the renewal term and the selected add-ons. Include management time if a provider handles backups and updates. A cheaper plan is worthwhile only if it supports the workflow you need.

Choose hosting whose limits and incident recovery process you understand. Assess speed using your own site. Measure the same pages with the same content and similar conditions, then keep laboratory results separate from visitors' actual experience.

A test copy is not automatically a risk-free publication

The deployment documentation SiteGround distinguishes Full Deploy, which replaces files and public website base, and Custom Deploy, which compares changes. The choice is not just a faster button: the database may contain more recent data than the copy.

Consider this example: you edit a form on a copy made on Tuesday. On Wednesday, two requests arrive on the public website. Before publishing on Thursday, you need to know whether those requests are stored in a table that will be replaced. Work in a test environment with fictitious data; do not try this scenario on real customer records.

1. Identify the data affected by the change and those that must remain intact.
2. Check after simulated deployment the form, message receipt and requests created between the two steps.
3. Run the expected reverse and check what it restores. Keep reference backup and time stamping.

What should be included in the estimate

Enter the plan, initial duration, renewal, pre-production functions and the person responsible for updates. For Hostinger, the overview of WordPress plans shall be read at the level of the chosen plan. If no team member can explain the restoration, add a maintenance service to the budget before choosing from the subscription alone.

Reviews to consult

• Hostinger
• SiteGround