Monthly support of the online store
Monitoring, backups with recovery verification, platform updates and fixed response time. We start with a free technical inspection.
Website maintenance is work you don't see while it's being done: platform and PHP updates, backups that a site has actually been restored from, domain and certificate renewals, downtime alerts that reach you before a customer calls. Which of these you need depends on what you have. A site without a store needs technical support: forms, updates, backups. A store that takes orders every day needs monthly maintenance with checks of the cart, payments and shipping labels. If you run your own server, VPS or dedicated, there is separate server administration. Not sure which of the three fits you? Start with a free technical health check, and the answer will be clear after it.
Products, platform updates, browsers and search requirements keep changing, so a site needs steady attention.
We monitor availability and errors, update components and take on the tasks you send us.
Every change is logged, and the access and code stay with you, so the state of the site is always clear.
The scope of maintenance depends on the site and how often it changes. We agree on the format after reviewing your situation.
Monitoring, backups with recovery verification, platform updates and fixed response time. We start with a free technical inspection.
System updates, disk space, SSL certificates, caching, backup checks and predictable rollouts with a way back. We start with a free review of your server.
Platform updates, backups with restore verification, availability monitoring and form checks. Starts with a free technical check.
A corporate website, a services page, a landing page. There is no cart to crash, so a broken form looks like silence: no inquiries come in, and people look for the cause in the ads. What this needs is regular care: updates, backups and test submissions of the forms.
We'll review your situation in a free auditEvery hour of downtime means orders that won't happen, and a payment failure or a stock sync that breaks overnight is only noticed by the quiet morning order queue. This calls for monthly store maintenance: beyond the platform, we check checkout, payment confirmations, shipping labels and the product feed.
A VPS or dedicated server gives you freedom but takes all the work off the hosting provider: disk space, OS and database updates, log rotation, access left behind by former contractors. Separate server administration covers this.
The developer is gone, access is scattered, and nobody remembers what was changed in the core. First comes an inventory of access and transferring the domain and hosting to you, then the usual regular cycle.
We find out what you have: a website or a store, shared hosting or your own server, who has looked after it so far and what access has survived. The answers determine which of the three services you need.
We review the platform, module and PHP versions, free disk space, domain and certificate expiry dates, whether backups exist, and the error logs. You get a description of the site's condition, a list of risks and a recommended maintenance format.
If nobody has looked after the site for a long time, we first close the gaps: outdated versions, a full disk, backups that won't restore, access held by former contractors. The scope and timeline of this stage are fixed in the contract after the check.
Updates in an agreed window, backup checks, monitoring and tracking of renewal dates. For a store we add checks of checkout, payments and data exports; for a server, disk, logs and access.
A report on what was done and what was found. Anything outside the scope of maintenance gets a separate estimate, and you decide whether and when to do it.
Scheduled care of the server and the platform: OS and PHP updates, free disk space, domain and certificate renewals, backups with restore testing, error logs and uptime monitoring. Plus outage response within an agreed time. Adding products, copywriting and building new features are not included; those are separate jobs. If nobody has looked after the server for a long time, the first stage goes to clearing the backlog, and the regular cycle starts after that.
Yes, this is a common situation. We start with a technical check: platform and module versions, server condition, where the backups are and whether anyone has restored from them, what access exists at all and whose name it is in. If the domain or hosting is registered to a former contractor, our first step is to get them transferred to you. Changes previous developers made to the platform core go on a separate list, because those are what most often break during updates.
The things that cost money the moment they break: whether the catalog and product pages open, whether the cart and checkout work, whether payment confirmations arrive, whether shipping labels are created, whether prices and stock levels were updated from the import. Some checks are automated and send alerts; others we run by hand after updates. The point is to learn about a failure before a customer does: an order that failed overnight looks like a slow day in the reports, not like an outage.
In focus. On a site without a store, what matters most is forms and availability: the site has to open, stay updated and deliver inquiries. In a store, money is at stake every day, so there are more checks. The scope of checks is different, and so is the contract. If the store runs on its own server, server administration is added to maintenance.
In most cases, no. On shared hosting the provider takes care of the system, updates and disk, and a separate administrator can change little there. Server administration is needed when you have a VPS or a dedicated server: then the OS, database and PHP versions, disk space and access are the responsibility of whoever runs that server, not the hosting provider. If you are not sure what you have, the free check will show it.
There is no public price, because work with the same name can differ several times over: a site on a current platform version with working backups and a store on an unsupported PHP version where nobody has tested the backups are different scopes. After the free check we name the amount, listing backlog cleanup separately if it is needed, and fix it in the contract.
For new projects we register the domain, hosting and server in your name from day one. If something is registered to a former contractor, our first step is to transfer it to you. At the end of the engagement we hand over a description: what is where, where the backups are and how to restore them. We remove our own access when the work ends and let you know.
Describe the task in your own words — we will tell you where to start and whether you need what you came for. If you do not, we will say so.