Our standard: every site we build loads in under 2.5 seconds on mobile data.

Transform

Cloud, hosting & managed support

Hosting, SSL, backups, uptime monitoring and patching, with a response time we publish rather than one you find out about during an outage.

Indicative
from KES 14,000/mo
Typical commitmentMonthly, cancel anytime
Deposit50% to start
Source codeYours at handover
SupportCare Plan from KES 14,000/mo
Discuss a project

Who this is for

The site works. Nobody is watching it. The certificate expires on a Saturday, the backup has not been tested, and the first you hear of any of it is a client asking why the site says "Not secure".

A site with no owner

Built by someone who has moved on, hosted on an account nobody can log into.

An organisation with a compliance duty

Backups, patching and access control that have to be demonstrable, not assumed.

A team with no technical staff

One number to call, and a response time in writing.

A system that matters on Monday

Monitoring that tells us it is down before your users do.

What you get

Managed hosting

Provisioned, configured and documented, in your own account where you want it.

Daily backups, tested

A restore is rehearsed, not hoped for. Recovery point and recovery time stated.

Certificates that renew

Automatically, with monitoring in case the automation fails.

Uptime monitoring

Checked from outside, with an alert to us before it becomes an email from you.

Security patching

Applied on a schedule, out of hours, with a note of what changed.

A monthly report

Uptime, incidents, patches and what we would do next. One page.

How the build runs

Each stage ends with something you can open, and a decision you have to make. No month of silence.

  1. 01

    Takeover audit

    What is running, where, on whose account, and what is about to expire.

    1 week
  2. 02

    Stabilise

    Access recovered, certificates fixed, backups started, monitoring added.

    1 week
  3. 03

    Document

    A runbook your team can use, including how to reach us out of hours.

    1 week
  4. 04

    Run

    Monthly patching, monitoring and reporting, with a published response time.

    Ongoing
  5. 05

    Review

    Quarterly: what broke, what we changed, and what should change next.

    Quarterly

What we need from you

Three things, and a project runs on time.

Most delays are not technical. They are a decision nobody was able to make, or data nobody could find.