Skip to main content

Cmsmart services

Hosting and DevOps for Cmsmart Ecommerce and WooCommerce stores

A staging copy, a deployment you can undo, backups that are restored in a test, and an alert that reaches a named person.

Quoted per project, no obligation. The assessment is free and carries no price list.

In short

What does a reliable hosting and deployment setup look like for a WooCommerce store?

A reliable setup has separate staging and live copies, deployments you can roll back, backups that are restored in a test, monitoring that alerts a named person, and server settings that suit your traffic and your designer. Cmsmart sets this up on your hosting or on a Cmsmart server, after a free assessment, and quotes it per project.

Key facts: Hosting and DevOps
ScopeEnvironments, deployment, backups, monitoring, server settings and access for one store or a small group of stores
What you getChanges tested on staging before live, a way back after a bad release, and an alert when checkout or the site fails
Typical inputsHosting access, how the store is deployed today, your busiest days and who makes changes
DeliverablesAn environment map, configured staging and live, a deployment routine with rollback, a recorded restore test, alerts and a run book
How pricing worksFree assessment, then a quote per project. Annual Fullstore, B2B and Marketplace plans include 3 months of hosting for one store; see the pricing page.

How it works

From a change to a monitored live store

From a change to a monitored live storeA change is tried on a copy first and goes live by a routine that can be reversed. Monitoring watches the journeys that make money, and backups count only once a restore has worked.Staging copy1Test2Deploy to live3Monitor andalert4Back up andtest a restore5From a change to a monitored live storeA change is tried on a copy first and goes live by a routine that can be reversed. Monitoring watches the journeys that make money, and backups count only once a restore has worked.Staging copy1Test2Deploy to live3Monitor and alert4Back up and test a restore5
From a change to a monitored live store. A change is tried on a copy first and goes live by a routine that can be reversed. Monitoring watches the journeys that make money, and backups count only once a restore has worked.

The problem

What does a store without a deployment routine risk?

  • Changes made straight on the live store
  • Backups that were never restored
  • A sale or a campaign that slows the store
  • Nobody alerted when checkout stops working
  • Credentials shared in chat, or held in a former developer's account

Fit

Is this the right service?

A good fitAnother route fits better
You release changes often and want them tested before they reach customersThe store is stable and you only need someone to apply updates: a care plan covers that
Your designer, uploads or print files need server settings you have not checkedYou want a new store built: that is a setup or build service
You are unsure where backups live or whether they restoreYou need round-the-clock on-call cover: that is agreed separately, not part of this setup

What we do

What is in scope?

PartInputDeliverable
Environments Live and staging, and a development copy if you need one Separate copies with a documented way to refresh staging from live
Deployment Code, plugin and theme changes A repeatable routine with a rollback path
Backups Files and database Scheduled backups and a recorded restore test
Monitoring Uptime, the checkout journey and errors Alerts to a named owner
Server settings PHP version, memory, caching, scheduled tasks and the image library Settings that suit the store and the designer, written down
Access and secrets Admin users, SFTP or SSH and keys Accounts with only the rights each person needs, and credentials kept out of chat

The Cmsmart angle

What the Cmsmart designer needs from the server

These requirements come from the plugin's own documentation. They are the usual reason a designer works on one host and not on another.

Core Plugin requirements we configure for

  • Versions. Cmsmart Product Designer requires WordPress 5.6 or later, WooCommerce 8.0 or later and PHP 8.0 or later.
  • CMYK output. A CMYK JPG with an ICC profile needs ImageMagick with lcms2 on the server.
  • Large option sets. A very large option set can reach the PHP max_input_vars limit. The editor warns, and the hosting value can be raised.
  • Background jobs. Print-ready PDFs and sample imports run in the background, so scheduled tasks must run reliably.

Custom Built as custom development

  • A deployment pipeline for your own theme and plugins
  • Monitoring of the checkout journey and of the print-file queue
  • Moving the store to new hosting with a tested cut-over
  • Tuning for a known traffic peak

Current requirements

What WordPress and WooCommerce ask of a host

WordPress recommends hosts that support PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, and HTTPS. WooCommerce lists PHP 8.3 or greater, HTTPS and a WordPress memory limit of 256 MB or greater. The plugin's own minimum is lower than what the platforms now recommend, so the assessment checks your host against both.

Source: WordPress requirements, WooCommerce server requirements (read 10 October 2026).

Cmsmart hosting

Hosting on a Cmsmart server

Annual Fullstore, B2B and Marketplace plans include 3 months of hosting for one store on a Cmsmart company VPS, with 20 GB of disk and weekly backups. After that we quote hosting for your store, or you move it to your own hosting. The pricing page has the current plan details.

Scope

Included, not included, and extra

Clear lines before you start. The final scope is written into your proposal.

Included

  • An environment map and a gap list
  • A staging copy and a documented way to refresh it
  • A deployment routine with a rollback path
  • Scheduled backups and one recorded restore test
  • Monitoring that sends alerts to a named owner
  • Server settings written down, with a run book

Not included

  • Round-the-clock on-call cover. Operations cover is agreed separately.
  • Hosting fees from your own provider
  • Building or redesigning the store
  • Hosting for AI model workloads, which is outside this service
  • Licences, hosting and third-party fees (plugins, fonts, images, services, provider accounts)
  • Anything that is not written in the approved scope

Extra, quoted separately

  • Moving the store to new hosting
  • A care plan after the setup
  • Speed work on the store's own code

What we need from you

  • Hosting access, or approval to use a Cmsmart server
  • How changes are made and deployed today
  • Your busiest days and any expected traffic peak
  • The name of the person who receives alerts
  • A staging copy of your store, or approval to create one
  • Someone on your side who can make decisions when a question comes up

Process

How the work runs

Each phase is a milestone, approved and invoiced one at a time. The timeline is set in the assessment because it depends on your store, your products and your systems.

  1. Free assessment. We read your brief, your store and your constraints, and tell you whether the service fits and what it would involve.
  2. Written scope and quote. Included, not included, extra and what we need from you, set out before any work starts.
  3. Build on a staging copy, in milestones you approve one at a time in your dashboard.
  4. Acceptance with your own products, files and orders, including the awkward ones.
  5. Handover with a run book, then support through tickets in your dashboard.

This service in three phases

What happens, and what you receive

PhaseWhat happensWhat you receive
1. Assess We map how the store is hosted, deployed and backed up today, and what has gone wrong before. A written environment map and a gap list
2. Set up We build the staging copy, the deployment routine, the backups and the alerts. A working setup on your hosting or ours
3. Prove and hand over We deploy a change end to end, restore a backup, and trigger an alert on purpose. A recorded test of each, and a run book

Free assessment

Start with a free assessment

Describe your store and what you need. We reply with whether the service fits, what it would involve and a quote, with no obligation.

FAQ

Frequently asked questions

Can you set this up on our own hosting?

Yes, if the host gives the access the setup needs. The assessment checks that first and says if the host is the limit.

Do you provide hosting?

Annual Fullstore, B2B and Marketplace plans include 3 months of hosting for one store on a Cmsmart company VPS. After that hosting is quoted, or you move to your own.

Does the setup include 24-hour monitoring?

It includes monitoring that alerts a named person. Staffed round-the-clock cover is a separate agreement.

Why test a restore?

A backup you have never restored is an assumption. The setup includes one recorded restore, so you know the copy works and roughly how long recovery takes.

Will it change how my team works?

Changes go to staging first and reach live by the routine we set up. Your team keeps managing products and orders in wp-admin as before.

Who you work with

The team behind Cmsmart and its published work

  • 2012Netbase since 2012Cmsmart Ecommerce is a Netbase JSC company
  • 6,300+client projectssince 2012
  • 80+countriesclients worldwide
  • 17,133proposals writtenin our project system, live count

Client projects and countries: Netbase portfolio library and WorkSuite project records, as of Sep 2026. Proposals: records in our Cloodo WorkSuite project system, all-time, refreshed every 6 hours.

Stores on Cmsmart Ecommerce

  • Customer logo: clickprint.lk
  • Customer logo: storyblockplus.com
  • Customer logo: privatwelt24.de
  • Customer logo: 3dparati.es
  • Customer logo: centropromo.it
  • Customer logo: expressedinprints.com
  • Customer logo: lynxdigiprint.nl
  • Customer logo: rynoprinting.com
Hosting and DevOpsFree assessment

Top