Most outages send a warning first. The server disk has been filling up for weeks, the web shop certificate is due to lapse late on a Friday, the UPS battery can no longer hold out for five minutes. On the day, it looks like bad luck, yet there was nearly always a signal nobody happened to be watching. Apply watches those signals remotely and prepares for what cannot be avoided: a backup that genuinely comes back, a second line, a tidy shutdown when the power goes and a plan your team knows how to follow. It all starts from one plain question: what does an hour of standstill cost your business?
The starting point is business impact, not technology. Once it is clear which application must never stop and which can wait until tomorrow, the rest of the budget explains itself.
A one-page table covering the clinic appointment book, the card terminal, the PrestaShop store, the ERP or email: how many hours of service can be lost (RTO) and how much data can be re-keyed by hand (RPO). The appointment book may not survive an hour; the historical archive could manage a week.
Disks reporting SMART errors, partitions at 90 %, SSL certificates and domains about to lapse, expiring licences, services that quietly restart every night. On Premium these alerts are handled at any hour; on Start and Business, within support hours.
The 3-2-1 rule plus an immutable copy on separate storage with its own credentials, which ransomware cannot wipe even after seizing the server. Retention is planned to cover mistakes found late, not merely yesterday's files.
A fallback connection from a different carrier, a replica in a Spanish or EU data centre for whatever cannot wait, and a UPS configured to power servers down in sequence. Swapping a disk or battery is done by your staff or a local technician, with Apply directing over video.
A share of outages is caused by a patch. So updates go to a small pilot group first, roll out in an agreed window, and there is always a snapshot beforehand to roll back to if the management software stops launching.
Who decides, which systems return first, which contacts to alert, how to keep serving customers on paper, and a prepared note for the website and social media. Written so management can follow it, not only a technician, and stored away from the servers too.
None of them is dramatic and all of them are foreseeable. Each has its own specific fix, and no single fix handles them all.
Fix: track the dates. The shop flashes a “not secure” warning in the middle of Black Friday and Redsys starts declining payments. A reminder thirty days ahead and a properly tested auto-renewal prevent it.
Fix: monitoring and a backup. Once the disk fills, the ERP database cannot write and invoicing halts. If the disk dies outright, the warranty or your staff handle the swap; Apply recovers the data and the system.
Fix: an immutable copy. Attackers go after backups first so they can encrypt them with everything else. A copy with separate credentials and its own second factor is what decides between recovering in hours and haggling over a ransom.
Fix: UPS, orderly shutdown and a 4G or 5G line. Roadworks on the industrial estate or a blackout like the one in April 2025 can leave the office dark for hours. What matters is that servers shut down cleanly and restart in the right sequence.
Fix: a prior snapshot and an agreed window. A PrestaShop module that stops working after an upgrade, or the gestoría software refusing to open after a Windows patch. With a snapshot in hand, reverting takes minutes.
Imagine a dental clinic in Seville that has run daily backups “for ever”. When the server fails, they find the job was copying the old folder of the practice software, not the one in use since the last migration, and that failure warnings went to a mailbox nobody opened any more. None of this shows in a green dashboard; it only surfaces during a test restore. That is why Apply restores for real, at the agreed frequency, and records how long it takes.
That figure covers the provider's infrastructure, not your data or your configuration. If someone deletes a folder, ransomware encrypts the virtual machine or an update breaks the application, the provider has kept its promise and you are still at a standstill. This is the shared responsibility model: backups, monitoring of your own service and the recovery plan remain yours to organise.
That a UPS buys minutes, not hours, and its real job is to switch servers off without harming databases. That when power returns there is a sequence: network and storage first, then servers, applications last. And that with no fibre and no landline, you need to know in advance how staff and customers will be told. All of that belongs in the recovery plan.
Your RTO sets the price. Recovering the same day is cheap; recovering within an hour requires a standby replica and more budget. Once the impact map is done, it usually turns out that only two or three applications need strong protection. The initial review and any one-off test restore are billed at €75 per hour + VAT; under a Start, Business or Premium plan, periodic tests are part of maintenance.
On Premium, alerts are dealt with at any hour and the response time is 15 minutes. On Start or Business, cover runs Monday to Friday, 9:00-18:00 Spanish time (CET), and weekends are added with the 24/7 IT support service. The engineer works remotely; if hardware needs touching, they guide someone on your team with the plan open in front of them.
Possibly. NIS2 and its transposition require continuity and incident management measures from the organisations in scope, and the ENS asks something similar of anyone working for the public sector. Whether your company is obliged is for your legal adviser to determine. Either way, the impact map, the test restore log and the written plan are exactly the evidence auditors and large customers request.
We review your backups and monitoring, carry out a real restore and tell you how long each critical application takes to return.
Your request is with us
Expect an answer within one working day. A reported fault that has halted your team is handled first.
No match found. Try another spelling, or go with the closest provincial capital: every job is done remotely, so the location makes no difference to what we deliver anywhere in Spain.
