1984 Hosting for WordPress in Iceland: pricing and backups
1984 Hosting’s WordPress plans in Iceland, initial and renewal terms, migration, the Security Pack and backup limitations.
Read more →

Site appearance
Web hosting
Six WordPress offers in Mauritius and an exercise for checking original files and media variants after an update.
Source published: · Source updated: · Editorial policy
Visit the official cloud.mu website ↗
This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.
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.
| Plan | Price and billing | Resources and limits |
|---|---|---|
| WP Starter | 499 MUR including VAT per month or 5,389 MUR including VAT per year according to the table. Renewal: Automatic renewal for the same term under the general terms. No separate future amount published. Price recorded on November 10, 2026. Monthly or annual. Displayed amounts include VAT. General terms require thirty days’ notice of non-renewal. | 25 GB SSD, 1 site and 1 database. 25 mailboxes. Public retention discrepancy from 7 to 30 days. Check per-account resources and how a clone is counted. |
| WP Premium | 749 MUR including VAT per month or 8,089 MUR including VAT per year according to the table. Renewal: Automatic renewal for the same term under the general terms. No separate future amount published. Price recorded on November 10, 2026. Monthly or annual. Displayed amounts include VAT. General terms require thirty days’ notice of non-renewal. | 50 GB SSD, 2 sites and 2 databases. 50 mailboxes. Public retention discrepancy from 7 to 30 days. Check per-account resources and how a clone is counted. |
| WP Business | 1,299 MUR including VAT per month or 14,029 MUR including VAT per year according to the table. Renewal: Automatic renewal for the same term under the general terms. No separate future amount published. Price recorded on November 10, 2026. Monthly or annual. Displayed amounts include VAT. General terms require thirty days’ notice of non-renewal. | 100 GB SSD, 3 sites and 3 databases. No advertised numerical mailbox ceiling. Public retention discrepancy from 7 to 30 days. Check per-account resources and how a clone is counted. |
| WP Ultimate | 2,149 MUR including VAT per month or 23,209 MUR including VAT per year according to the table. Renewal: Automatic renewal for the same term under the general terms. No separate future amount published. Price recorded on November 10, 2026. Monthly or annual. Displayed amounts include VAT. General terms require thirty days’ notice of non-renewal. | 200 GB SSD, 5 sites and 5 databases. No advertised numerical mailbox ceiling. Public retention discrepancy from 7 to 30 days. Check per-account resources and how a clone is counted. |
| WP Ultimate+ | 3,149 MUR including VAT per month or 34,009 MUR including VAT per year according to the table. Renewal: Automatic renewal for the same term under the general terms. No separate future amount published. Price recorded on November 10, 2026. Monthly or annual. Displayed amounts include VAT. General terms require thirty days’ notice of non-renewal. | 300 GB SSD, 6 sites and 6 databases. No advertised numerical mailbox ceiling. Public retention discrepancy from 7 to 30 days. Check per-account resources and how a clone is counted. |
| WP Ultimate++ | 4,989 MUR including VAT per month or 53,882 MUR including VAT per year according to the table. Renewal: Automatic renewal for the same term under the general terms. No separate future amount published. Price recorded on November 10, 2026. Monthly or annual. Displayed amounts include VAT. General terms require thirty days’ notice of non-renewal. | 500 GB SSD, 7 sites and 7 databases. No advertised numerical mailbox ceiling. Public retention discrepancy from 7 to 30 days. Check per-account resources and how a clone is counted. |
cloud.mu offers WordPress hosting advertised in Ébène, with cPanel, LiteSpeed and WordPress Toolkit Deluxe. In this case, a fictional Mauritian publication needs to update an image-related plugin. It wants to preserve originals, recover the correct thumbnail sizes and ensure the update remains reproducible on a copy. Plan choice depends on site count, image volume and space needed for regeneration.
The sales page places two backup durations side by side. This profile distinguishes them and explains how to arrange recovery even if the expected point is no longer available. It also separates the role of caching, the plugin and what the panel can check. A cached page may continue showing an old thumbnail after an update. The project therefore establishes a reference before the operation.
The exercise compares fictional image inventories and checks dimensions, responses and originals. It runs in Node.js without WordPress, a browser or requests. Acceptance testing on a real copy remains a separate operation.
The sales cards display two cycles in Mauritian rupees and specify that VAT is included. The offer descriptions reproduce displayed annual amounts, which may differ from a rounded calculation based on the monthly price. Compare each amount with twelve monthly payments at the observed rate to measure the cycle difference. The public WordPress catalogue confirms all six plan names. Read the first invoice date, selected cycle and possible additional fees in the contractual offer before committing.
For Starter, the displayed annual cycle costs 599 MUR less than twelve payments at the displayed monthly amount. This difference compares two observed billing cycles. The cards do not present it as a first-cycle discount followed by a different renewal schedule. The Mauritian tax authority states a standard VAT rate of 15%. The site already displays VAT-inclusive prices. Keep the domain, any out-of-plan email and additional interventions on separate lines to compare two proposals.
The general terms state that the subscription renews automatically for a term equivalent to the initial one. They require at least thirty calendar days’ written notice to prevent renewal and separately address termination for convenience at sixty days. They also allow some price adjustments with written notice. The sales FAQ states that a monthly service can be stopped before the next cycle. The definition of writing and the email-notification clause do not fully align. Confirm the applicable notice period and accepted notification method for your offer. Obtain the exact renewal price, how notice applies to the chosen cycle and the formal notification channel. If choosing monthly service to prepare a transfer, ask from the outset when termination can take effect.
The six plans allocate 25 to 500 GB SSD. Site and database counts are one, two, three, five, six or seven depending on the level. Starter displays twenty-five mailboxes, Premium fifty, and higher levels email accounts without a numerical quota advertised on the card. Traffic is displayed without a quantified ceiling. The public pages examined do not detail EP, CPU, RAM, inodes or I/O for each plan. Have the account’s PHP settings distinguished from cumulative usage limits. A storage table useful for budgeting does not establish how many thumbnails can be generated simultaneously.
A private copy and local archive may occupy disk alongside production. Measure originals, variants, database export and temporary files separately. An image can have multiple size or format variants. Total bytes and file count may therefore grow at different rates. With Starter, check how a temporary copy is counted if you already have one site and its database. If the account does not permit a second installation, prepare a separate private environment or a plan explicitly allowing it. Changing plans for storage alone does not validate other limits.
cloud.mu advertises its WordPress infrastructure in Ébène. For a residency requirement, ask for backup locations, regions processing logs or ancillary services and export options. The country advertised for WordPress servers does not identify where all copies reside. A publication using licensed photos must also check whether originals need to remain available in an independent archive. When changing hosts, this inventory helps separate published images, working files and references that must be retained.
The range advertises cPanel, LiteSpeed, LSCache and WP Toolkit Deluxe. The provider describes cloning and Smart Updates, which tries updates in a separate environment. cPanel documentation locates WP Toolkit under Domains when the provider enables it. Automated page checking still needs business-level verification, such as served dimensions, intended format and original-file integrity. Also test caching and optimization separately if the plugin changes variant formats.
The cloud.mu public site and guides consulted are in English. The provider advertises a team speaking English, French and Creole. The terms describe a help center during business hours. Telephone and chat appear on the site. Check the appropriate recovery channel and when the team can be reached. Panel language depends on version and host options. Recent cPanel documentation has changed language settings and removed translations from its supported list. Confirm French availability on the delivered installation.
cloud.mu presents a separate Site Builder with a composition interface. The WordPress table quantifies no generative AI credits, and the Site Builder page consulted does not specify any. Smart Updates is described as an automated testing tool. For the publication’s case, keep reference originals and expected rendering approved by the editorial team. If a third-party tool produces images, check rights and files separately from the WordPress update.
The six-plan table and public catalogue advertise thirty days of backups. A descriptive section and FAQ on the same WordPress page describe daily copies retained for seven days, including web content, databases and email. The general terms leave customers responsible for maintaining copies and exclude a general obligation to make additional copies. Confirm the advertised thirty days for your offer. Meanwhile, do not base your schedule on a point older than the FAQ’s seven days being available. The FAQ describes restoration through cPanel. The terms provide for intervention fees if recovery does not result from a service error. Before choosing, request plan-specific confirmation of retention, scope, oldest visible copy and any restoration fees.
To prepare the change, keep an SQL export, file copy and active-version list together. For a few important images, record SHA-256 checksums of originals and archive expected dimensions and formats. A filename or URL may remain unchanged when content changes. The checksum checks the reference file’s content. On the restored site, also validate the relationship between the article, media-library entry and variant actually requested by the browser. Well-preserved files can produce an incorrect page if the database still points to old names.
The provider advertises a free transfer from an existing cPanel account. For the publication’s team, record transfer scope and handle site import, email and domain or DNS changes separately. Another panel type or partial migration may require a quote. Keep the independent copy and test it before scheduling deletion. The general terms provide that data may be erased after service ends and that assistance with recovery after closure may be charged. The safe time to verify the export therefore precedes contract termination.
Three fictitious datasets show variation and original discrepancies before validation. — Illustration by BlogPasCher.Open full-size illustration ↗ In the extracted ZIP directory, run node EXERCICE-CLOUD-MU.cjs. The script reads neither a site nor real media. It computes checksums on fictional strings and compares simulated observations with an expected inventory. The output RESULTAT-CLOUD-MU.json contains two reference checksums, three variants and each trial’s verdict. Two variants must be square at 480 pixels per side. An article image must measure 1,200 by 800 pixels. All variants in this case must be served as WebP. This rule belongs to the scenario and is not an advertised default WordPress or cloud.mu setting.
The “incomplete variants” candidate fails on three points. The square harbor thumbnail has a different size, the article variant returns an unavailable response, and the market thumbnail presents an unexpected type despite a success status. The “modified original” candidate has the correct variants but a different original checksum. Only the third candidate satisfies every check. The assertions also require the labels and order of discrepancies in the first case. They make an unintended reduction of acceptance testing to mere file presence visible.
To repeat the exercise with another theme, choose a landscape photograph and another whose composition makes cropping obvious. Enter actually configured dimensions in the inventory, including theme-specific variants. Decide the expected MIME type and which alternative formats are allowed. A small photo may be too small to generate a large variant. Record that case as a documented exception rather than turning it into an arbitrary failure. Use checksums to check originals. Intended optimization of a variant may change its checksum even when display remains correct.
On a private copy, open WP Toolkit from cPanel if enabled. Select the installation, use Clone if configuration permits, and check the destination address and database before proceeding. Disable real sending and tasks connected to production on this copy. Update one plugin at a time. If using Smart Updates, read its result, then open reference articles on the copy you control. Record the file actually served and its natural dimensions as well as displayed dimensions. In browser developer tools, the Network tab lets you check each media response’s status and type.
In WordPress, consult Tools, Site Health, then media-processing information to identify the available engine. The provider documents enabling GD through the cPanel PHP selector. Check the PHP version used by the copy and support for the desired format. If WP-CLI is installed in your local environment, wp media image-size lists registered sizes. From the copy’s root, the second command regenerates one size for the selected identifier and requests retention of old thumbnails. Then check files and metadata before concluding. Replace 123 with a reference image’s identifier. The name thumbnail is a WordPress size. It does not necessarily correspond to the exercise’s square thumbnail.
Compare rendering after purging the copy’s cache, then with caching in place. If the original and variants exist but an article still requests an incorrect URL, check metadata and the published address before regenerating the entire catalogue. If PHP versions or processed images differ between trials, return to the initial dataset.
wp media image-size
wp media regenerate 123 --image_size=thumbnail --skip-deleteFor the publication, authorize the update only if each reference image’s original remains identical and useful variants are available in the chosen format and dimensions. A success status is insufficient. A page may receive HTML instead of an image while retaining a correctly sized box on screen. Check the type, file and rendering. Handle redirects, alternative formats and impossible sizes under rules set before the trial. An intentional compression change may remain acceptable if it preserves framing, the source file and minimum quality approved by the editorial team.
If regeneration fails, start with the smallest reproducible cause. A missing size may relate to the theme. A missing format may depend on the PHP engine or plugin. An unexpected response may come from a wrong address, redirect or cached response. After correcting it, reset the copy or reproduce the same starting point before comparing results. Keep the reference image set and size record for the next update. If reverting to the previous state, check that the restored database version points to its corresponding files and variants.
Plan choice then depends on how many sites and databases actually need to be retained in parallel. The annual budget may be attractive if a test environment is available and renewal and exit dates are clear. If the plan leaves no room for a copy, a separate test environment may cost less than a permanent plan upgrade. If the expected backup point depends on the discrepancy between seven and thirty days, keep an independent copy and have plan retention confirmed in writing. Set the decision time and rollback owner before changing production.
Use these references to check the features, requirements and limitations described. Reading documentation is not a practical test.
English translation of the reviewed French edition. Code examples retain their original identifiers, comments and output strings for reproducibility. Linked exercise files and original screenshots may contain French. No new practical tests or price checks are implied by translation.
1984 Hosting’s WordPress plans in Iceland, initial and renewal terms, migration, the Security Pack and backup limitations.
Read more →Compare 34SP.com WordPress containers, shared memory, staging copies, downloadable snapshots and site migration.
Read more →Compare AEserver’s managed WordPress prices and check whether your network must be split into independent installations before migration.
Read more →