AEserver in the UAE: managed pricing and the Multisite restriction

Who AEserver 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

Product page in English and a help-centre entry under an Arabic path.

Control panel

Managed administration interface advertised. Confirm its language. The billing portal offers languages including French, English and Arabic.

Support

Local 24/7 assistance advertised. English and Arabic mentioned. Telephone hours are separate.

AEserver in the UAE: deciding what to do with a WordPress network

AEserver sells a managed WordPress range from the United Arab Emirates, advertising staging, updates and backups. The provider explicitly excludes WordPress Multisite installations from this range. A fictional Dubai team runs two linked sites in one network. The site count advertised on a pricing card and the accepted installation type are separate criteria.

The team wants to know whether it can retain the network as it stands or must separate the sites. It examines a configuration record, table families and shared services. The local exercise compares those three elements. A single-site configuration is accepted for further checking. A confirmed network or contradictory inventory blocks direct import. The test also identifies dependencies to address before any split.

The decision then depends on the pricing term, number of installations, advertised hosting region and migration scope. This profile examines the managed product and its limitations. It separates the provider’s location, server region and location of stored copies.

Distinguishing monthly prices and the dirham billing term

On November 10, 2026, the Managed WordPress table showed AED 157.50 per month for Starter, AED 315 for Business and AED 450 for Enterprise as monthly equivalents billed over thirty-six months. The crossed-out reference prices were AED 210, 420 and 600, and the advertised discount was 25%. Multiplying the three highlighted prices by thirty-six gives AED 5,670, 11,340 and 16,200 excluding tax. These totals are calculated from the table and must be compared with the amount invoiced for the full term.

The public catalogue for the same range lists plans named Starter EU, Business EU and Enterprise EU with monthly payments of AED 280, 560 and 800. These values use a different term. They do not establish the renewal price for a thirty-six-month commitment. The catalogue states that prices exclude UAE VAT and taxation depends on where the service is used. At the standard UAE VAT rate of 5%, where applicable, the thirty-six-month Starter example comes to AED 5,953.50 including tax. The quote should separate the initial period, discount, tax and domain and email renewal dates.

The cancellation policy describes a deadline of at least three working days before the due date to prevent renewal of a hosting subscription on automatic payment. It states that renewal may be processed one day before the due date. Confirm the amount and duration of the discounted plan’s next term before purchase. To compare monthly and thirty-six-month commitments, record the billing date, actual amount due and exit terms for each. The crossed-out price is a commercial reference. The refund policy also excludes Managed WordPress from the thirty-day guarantee available for certain shared plans.

Reading quotas and identifying the service region

The cards show 15 GB SSD and 100,000 monthly visits for Starter, 50 GB and 400,000 visits for Business, and 250 GB and 1,000,000 visits for Enterprise. The visit label alone does not explain how the provider counts visits or what happens after an overage. The page advertises a platform dedicated to the product and resource options. CPU and RAM quantities and the exact number of usable independent installations per plan still need confirmation. For a team splitting a network, each site needs its own slot and database.

The product FAQ refers to a European data centre for managed WordPress, and the catalogue confirms the EU suffix on these three plans. Those materials do not specify the hosting country or city or copy locations. AEserver publishes a separate Managed WordPress Dubai catalogue with Premium, Premium Plus and Enterprise at AED 435, 544 and 680 per month excluding UAE VAT. It lists 3, 10 and 15 sites respectively. Those capacities apply to the Dubai plans. The Dubai catalogue lists PHP 7. Confirm the version actually offered before importing a site there. Where data residency determines the choice, obtain an answer for the exact plan and record site, database and backup locations separately.

SSL, PHP 8.x, MariaDB and a test environment are advertised. Confirm the destination’s PHP version and compatibility with the plugins that will remain after separation. If the team must keep per-site integrations, it also needs to know whether it can access logs, create scheduled tasks and choose separate PHP versions. The managed plan does not support WordPress Multisite. More disk space does not change that rule.

Defining managed services, support and AI

AEserver advertises preinstalled WordPress, cloning between test and production, caching and core updates. The page describes plugin and theme updates configurable per site, excluding custom themes by default. It advertises SSH and SFTP on request. Clarify dashboard contents, database access and permitted operations for each plan before making an exit procedure depend on a command. Retain responsibility for validating update results on each separated installation.

The range’s reviewed page is in English, and the provider publishes a help centre under an Arabic path. It advertises continuous local support in the UAE. A guide mentions support in English and Arabic, with a telephone line Monday to Saturday from 9 a.m. to 6 p.m. UAE time. The billing portal also offers French among its interface languages. Confirm the managed dashboard’s languages and the exact scope of help with splitting a network. Assistance migrating a standard site does not demonstrate support for this transformation.

AEserver sells Spark AI, a WordPress site builder that generates content from a description. Its page shows an equivalent starting at AED 30 per month over twelve months or more. Its AI Builder product offers websites and web applications with a separate subscription and credits on its own platform. The three Managed WordPress EU cards do not detail access to those services or generation quotas. If the team considers replacing an old theme with a generated design, treat rebuilding as a separate editorial and technical decision from extracting the network. Accounts and media to preserve remain migration data.

Backing up components and preparing to leave

The three cards advertise automatic daily backups. The page mentions several recovery points for the site and database. The general terms state that standard backup is provided without a general integrity guarantee. An AEserver article mentions thirty days of retention in the UAE for managed WordPress in Dubai. For EU plans, confirm retention duration, recovery granularity, archive location and the cost of a specific intervention. The provider also mentions paid backup services with their own agreements. Clarify what the plan includes before relying on recovery of the network or its future independent installations.

The AEserver guide describes inbound migration through a ticket, followed by preparation in a test environment before transfer. The sales profile advertises free migration. For a network, separately record what the team can export and what the provider accepts for import. Describe network plugins, mapped domains, both sites, media volume and shared accounts. Request a written scope and avoid sending credentials through an unintended channel.

Prepare a copy of the files and the complete network database before extracting it. Files include media, themes and plugins, with their versions and destinations. The database includes site-specific tables and global data needed to understand accounts and settings. A WordPress editorial export in XML format supports a different task: moving one site’s content. Also record attachments, plugin-specific settings and email. Validation requires an exit copy that the team has already opened with its own access.

Practising a network check before migration

Guidance for preparing a targeted restore. — Illustration by BlogPasCher.Open full-size illustration ↗

The ZIP under “Prepare your site” contains EXERCICE-AESERVER.cjs, which processes fictional records. The supplied result was obtained with Node 22.16.0. The example prefix is atelier_. The single-site inventory contains the content, options and account table families selected for the test. The network inventory adds atelier_blogs, atelier_site, atelier_sitemeta and two numbered tables for the second site. The configuration flag is supplied as test data. The program does not read wp-config.php, connect to a database or create an installation.

The single-site control case receives permission to continue checking. The network case is rejected for direct import. The team has inventoried site 2’s media and still needs to examine shared accounts, network-activated plugins, mapped domains and scheduled tasks. The script also blocks cases where network tables contradict the configuration, the record cannot determine the mode, or a single-site installation lacks basic tables. It identifies the missing tables in the last case. The result does not prove that a site accepted by the model will fit a plan or that its plugins are compatible.

For a real inventory, record the prefix and network settings from wp-config.php using a copy, without copying its secrets into a report. Check the sites in network administration and compare that list with the tables. Account tables also exist in single-site installations. Their presence alone does not establish network mode. WordPress code distinguishes global tables from site-specific tables and permits certain custom account-table settings. The supplied program models only its dataset’s prefix and table families.

node .\EXERCICE-AESERVER.cjs

Preparing to separate the sites and roll back

To separate the two sites, create two private destinations, each with a database and a test domain. Start by inventorying content, media, roles, theme settings and plugins. When the task concerns editorial content, use Outils > Exporter (Tools > Export) on the source site, then open Outils > Importer (Tools > Import) on the destination and check content types. XML export is not enough to recreate a business plugin or its data in private tables. Retain a full network archive and handle that data using the plugin’s procedure.

Recreate the required roles in each installation and check accounts with test credentials. Network activation can hide a lack of site-specific configuration or make an integration unavailable after separation. Check theme, media, form and task loading, plus each role’s access. Record public URLs, redirects and links between the two sites. Assign an owner to each domain and record which installation will answer at each address. If content shares media or a service, identify the new location before changing links.

At cutover, define the final copy point and handle content that changes between export and opening. Until both destinations pass their tests, keep the original network and its settings accessible. If the process fails, restore routing or retain the original destination and reconcile writes made on the copies. If separation loses a function tied to shared data, the test result rejects the new architecture for that specific need. The decision belongs to the team responsible for content and accounts.

Deciding before reserving a WordPress destination

For a single-site installation, the cards provide an initial choice by volume, and the range advertises backups, staging and update management. The Dubai team must obtain the number of independent installations per plan, the total cost of the selected period and the assigned region. If paying monthly, the price must match the EU plan and term in the quote. If choosing thirty-six months, retain the initial price, tax and renewal schedule separately. The tax notice published on the Business page corroborates the catalogue’s presentation excluding VAT.

Once the network is confirmed, the product rule excludes direct import even if the combined media fits on disk. Separation becomes an option when each installation can recreate the functions in use. Both destinations must display the expected content, open their media and apply the intended roles. The domain administrator must be able to identify the destination and rollback rule for each name. The WordPress administrator must be able to reopen the latest full network copy.

If inventory evidence conflicts, postpone choosing a plan until the database and configuration matching the live site are identified. If the inventory is consistent but accounts or plugins must remain shared, retain the requirement for hosting that supports the network. For a validated split, keep the source during checks of both destinations and record the latest writes before closing its access. A signed decision identifies the selected mode, outstanding dependencies and the person authorizing the address change.

Prepare your site

• 25 WordPress backup tools for different recovery needs (in French)
• Unmet WordPress requirements: checking PHP and MySQL or MariaDB (in French)
• WordPress migration, staging and imports: choosing the right tool (in French)
• Download the Multisite checking exercise