Dubai · Website Care
Website maintenance services in Dubai — for the site you already have.
Somebody has to keep it running after launch. We do that on the sites we built, and on the ones we inherit — once we have audited them and told you honestly what we found.
- A named engineer
- You keep every login
- Cancel with 30 days
What care covers
Four things that rot quietly when nobody owns them.
None of these announce themselves. You find out about the backup on the day you need it, and about the expired certificate when a customer tells you their browser is warning them.
The updates nobody ran
Core, plugins, themes and dependencies fall behind one release at a time, and the version that finally breaks the site is rarely the one that introduced the problem. Updates go onto staging first, the pages that earn money get checked, then it ships.
The backup nobody restored
A copy that lives on the same server as the site is not a backup, and a backup nobody has ever restored from is a hypothesis. Copies go somewhere else, and we restore from them on a schedule rather than on the worst day.
The speed that leaked away
Sites rarely get slow in one deploy. They get slow through a tracking script here, an unoptimised upload there, and a plugin added for one campaign and never removed. We re-measure against the budget the site launched with — and set one at the audit if it never had one.
The keys nobody can find
Registrar, DNS, hosting, CMS admin and the analytics property are often in five places, two of them a previous developer's personal email. Part of care is a written inventory: what exists, in whose account, renewing when.
Care services
Three services — two you keep, one you commission once.
Support and hosting are standing arrangements. Speed is a defined piece of work with a measurement at each end. They overlap on purpose: a care plan on hosting we run is a shorter conversation than a care plan on hosting we have never seen.
Monthly care covering updates, security patching, offsite backups, uptime monitoring and a named engineer who answers when you write.
You receiveMonthly report + retained hours
Core Web Vitals brought back into the green — images, fonts, scripts and server response profiled and fixed against measured field data.
You receiveOptimisation + CWV report
Hosting & Email
SoonManaged hosting with staging, SSL and daily backups, plus business email — configured, monitored and supported from Dubai.
You receiveManaged hosting + business email
Choosing
Which of the three you actually need.
Getting this wrong is expensive in a specific way: a retainer on a site that is already broken pays somebody to watch it stay broken.
| Option | When it fits | When it does not |
|---|---|---|
| A monthly plan | The site works, and the risk is neglect — updates nobody runs, backups nobody checks, and a short list of small changes each month that never quite justifies a project. You want a named engineer and a report that says what happened. | It is not a repair budget. If the site is already broken, already slow, or carrying years of plugin debt, that gets fixed as a piece of work first. Retained hours spent on stabilising are hours you never see the benefit of. |
| A speed engagement | Field data says the site is failing Core Web Vitals, or it has quietly got heavier and you can feel it on a phone on mobile data. A defined engagement, with a measurement before and the same measurement after. | Not the answer when the site is slow because of where it lives. Oversold shared hosting sets a floor that no amount of image and script work gets under — that is a hosting conversation, and cheaper. |
| Move the hosting | The real problem is infrastructure: nobody is certain where the site is hosted, the certificate is renewed by hand, DNS sits with a developer you no longer work with, or your own email is landing in customers' spam. | Not needed when your hosting is sound and your email is on a platform you control. Keep both and put a care plan on top — we maintain infrastructure we did not sell you. |
How care works
Five steps. Sites we built join at step four.
Everything above that step exists because an inherited site arrives with a history, and none of it is written down.
01
Audit
Nothing starts on a site we did not build until we have opened it: hosting and registrar, DNS records, certificate expiry, CMS and dependency versions, lapsed licences, whether backups exist and where they land, where form submissions actually arrive, and what the error log has been saying. You get the findings in writing — including the cases where the honest answer is that rebuilding costs less over two years than maintaining.
02
Take the keys
Every account moves into your name — registrar, DNS, hosting, CMS, repository, analytics — with us added as a user rather than as the owner. It is an unglamorous step that quietly prevents the next version of the problem that brought you here.
03
Stabilise
The audit backlog is cleared before any monthly rhythm begins: backups running somewhere other than the web server, updates brought current on staging, domains and certificates on automatic renewal, monitoring pointed at a person rather than an inbox nobody opens.
04
The monthly cycle
Updates staged, checked and shipped. A restore verified. Uptime and error logs reviewed. Core Web Vitals re-measured against the budget. Your retained hours spent on the list you send us. It ends with a report saying what changed and what we would do next — not a screenshot of a green dashboard.
05
When something breaks
Incidents leave the cycle. You get a named engineer, an account of what happened and what has been done about it, and the change that stops it recurring. Response targets are written into the plan rather than left to goodwill.
Stack
Boring technology, chosen so the next developer recognises it.
Nothing here is exotic. That is the point: an unusual stack is a lock-in mechanism dressed up as innovation.
- CMS & commerce
- WordPressShopifySanityPayloadWooCommerce
- Infrastructure
- VercelAWSCloudflareGitHub ActionsSentry
Care pricing
What care costs, and what it buys.
AED 1,500
per month
Indicative starting point for a small business site. Larger sites, bigger blocks of retained hours and SLA-backed response sit above it. Prices exclude 5% VAT, and plans cancel with thirty days' notice.
What changes the priceWhat that covers
- Core, plugin and dependency updates, staged before they ship
- Offsite backups, and a restore that has actually been tested
- Uptime, error and certificate monitoring
- Security patching, with renewals tracked rather than remembered
- Retained hours each month for small changes
- A named engineer, and a monthly report of what changed
Related
The rest of what we do.
Two disciplines and the care plan that keeps the result alive. This page covers one of them.
Questions
Asked before handing over the keys.
Yes, once we have audited it. The audit tells both of us what we would be taking on — versions, dependencies, licences, backups, hosting and whatever has been patched by hand along the way. Occasionally it ends with us saying the site is not worth maintaining, and that you would spend less rebuilding it than propping it up. We would rather say that in week one than discover it in month six.
Where the site is hosted and who holds the domain; DNS records and certificate expiry; CMS, plugin, theme and dependency versions, and which of them are abandoned upstream; licences that have lapsed; whether backups exist and where they are stored; where form submissions actually arrive; the server error log; and the performance profile on a phone rather than a desktop. You get it in writing whether or not you go on to a plan.
Included: updates and security patching, offsite backups, uptime and error monitoring, certificate and domain renewals, a block of retained hours for small changes, and a monthly report. Not included: new features, a redesign, new page templates, content production or campaign work. Those are quoted as their own project — absorbing them silently is how a retainer stops covering the maintenance it exists for.
Both, at different scales. Holding a site to the performance budget it launched with is maintenance and sits inside the plan. Bringing a site that already fails Core Web Vitals back into the green is an engagement with its own scope, measured before and after — and once it is fixed, the plan is what stops it drifting again.
Routine work happens in our working hours, Sunday to Thursday, 9:00 to 18:00 GST. Response targets are written into your plan rather than left implied, and the larger tiers are SLA-backed. Downtime and security incidents are handled as incidents rather than queued as tickets, and you are told what happened instead of noticing the site came back.
Usually, yes. What we need is real access rather than a restricted panel login, and backups that are allowed to leave the server. There are hosts where we will tell you the plan is worth less than a move — and we will say so before you sign rather than after.
No. Care plans are monthly and cancel with thirty days' notice. Everything already sits in your accounts — domain, DNS, hosting, code, analytics — so leaving is a matter of removing our access. There is nothing to negotiate and nothing to buy back.
Patching, sensible access control and offsite backups are what the plan does to make it unlikely. On a site we maintain, recovering from a known-good copy and closing the route back in is covered. Cleaning up a compromise on a site we have only just met is its own job with its own scope — we will not quote a fixed price for a mess we have not seen yet.
Ready to build something that lasts?
Tell us what you need. You will get a scoped response with an indicative price — from an engineer, not a salesperson.