Book a consultationBook

Safe data and a fast return to work after an outage.

The copy is made automatically on an appliance at your office. We keep a second, encrypted copy in Poland. After an outage we restore a file or a system on site. If the whole site is lost, we restore from the copy we hold.

  • A copy at your office
  • A second copy in Poland
  • Immutable copies
  • Monitoring and tests

Normal operations

Copy on siteThe server writes a copy to the appliance at your office.
Copy in PolandThe appliance sends an encrypted copy to us.
Server failureThe server is down. The office and the copy on site remain.
Restore from the local copyWe restore a file or a system from the appliance at the office.
Failure across the officeThe server and the appliance at the office are unavailable.
Restore from our copyWe restore the systems onto the server from the copy in Poland.
  1. ServerThe systems you work in
  2. Appliance at the officeCopy on site
  3. Copy with usIn Poland, away from the office

Different causes of an outage, two places with a copy

Not every incident can be predicted. What can be set in advance is how often a copy is made, how long we keep it, and where we restore the data from.

  1. 01

    AI-assisted attack

    Automation speeds up phishing and ransomware. An immutable copy has its own credentials, so a taken-over server does not wipe the backup history. A second copy sits off site.

  2. 02

    Server or link failure

    When the server is down and the office is still standing, a file or a system comes back from the appliance on site. The whole copy does not have to be pulled in from outside.

  3. 03

    Fire, theft, or flood

    One building can take out the server and the local copy together. The encrypted copy we keep in Poland remains.

  4. 04

    Human or update error

    A deleted file, a bad configuration, or a faulty update. We go back to an earlier version on the NAS. A test shows whether the restore really works.

Packages

Three scopes. The price comes after a conversation. Restoring data carries no extra fee.

  • Backup

    A managed copy and data restore.

    For a company that wants an automatic copy on site and a second one off site.

    • Automatic copy on site
    • Encrypted copy in Poland
    • Immutable copy
    • File and system restore
    • Monitoring and a test on request
    Book a consultation
  • A faster return to work

    Continuity

    Plus starting a system from the copy.

    For a company that, after a server failure, wants to return faster than a full restore onto new hardware.

    • Everything in Backup
    • Start the copy as a machine
    • Shorter time back to work
    • Restore test included
    Book a consultation
  • Compliance

    Longer retention, an audit, and more frequent tests.

    For a company in a regulated industry or with a longer retention period.

    • Everything in Continuity
    • An audit to start
    • Longer retention
    • More frequent tests with a report
    Book a consultation

Full comparison

GDPR and regulation

Compliance depends on where the data is stored and how we can prove it.

GDPR
The off-site copy is in Poland. The data processing agreement names the data centre. Client repositories are isolated.
NIS2 and KSC
New cybersecurity rules do not cover every company. In the audit we check whether they apply to yours and what they mean for your copies.
Proof
A restore test report, not a chart with an uptime percentage.

How we work

Four steps, always in this order. We deploy nothing until we know what we protect and what downtime costs.

  1. AuditWhat is critical, how much data there is, and what an hour of downtime costs.
  2. DesignRPO (how much data you can lose), RTO (how fast you are back at work), retention, and which systems are in scope.
  3. DeploymentAn appliance on site, a copy of changes, an encrypted copy in Poland, and monitoring.
  4. TestWe restore a file or start a machine and hand over a report with the result.

What you get

After every test you get a report, and the restore procedure is written down step by step. Below is an example with fictional data.

Example · fictional data

Restore test report

Test date
14.03.2026
Scope
ERP, file server, email
Target RTO
4 h
Measured recovery time
3 h 12 min
SystemRestore time
ERP— No issues1 h 05 min
File server— No issues48 min
Email— With notes1 h 19 min

Result: passed with notes

To fix

  • The appliance at the office is low on free space. Disks need adding before the next test.
  • The database password was not in the password vault. It delayed the email restore by 20 minutes.
Example · fictional data

Restore procedure, excerpt

  1. 01

    IT manager

    Confirms whether a file, a server, or the whole site is down.

  2. 02

    alpha backup

    Restores a file or a system from the appliance on site. ERP first.

  3. 03

    alpha backup

    If the appliance is down too, restores from the copy in Poland.

  4. 04

    IT manager

    Notifies teams using the contact list.

  5. 05

    Both sides

    After the repair, agree the return to the production server.

What does an hour of downtime cost you?

Enter the number of servers, hours of downtime per year, and the cost of one hour. The calculator shows the yearly cost of downtime and the package that fits. It is a guide for the conversation, not a quote.

Calculate downtime cost

Questions

Short answers. We cover the details at the consultation.

How is this different from full DRaaS?

It is a managed copy and a restore: an appliance at your office, an encrypted copy in Poland, and recovery of a file or a system. We do not keep always-on copies of every machine. Continuous replication and automatic failover can be added later.

Where are the copies physically stored?

One is on the appliance at your office. The second, encrypted, is with us in Poland, away from that site. We name the data centre in the design.

Can ransomware encrypt the copy too?

An immutable copy cannot be overwritten or deleted before the retention period ends. The copy has its own credentials, separate from the production server. There is also a second copy off site.

How often is a copy made, and how long do you keep it?

After the first full copy we send mainly the changes, so the job can run often, for example every hour or every 15 minutes. Retention is set per client. An example: 30 days on site, 90 days off site, and monthly points for a year.

How often do you test recovery?

A message that the backup succeeded is not enough. We check a file restore, a machine start, and copy integrity. On request in Backup, included in Continuity, and more often, with a report, in Compliance.

Is the calculator result a quote?

No. The calculator estimates downtime cost from your rate and points to a package. We prepare a quote after a consultation.

Let's talk about what you have today.

An hour's conversation: what is critical, where the copies are, and how long getting back to work takes. No blind quote, no obligation.

Book a consultation