yucod

Get your website and data back online in hours, not days

We set up automated backups and write a recovery plan: who does what, in what order, and how long it takes. You stop guessing where the last working copy lives.

Quote and schedule after your brief

Who it's for

  • Owners of online stores where every hour of downtime means lost orders
  • Businesses whose customers and deals live in a CRM
  • Companies with a website but no clear answer to who runs backups and where they are stored
  • Teams that switched vendors and aren't sure they hold every access credential

Problems we solve

We have backups, but nobody has ever tried restoring one

We automate the backups and run a restore on a separate test environment. A backup that has never been opened doesn't count.

The site went down and nobody knows who to call

We write a one- or two-page plan: contacts, step order, access list, who makes decisions. Someone can follow it at 3 a.m.

Backups sit on the same server as the site

We store copies in a separate cloud account that only you control. If the server is compromised or lost, the copies survive.

CRM data and form submissions aren't in any backup

We add the CRM, lead databases and automation settings to the plan, and set a backup frequency for each data source.

What's included

  • Inventory of what needs protecting: site, database, uploaded files, CRM, email, domain
  • Automated scheduled backups (daily or more often, depending on how fast your data changes)
  • Storage in a separate cloud account owned by you
  • Encryption and restricted access for the copies
  • Test restore: we bring a copy up on a separate environment and verify the site works
  • Agreement on two numbers: how much data you can afford to lose and how fast you must be back
  • Written incident plan with roles and contacts
  • Access register: domain, hosting, DNS, email, CRM
  • Uptime monitoring with alerts to your messenger or email
  • Short training for one person on your side to run a restore from the plan

Choose the scope

Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.

01

Basic

A small site or landing page where data rarely changes

  • Automated site and database backups
  • Separate storage in your account
  • One test restore
  • One-page recovery plan
Discuss this scope
02

Business

An online store or corporate site with a CRM

  • Backups of site, database, files and CRM
  • Several backups per day for the orders database
  • Test restore with measured recovery time
  • Full continuity plan
  • Monitoring with alerts
Discuss this scope
03

Ongoing care

Teams that want backups and the plan kept current

  • Monthly check that backups are running
  • Quarterly test restore
  • Plan updates after site changes
  • Incident response under an agreed schedule
Discuss this scope

How we work

01

Inventory

We list everything that must be protected and review what is already set up.

02

Recovery targets

Together we decide how much data you can lose and how long the site can be down.

03

Backup setup

We connect automated backups, separate storage and encryption, all under your own accounts.

04

Test restore

We bring a copy up on a separate environment, check the site and record how long it took.

05

Plan and handover

You receive the recovery plan and access register, and we walk one person on your side through them.

Scope and limits

  • We don't promise zero data loss. There is always a gap between two backups, and we agree its size with you upfront.
  • We don't guarantee outages won't happen. We shorten their impact; we don't remove their causes.
  • We can't recover data that was never backed up before we started, and we don't take on systems we have no access to.

FAQ

What is the difference between a backup and a continuity plan?

A backup is the files and database you can restore from. A continuity plan is the instruction: who does what, in which order, so the business keeps running. Without a plan, even a good backup can cost you extra hours of downtime.

How often should backups run?

It depends on how fast your data changes. A landing page is fine with one backup a day. A store taking orders needs several per day. We ask how many orders or leads you can afford to lose and set the schedule from that.

Where are the backups stored?

In a separate cloud account registered to you. We don't keep copies on our side. All accounts and files are yours under the agreed terms, so you can change vendors without losing access.

Do you work with sites you didn't build?

Yes, if we get access to hosting, the database and the domain. We start with a review and tell you what can and can't be protected. Payment is staged, so you see results before the next payment.

How much does it cost?

We prepare a quote after reviewing your brief and requirements. A first stage can cover: automated site and database backups; Separate storage in your account. Scope, payment and schedule are agreed before work starts.

Can we start with a small pilot?

Yes. The pilot: set up backups for one site and run one test restore. The measurable KPI is the time it takes to bring the site back from a copy. If you're happy with that, we extend coverage.

Start with your task

Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.

Start a project brief