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 400 net a month for the first 3 months, then PLN 600 net. A dedicated server — PLN 750 net a month for the first 3 months, then PLN 1,300 net. Administration of an AWS environment starts at PLN 2,150 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. It can be enough for smaller and mid-sized stores. With a dedicated server the whole machine is given to your environment, which is why that variant is more often chosen by stores with heavier load, a bigger catalogue or several Magento instances.

Yes. Administering the environment is part of the packages. The exact scope depends on the variant and is described in the offer and the contract.

Infrastructure monitoring runs without a break in every variant — availability, load, disk space and service errors are checked automatically, whatever the hour. The list of monitored parameters and the hours in which the team responds to an alert are confirmed in the contract. Monitoring and an SLA for the Magento application itself — store errors, broken modules, time to fix — are covered by AURORA CARE.

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.

A VPS usually fits 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. A dedicated server is the right choice with heavier load, a large catalogue, heavy imports, extensive integrations or several stores on one environment. AWS is worth considering when a project needs services separated, resources scaled or a more complex architecture. We make the call after reviewing the current load, not from the number of products alone.

Not always. What Magento 2 needs above all is dedicated resources and an environment configured for the application — on shared hosting, with no control over the database, cache, search engine and cron, 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.