WP Hosting / Network Dynamics: WordPress in Australia, Prices and Limits

Who WP Hosting (Network Dynamics) 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

English on the pages reviewed.

Control panel

cPanel and WordPress Management documented in English; actually enabled language not tested.

Support

Australian team advertised 24/7, channels and documentation in English; French not established.

WP Hosting now forms part of Network Dynamics

Presentation image from Network Dynamics, the current brand of WP Hosting. General banner, without evidence of performance or a tested plan.

WP Hosting remains a useful name for finding Australian WordPress hosting, but the current commercial experience bears the Network Dynamics brand. The official January 2, 2026 announcement presents this as internal consolidation: WP Hosting already belonged to the group. The provider specifies that it is not a sale, that teams and infrastructure continue, and that existing customers need not migrate sites or change passwords for this reason alone.

This profile examines WordPress plans currently displayed through the WP Hosting domain, consulted on November 3, 2026. It does not turn old packages into automatic equivalents of the new catalogue. A long-standing customer should compare the service name, invoice and specific terms with the current table. In a comparison, WP Hosting and Network Dynamics should be grouped to avoid counting the same organization twice.

The listed operator is Network Dynamics Pty Ltd, with an address in Kew East, Victoria. The offering clearly targets Australian businesses. A local business address identifies the operator without itself establishing the storage city of each site or all its backups.

Three packages with distinct site and storage quotas

WordPress Startup is displayed at 19 Australian dollars per month. It includes one site, 5 GB NVMe storage and three POP/IMAP mailboxes. WordPress Business rises to 29 AUD per month for up to two sites, 10 GB and ten mailboxes. WordPress Business+ reaches 49 AUD per month for up to five sites, 20 GB and twenty mailboxes. These amounts are advertised as including GST. Capacities belong to the package; the table does not promise that much storage for each site. Also clarify the space used by a staging copy and how it counts against installation limits before sizing several projects.

All three cards advertise LiteSpeed, multiple PHP versions, SSL certificates, daily backups, free incoming migration and unmetered bandwidth. The latter does not mean infinite computing capacity. The usage policy prohibits resource consumption that disrupts other customers. Core counts, RAM, PHP processes and input/output thresholds are not quantified in the reviewed table.

For a small brochure site, Startup provides a clear allowance. For two projects, Business may avoid two subscriptions if their combined volume remains suitable. Business+ mainly raises visible quotas. None of these figures establishes concurrent visitors supported by a store or turns permitted sites into a performance guarantee.

Initial, annual and renewal pricing without a separate introductory discount

The current page distinguishes monthly from annual payment. Monthly service is billed at the displayed rate without a long commitment advertised. Annual payment means paying for ten months and receiving twelve, with two free months each year. Applied to monthly amounts, this gives 190 AUD for Startup, 290 AUD for Business and 490 AUD for Business+, including GST. These are calculations from the public rule, not invoices from a completed order.

The official pricing post of July 17, 2026 explains a return to identical prices for new and existing customers of the same service and a recurring annual reduction. No first-year reduction followed by a different renewal price was recorded in the current offering. This describes present policy; it is not a contractual price freeze for all future years.

The terms provide for advance payment. Annual invoices are issued thirty days before the due date, monthly invoices seven days before. Check the period, options, any setup fees and currency actually charged in the summary. Public access to order configuration did not allow validation of a final total here. For a French company, precise tax treatment and any exchange fees remain to be established; no euro amount is simulated. General terms require an age of at least eighteen and accurate information but do not themselves validate admission of a French application. Confirm accepted billing country and applied tax before paying.

The fifteen-day guarantee has a decisive exclusion

The billing policy dated February 13, 2026 allows a refund within fifteen days of an initial order or annual renewal. It excludes domains, options, certain licences and special configurations, among other items. It also excludes services that used free migration. The commercial guarantee banner is therefore insufficient for a business specifically intending to entrust its move to the provider.

Outside the eligible window, the provider offers no proportional refund for unused time. Annual payment reduces the displayed cost but commits a larger amount. For an uncertain project, comparing the monthly total of a short evaluation with the annual total is more useful than looking only at a monthly equivalent. Migration scope and refund eligibility must be clarified before activation.

Nonpayment also has practical consequences: the policy announces suspension after seven overdue days, then termination after fifteen days with active-data deletion. It mentions offline copies that may sometimes allow recovery for up to ninety days for the 99 dollars stated in the policy, potentially plus outstanding payments. Taxes on this intervention must be confirmed, and data integrity or completeness is not guaranteed. This possible paid recovery never replaces an export retained before cancellation.

Managed WordPress without a promise of universal compatibility

The provider advertises WordPress installation, staging, core/theme/plugin update management and control over automatic or approval-based updates. The knowledge base describes WordPress Management, formerly WordPress Toolkit, in cPanel. Users therefore have WordPress-oriented management while retaining a broader hosting environment for files, databases and email.

Guides specify that some commercial plugins may require manual updates or their own licence. The package does not prove that a theme purchased elsewhere, builder subscription or payment plugin is provided. Before transfer, inventory required PHP versions, scheduled tasks, cache rules, licences and external services to distinguish platform maintenance from maintenance of the entire application.

The page promises compatibility with Cloudflare and CDNs. It does not establish an included paid CDN licence. Scores and loading times illustrated in the commercial presentation are not measurements made on the reader’s site. No load, migration or installation test was performed for this profile; actual cache benefits remain to be checked on a representative workflow, especially cart, customer account and payment.

Staging: advertised, but Startup access still needs confirmation

All three commercial cards display a free staging environment. Yet the official WordPress Management cloning guide states that advanced features are available from Business and that a Startup customer may need to upgrade. This contradiction prevents claiming that the cPanel clone button is usable with every new Startup subscription. It may reflect a distinct recent workflow or outdated documentation; no account was opened to resolve it.

For a team wanting to try an update without touching production, the documented process therefore suits Business or above where WordPress Management is actually accessible. It requires cPanel access, a distinct empty destination and enough room for a second copy. Before creation, arrange with the maintainer to block sending, payments and synchronization from first startup; if this cannot be controlled, have support arrange the clone. First create an independent backup, then open WordPress Management in the sidebar, expand the site and choose Clone.

Under Target, select Create subdomain or Use existing domain. In the latter case, the domain must already be added to the service. Check the path field after the slash: leaving it empty puts the copy at the selected domain’s root. Do this only if the root is dedicated to testing and empty; a distinct address may still point to files already in use. Keep the proposed database name unless a validated need requires otherwise, without reusing production’s database. Click Start after checking the destination. The expected result is a copy at another address without changing the original site’s public address.

Check a copy before returning anything to production

A WordPress copy can retain the same API keys, SMTP connections, scheduled tasks and payment settings as the public site. Before working on it, check that the prepared isolation works: messages to real customers blocked, external synchronization disabled and payments in test mode. Restrict access to the relevant people; asking search engines not to index it is not access control. This preparation belongs to the site owner.

Then check important pages, administrator login, forms, cart and media. Successful cloning does not prove that purchasing works. For an active store, copying the entire test database to production could erase orders placed since that copy was created. The cloning guide reviewed is insufficient to validate selective table deployment: prepare this separately instead of reflexively using full replacement.

If the trial fails, discard the test copy and retain production as the reference. If work on the public site is actually necessary, take a new backup immediately beforehand, plan the necessary write pause and check the result afterward. Rollback rests on this recent state rather than an old copy unaware of the latest registrations or transactions.

Daily backups: distinguish retention from a personal copy

The WordPress page advertises a complete daily site backup and thirty days of history. Business+ mentions extended retention without a specific duration in the reviewed table. Preserve that lack of precision: the commercial wording does not justify adding sixty or ninety days to the package. Exact backup location, independence and data-return times are not established by this page alone.

The JetBackup 5 guide provides a usable process for the relevant cPanel services. In cPanel, open Files, then JetBackup 5. Choose Create Backup on Demand, confirm with OK and consult Queue until completion with a green check mark. This prepares a backup before an intervention if the feature is available on the service. A pending task must not be treated as a completed copy.

To retain data elsewhere, open Home Directory for files, select a date and Change File Selection, then the actual site folder. The default folder is public_html, but an additional domain may use another root. After Select Files, choose Download, then Download Selected Items. Once preparation finishes in Queue, the download icon leads to archives. Repeat under Databases for the affected database. Check archives locally and keep files and database from the same period together.

Restore a file or database with JetBackup 5

This second process is for an administrator with cPanel access who knows what must be restored. Start by preserving the current state. To fix an incorrectly edited file, open Files, JetBackup 5, then Home Directory. Choose a backup predating the incident, click Change File Selection and browse the site’s exact root. Select only affected files, confirm Select Files, then Restore and Restore Selected Items.

Follow progress in Queue. Wait for completed status before reloading the site or starting another restoration. Then check the original error, administrator access and features using the modified file. Restoring a single file may suffice after a bad edit, avoiding unnecessary replacement of recent content in a healthy database. The guide uses wp-config.php as an example without requiring that file to be replaced for every incident.

For database restoration, choose Databases and identify the correct database. The provider highlights the risk of losing transactions on commerce sites. Pause writes for the necessary period and preserve more recent data before acting. If the result is unsatisfactory, restore the copy taken immediately before the operation. These steps describe official documentation; no restoration was performed as part of this research.

Incoming migration and access: organize a verifiable transfer

The migration policy normally limits the free service to one migration per account on an eligible package unless otherwise agreed. It covers files, databases and mailboxes where applicable. Special configurations, custom scripts and moves between two Network Dynamics services are not automatically included. The advertised usual timeframe is two to three working days; complexity or incomplete access may extend it.

Before requesting migration, retain an independent export, record DNS, email settings and licences, then specify what must move. Provide only required access through the provider’s appropriate channel, using temporary credentials where possible. The policy requires the customer to test the site after transfer. The commercial announcement of migration without interruption remains the provider’s promise rather than a result observed here.

Checks should cover the destination site, HTTPS links, forms and incoming/outgoing email before deleting old hosting. If the new service is unsuitable, retaining the old instance and exports enables planning a return. After acceptance, revoke unnecessary access. The customer portal, cPanel, WordPress and main account mailbox have different roles: losing one access should not mean losing every recovery method.

Languages, assistance and the actual scope of promised availability

The pages, guides and screenshots consulted are in English. The provider advertises an Australian team reachable at all times; the contact page lists phone 1300 974 678, tickets and chat. French support is not demonstrated. A manager located in France should also check how to call this type of Australian number and how follow-up works rather than assuming all channels have identical terms from abroad.

The SLA specifies response targets of one hour for critical incidents, four hours for priority requests and twenty-four hours for general inquiries. These are published targets, not observed times or a guarantee of resolution within that period. A useful request contains the domain, problem time, preceding action and exact error without copying passwords or customer data.

The advertised contractual minimum WordPress availability is 99.9% per month, with numerous exclusions, including WordPress application errors and theme or plugin problems. Any credits must be requested within thirty days; they are not compensation for lost revenue. A statement that infrastructure is designed for higher availability does not replace this contractual threshold.

Artificial intelligence and limits of included management

No included AI assistant, generation quota or model credit is established in the reviewed WordPress packages. The group separately sells hosting for code produced by AI tools and other technical services. Their presence in the menu does not include them in Startup, Business or Business+.

For a project already using an AI plugin, separately check its licence, model provider, keys, billing and transmitted data. Hosting the site and accessing the model are potentially separate purchases. No AI call, content generation or key test was performed for this profile.

Advertised protections, updates and backups provide useful tools but do not remove the need to manage administrator accounts, abandoned plugins and payment permissions. A team wanting development assistance must obtain that service’s scope; hosting maintenance does not establish that a theme change or business integration is included.

Prepare departure and choose based on remaining unknowns

Cancellation is performed for each active service in the customer area before the next billing cycle. Stopping a recurring payment is not sufficient evidence of service closure. First download files and database, separately back up necessary email and retain DNS information. Domain transfer, mailboxes and hosting are distinct operations; confirm which should continue.

At the destination, restore the copy, check PHP and database, recreate scheduled tasks and test the site before changing DNS. Plan a final transfer of new data if the old site remains active during preparation. Retaining the old service for a short verification period makes rollback easier, subject to its next due date and the terms without proportional refunds.

WP Hosting, now Network Dynamics, may suit a small business serving Australia, working in English and valuing clear recurring annual pricing. Before choosing, actual Startup staging access, computing thresholds, specific Business+ retention, storage locations and case-specific tax treatment remain to be confirmed. The inspected official visual is a Network Dynamics brand banner: it identifies the provider without proving a private interface or measured performance.