Magento 2 hosting with administration, backups and monitoring

For companies running a Magento 2 store or preparing a new build that need a managed server environment. The offer covers a VPS, a dedicated server and AWS administration.

A managed VPS costs PLN 700 net a month and a dedicated server PLN 1,400 net a month. Both figures cover the server, its administration, daily backups and monitoring — there is no separate charge for the machine. Administration of an AWS environment starts at PLN 2,350 net a month, with the cost of the AWS resources used added on top. Full specifications of all three variants are in the pricing section.

A VPS uses dedicated resources on a virtual machine and usually suits smaller and mid-sized projects: a catalogue up to a few tens of thousands of products, traffic without sharp peaks, integrations running on a schedule. With a dedicated server the whole machine is given to one environment, which is why it is chosen by stores with heavier load, a large catalogue, heavy imports or several Magento instances. AWS is worth considering when the project needs services separated, scaling or a more complex architecture. We propose the variant after reviewing the current load, not from the product count alone.

Yes. Availability, load, disk space and service errors are checked automatically, around the clock, in every variant. The list of monitored parameters is agreed for the specific store.

Backups are taken daily and are included in the price of every variant. They cover the whole environment: database, files and configuration. Retention, where copies are stored, and the rules and time for a restore are confirmed in the offer and the contract — they depend on the variant and the size of the store, so we do not quote one figure for every project.

Yes. We prepare the new environment, move the store and support testing before the switch. The scope and the schedule depend on the size of the database and files, the integrations and the current infrastructure. That is how the server change went when we took over the Chrisanne Clover build, among others. Changing the e‑commerce platform to Magento is a separate service: migration to Magento 2.

Yes. That configuration is possible on a VPS or a dedicated server. The number of stores should not be the only criterion — traffic, catalogues, integrations and background processes all matter.

Not always. What Magento 2 needs above all is dedicated resources and control over the database, cache, search engine and cron — on shared hosting a production store will not run steadily. A dedicated VPS meets those conditions; a dedicated server becomes the right answer with heavier traffic, a large catalogue, heavy imports or several stores on one environment.

PHP, the database, the cache and the search engine take memory at the same time, so what counts is the total, not the application alone. For a production store we treat 16 GB as the floor — that is what our smallest VPS variant carries. With a large catalogue, multistore, extensive integrations and heavy imports we start at 64 GB, which is the dedicated server specification.

Hosting covers the infrastructure and server administration. Code fixes, modules, Magento updates, an application SLA and responding to store errors belong to Magento application maintenance.

Where the infrastructure sits, how data is stored and the scope of the safeguards are agreed before the service starts. Compliance follows from the contract, the infrastructure provider's documentation and the actual configuration — not from a claim on a web page.