Updates in staging
Core, themes, plugins and PHP are updated on a copy of the site first, key functions are checked and only then is the live site updated. Urgent security patches go in faster.
A website is not finished on launch day. Every month brings updates to the core, plugins and PHP; certificates expire; forms quietly stop sending email because someone changed a mailbox password. Suppose an accountancy firm in Ljubljana runs a WordPress site with online booking for consultations. Nobody has updated it for a year for fear of breaking something, and the fear is justified: updating after a year is risky. Regular maintenance means small steps, tested before they reach the live site, and someone who notices when something stops.
We maintain WordPress, WooCommerce, PrestaShop, Laravel and other systems. The scope is written into the agreement, so you know exactly what is included.
Core, themes, plugins and PHP are updated on a copy of the site first, key functions are checked and only then is the live site updated. Urgent security patches go in faster.
The site is checked every few minutes, SSL and domain expiry dates are watched and forms are tested for email delivery. When something stops, we hear before your customers do.
Daily backups of files and database, kept off the server in an EU data centre. Restores are tested on a schedule, because a backup nobody has restored cannot be trusted.
Reviews of plugin vulnerabilities, unused user accounts and admin rights. Unused plugins are removed, not just switched off.
A new page, an updated price list, a new job ad or a form fix. You send a request by email; we carry it out and confirm.
A short report on updates, availability, backups and changes made, plus suggestions for improvements worth considering.
Before maintenance begins we review the site. If it has gone without updates for a long time, the backlog comes first.
We obtain access, check the system, plugins, hosting and backups and list the risks. Ownership of all access stays with your company.
If the site has not been updated for a long time, we set up staging and bring it up to date step by step, fixing whatever breaks along the way.
Updates, monitoring, backups and small changes on the agreed rhythm. Requests come in by email and each one gets a reference number.
A monthly report and, once a year, a longer review of whether the site still meets your needs or a larger overhaul is due.
A backup stored on the same server is not a backup. When the server fails or an attacker encrypts it, the site and its copies vanish together. We therefore keep backups with a different provider or at least in a different data centre, and test a restore at least once a quarter.
Yes. We review the site first and tell you what state it is in. If it is badly out of date, we suggest clearing the backlog as a separate project, followed by regular care.
It depends on the system, the number of plugins and how many changes you expect. After the review you get a quote for a monthly scope. Work outside it is billed at €50 per hour plus VAT once you approve it.
During working hours, Monday to Friday 9:00-17:00 CET, we start on the problem as soon as we detect it or you report it. If you need cover outside those hours, we agree it in the contract.
Yes. Anyone you nominate can send requests, each gets a reference number and the history stays easy to follow, so nobody has to ask who ordered what.
Tell us the website address, the system it runs on and when it was last updated. We reply within one working day with a proposal for a review.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.