Nexcess

Nexcess is the managed application platform now presented within Liquid Web. The former nexcess.net homepage redirects to Liquid Web’s managed-hosting catalogue, and the current application page explicitly identifies Nexcess as the underlying platform. This profile retains the familiar Nexcess name while linking to the current official offering.

Key features

• Managed applications. The current catalogue covers WordPress and commerce-related hosting, including Magento.
• Platform management. Hosting is packaged around supported applications rather than an unmanaged virtual machine.
• Delivery layer. Liquid Web describes an Edge CDN powered by Cloudflare, with additional enterprise features sold separately.
• Growth options. Scaling capabilities depend on the product and tier; some allowances are specifically limited to higher plans.

Who it is for

Businesses and agencies operating WordPress sites or commerce applications that want application-focused hosting. Existing Nexcess customers and new buyers should use current Liquid Web documentation to identify the product and support arrangement.

Pricing at a glance

Managed application plans use recurring charges, with prices and included capacity determined by the current Liquid Web product. Earlier Nexcess promotions may no longer apply. Confirm application, tier and renewal terms with the official plan page.

Pricing model checked on 15 October 2026; confirm current terms on the official product page. No currency conversion or fixed price estimate is used in this profile.

Things to consider

• The brand and website have changed; old Nexcess tutorials and price tables may be outdated.
• WordPress, WooCommerce and Magento requirements should be checked against the exact current product.
• Included CDN features and paid enterprise additions are not interchangeable.

Before moving a production workload, record its runtime versions, storage needs, database size and external services. Decide who will own updates and incident response. A small pilot is a better way to establish compatibility than relying on a headline feature list; include a restore exercise and check that the team can retrieve its data independently.

Getting started

1. Read the official documentation and plan information, then write down the features and costs your project needs.
2. Choose a small test environment that matches the application’s runtime and persistent-data requirements.
3. Configure restricted access, domain settings and certificates; keep secrets out of source repositories.
4. Test deployment, backups and restoration with representative data before changing production DNS.
5. Review usage and recurring charges after the pilot, and document a migration or cancellation path.