Managed service

The outages that cost the most are avoidable

A website rarely goes down because of a server. It goes down because a domain was not renewed, a certificate expired, or a backup stopped running months ago. Three predictable causes — provided somebody answers for them.

  • Renewals tracked ahead of the deadline
  • Daily backups, restoration verified
  • We know the site is down before your clients do
Backupsdaily
Deadlines tracked, never missed
Restoration tested, not assumed
Availability monitored continuously
What is included

What the word "managed" actually covers

Hosting bought online sells you disk space. Everything that comes after stays your problem — and that is exactly the part we take.

dns

Setup

Sized for your real traffic, installed and put online. Neither under-specified nor billed for resources you will never use.

link

Domain name

Bought or transferred, and above all renewal tracked: an expired domain takes down the site AND the email, often the same morning.

lock

No warning to your visitors

The certificate is renewed before expiry, so browsers never show an alert to your prospects.

backup

Backups

Daily, stored away from the server they protect, and verified: a backup never restored is not a backup.

monitor_heart

Monitoring

We are alerted when the site goes down. The point is simple: not to hear it from one of your clients.

system_update_alt

Updates

Security patches are applied regularly, without you having to ask or even think about it.

The real issue

The backup you find dead on the day of the incident

Many companies have a backup — on paper. They learn on the day of the outage that it stopped running months ago, or that it cannot be restored. A backup you have never restored is not a backup, it is a ticked box.

The rest follows the same logic: the domain renewal, the certificate, the security patches. These are predictable deadlines. They only become a problem when nobody answers for them by name.

What we answer for

  • Domain renewal, tracked ahead of the deadline
  • The certificate, renewed before it expires
  • Security patches, without waiting for your request
  • Daily backups, stored away from the server
  • Restoration, tested rather than assumed
  • Site availability, monitored continuously
Handover

Changing host without cutting the service

A badly prepared migration takes down the site and the email at the same time. The method below avoids both.

  1. Inventory

    Where the site is hosted, who holds the domain, what credentials exist. Many companies discover at this point that they do not own their own access.

  2. Preparation

    The new hosting is set up and the site copied across, while the old one keeps serving your visitors.

  3. Switch

    At a time agreed with you, once the copy has been verified. The old hosting stays live as a fallback for a few days.

  4. Day to day

    Backups, updates and monitoring take over. You are told at each intervention.

References

Sites we keep in service

Transport and logistics, insurance, education, industry, consulting: setups we answer for day to day.

  • Berfast — M&M RAG TRANS
  • NovaShipping
  • ArceySolutions
  • ArchiPlast
  • Salgri
  • Scuola Italiana Paritaria Enrico Mattei
  • S&S Logistics
  • PCS
Frequently asked questions

Frequently asked questions

On European infrastructure. We put it in writing rather than display a "hosted in Morocco" claim that would be inaccurate.

IZ WEB SERVICES is a Moroccan company and processes your data as such. If your business requires data to remain in Morocco, raise it at the first conversation: that is handled upfront, not after the migration.

Hosting

Hand us the deadlines everyone forgets

Tell us where your site is hosted today and what it does. We will propose a costed handover, prepared to happen without downtime.