VPS Hosting for CMS Adobe Commerce on SSD

Adobe Commerce is the paid version of an e-commerce platform on PHP, formerly known as Magento Commerce: it has features for complex catalogues, customer segments and corporate sales. With VPS hosting for Adobe Commerce from HIP-HOSTING the shop, the search engine and the queues get a dedicated virtual server instead of a shared plan. There is no image of this platform on the order form, and it is installed by hand with access keys issued by the vendor. The size of the server depends on the catalogue and the number of orders; if sales grow, you simply enlarge the plan.

Get VPS from $3/mo
12 locationsFull root access
VPS for Adobe Commerce
  • Standardfrom $3/mo
  • Memoryfrom $10/mo
  • Hi-CPUfrom $5/mo

VPS / VDS PLANS

Our VPS hosting plans for CMS Adobe Commerce

Choose a location and plan line. Prices shown per month.

Tokyo, JapanAvailable

1 vCPU1 GB RAM

  • 10 GB SSD
  • 200 Mbps

$3/ mo

Order VPS

2 vCPU2 GB RAM

  • 20 GB SSD
  • 200 Mbps

$4/ mo

Order VPS

2 vCPU4 GB RAM

  • 40 GB SSD
  • 200 Mbps

$6/ mo

Order VPS

4 vCPU8 GB RAM

  • 80 GB SSD
  • 200 Mbps

$12/ mo

Order VPS

6 vCPU12 GB RAM

  • 120 GB SSD
  • 200 Mbps

$18/ mo

Order VPS

8 vCPU16 GB RAM

  • 160 GB SSD
  • 200 Mbps

$24/ mo

Order VPS

8 vCPU24 GB RAM

  • 240 GB SSD
  • 200 Mbps

$32/ mo

Order VPS

8 vCPU32 GB RAM

  • 320 GB SSD
  • 200 Mbps

$48/ mo

Order VPS

12 vCPU48 GB RAM

  • 400 GB SSD
  • 200 Mbps

$64/ mo

Order VPS

16 vCPU64 GB RAM

  • 500 GB SSD
  • 200 Mbps

$96/ mo

Order VPS

FAQ

Frequently asked questions

Only the Hi-CPU line carries NVMe disks at HIP; look for it in Paris, Dronten or Helsinki. The disk works hardest during the reindexing of the catalogue and the build of static files after an update. A small shop at the trial stage is fine on the SSD plans, Standard and Memory.

IN DETAIL

Service description

Licence and keys

Before the installation the vendor issues a pair of keys for access to the package repository. They are written into the authorisation file of Composer, and it must be kept like a password: outside the repository and with closed rights. If a key falls into foreign hands, replace it in the personal account of the vendor.

Installation and modes

The shop is assembled with Composer, then the installation is run from the console. For a working site turn on the production mode, because in the developer mode pages are built on the fly and run noticeably slower. The command that switches to production mode compiles the code and the static files itself; if the compilation was skipped with a flag, run it by hand.

Search, cache and queues

The catalogue needs a search engine, and cache and sessions are better kept in Redis. Message queues are handled by background consumers: by default cron starts them, and under load they are kept as services. If they stand still, orders and letters get stuck although the storefront looks alive.

Scheduled tasks and indexes

The platform calculates prices, indexes and mailings on a schedule. Add a regular launch of scheduled tasks and the mode of indexing by schedule, so that heavy work does not run at the moment of checkout. Look now and then whether the queue is falling behind.

Extensions and copies

Every extension is a risk for updates and speed. Install them one by one and test on a copy. A backup is the database, the uploaded media and the settings files. Take them together, keep them off the server and check before a sale that the copy unpacks.

Speed

For a shop the cache of ready pages, the opcode cache of PHP and a fast disk matter. An NVMe VPS server with Adobe Commerce copes faster with reindexing and with the build after an update; how many visitors it serves at the peak depends on memory. Connect a content delivery network for pictures if buyers are far from the data centre.

Protecting the shop

The admin area of a shop attracts password guessing, so keep two-factor login on (it is on by default) and, if the team works from known places, allow entry only from their addresses. Close the ports of the database, the search and Redis from the internet, and leave the login to the server by SSH key. Install the security fixes of the vendor without long pauses: on a copy first, then on the live shop.

Mail and payments

Orders produce many letters, so hand their delivery to an external mail service and make sure the ports for it are open, since mail ports on new servers are often restricted. Payment modules need an HTTPS address reachable from outside, or the notices about payment will not return. Go through a whole order before the launch.

Logs and the disk

Logs, reports and cache grow faster than expected. Set up log rotation, clear out old reports and check free space monthly. In the panel the disk only grows and cannot be squeezed back, so leave room for the growth of the catalogue.

Who it suits

  • a company with a large catalogue and complex price rules;
  • a wholesaler that needs customer accounts and closed price lists;
  • an integrator that runs clients' shops on this platform;
  • a team that moves a shop from another server under its own control.

Choosing a plan

Settle the licence and the size of the catalogue before you buy Adobe Commerce VPS hosting. To rent Adobe Commerce VDS hosting is to take updates, copies and queues on yourself, with the versions and extensions entirely your choice. You can begin a VPS/VDS for Adobe Commerce with four cores and 8 GB; if the queue grows during the first sale, add resources in the panel. Cheap Adobe Commerce VPS hosting is the one where the order queue does not pile up at the peak, even if the price is not a record low.