Website support is the recurring work that keeps a site available and secure: domain renewal, SSL certificate reissue, availability monitoring, updates and backups with restore testing. We take a site under support from $250 per month, including sites we did not build.
Key takeaways
The basic scope is five jobs that every site needs, whatever its size. Everything else is added according to the task.
The same scope includes minor content and layout edits within an agreed volume — the first package described on our technical support page. The scope is fixed in the contract so that both sides read the monthly fee the same way.
Moving a site from the staging area to the production server is a separate technical stage with its own checklist. A mistake at any step means a browser warning for visitors, emails in the spam folder or lost requests.
Important Register the assets in the company’s name from the start: domain, hosting and email on its details and its payment credentials. Working out who owns the domain at the moment it expires is expensive and slow.
In the .uz zone the buffer after the registration period ends is seven days. The rules for registering and using domain names in the “UZ” domain (cctld.uz) state that the registration period is at least one year, and once it ends the domain name is deactivated and remains with the current administrator for seven days.
After that the domain is released: its records are removed from the registry and the whois database, and it becomes available for new registration. The registrar must send a renewal notice no later than two months before expiry — but it goes to the contacts from the application form, and after a few years those often belong to an employee who has left.
Losing a domain affects more than the site. Email on that domain stops working, links in ads, business cards and signatures break, and if someone else has already registered the address, getting it back becomes a dispute rather than a request to the registrar. Hence a practical rule: the domain expiry date is watched by whoever is responsible for the site, not by a mailbox nobody can open.
The lifetime of public TLS certificates is shrinking on a schedule agreed by certificate authorities and browsers. Section 6.3.2 of the CA/Browser Forum Baseline Requirements sets three dates after which the maximum validity of a certificate is reduced.
Manual renewal stops working on that schedule: sooner or later a certificate is forgotten and visitors see a warning about an insecure connection. The answer is automation. Let’s Encrypt issues certificates for 90 days and recommends renewing them every 60 days, leaving a buffer in case something fails; six-day certificates are available separately.
In practice that means the reissue is automated, monitoring separately watches the actual expiry date on the server, and an engineer is alerted when the automation does not fire.
Without monitoring, the first to report an outage is a customer — or nobody does, and the requests simply stop arriving. Checks run from an outside location, so the site is seen the way a visitor sees it.
The content management system, plugins and libraries receive regular updates, including ones that close vulnerabilities. A site without updates eventually becomes a target for automated attacks that scan for known holes in popular plugins.
The order is simple: backup first, then the update, then a check of the key pages and forms. The backup is not a precaution but a mandatory step — rolling back is easier than repairing what an update broke.
A complete copy of a site has four parts, and missing any one of them turns a restore into a rebuild.
Important A backup you have never restored from is not insurance. What has to be tested is the restore itself: deploy the copy on a separate environment and open the site. How that fits into a plan for an outage is covered in the article on recovering IT systems after incidents.
The line runs through the purpose of the work: support keeps the site running, new work changes what it can do. That split removes the argument that starts with “it is a small thing, why is it billed separately”.
| Work | Included in support | Estimated separately |
|---|---|---|
| Domain renewal, certificate reissue, updates | Yes | — |
| Monitoring, backups, restore testing | Yes | — |
| Editing text, replacing a photo, adding a news item | Yes, within the agreed volume | — |
| Recovery after a breach or data loss | First response and rollback from a backup | Root cause analysis and rebuilding the weak spots |
| A new page, section or form | — | Yes, on estimate |
| A new integration, payments, a client portal | — | Yes, on estimate |
| Redesign or migration to another platform | — | Yes, a separate project |
A server for a website in a data centre in Uzbekistan starts at $30 per month and solves two things at once: pages open faster for local visitors and the data stays in the country. What the law requires to be stored inside Uzbekistan and when a foreign data centre is acceptable is covered in the article on cloud and servers in Uzbekistan.
Responsibility is split: the provider answers for the hardware and the network, the site owner for the application itself, its updates, backups and access. Cheap shared hosting often gives neither access to the logs nor a way to configure backups, so any investigation after an outage ends with “we cannot see what happened there”. The scope of server work is described on the servers and cloud page.
The price depends on what exactly is taken under watch: a single site, a set of the company’s working systems, or continuous development. The service page lists three packages with different scopes.
| What we support | Price | What it includes |
|---|---|---|
| Website | from $250 per month | Project handover, monitoring and alerts, backups with restore testing, updates and patching, minor content and layout edits |
| Company systems | from $700 per month | A map of the systems and their criticality, agreed response times and escalation, monitoring and logs, incident analysis down to the cause, a monthly report |
| Ongoing development | from $1,500 per month | A fixed number of team hours, sprints with a demo of the result, documentation, priorities reviewed every quarter |
We take a site over as a whole, even when someone else built it and no documentation survived: we work out how it is put together, collect the access credentials, describe the infrastructure and record the risks. After that we say plainly what can be supported as it is and what is cheaper to rebuild than to repair every month.
Response times by type of request are fixed in the contract, so you know in advance how quickly we start on a critical failure and how quickly on a routine edit. How request priorities and reporting work for a set of company systems is covered in the article on technical support for IT systems.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
Even a business card website has deadlines you can't miss: a .uz domain stays reserved for you for only seven days after registration expires, and since 15 March 2026 a certificate lasts no more than 200 days. Our website support starts from $250 a month: domain, certificate, monitoring, updates and backups with restore checks.
The provider is responsible for the hardware and network, while the application itself, updates, backups and access belong to the site owner or the support team. Exactly who does what, and how quickly a critical failure gets picked up, is fixed in the support contract.
Restore access step by step: the domain through the registrar using company documents, the hosting through the provider, the admin panel through server or database access. That is usually enough; if the site was built inside a contractor’s own account, it is sometimes faster to move the project to a new environment from a backup.
Updates that patch vulnerabilities go on as soon as they're released — automated attacks specifically probe for known holes in popular plugins. The order is always the same: back up, update, check the key pages and forms.
In a data centre inside the country: pages open faster and the data stays in Uzbekistan. A server for a website or a CRM starts at $30 per month. A foreign platform makes sense when the main audience is abroad and the data storage requirements are met.
Four parts: the site files, the database, uploaded photos and documents, and the server configuration — miss any one and a restore turns into rebuilding from scratch. Backups are stored off the original server and checked by deploying them on a separate setup.
They do not arrive, and that is the most expensive part of downtime: the advertising budget keeps being spent while enquiries are lost. That is why monitoring checks not only that the page opens but also that a test request goes through, and duplicate notifications in Telegram help you notice that the form has gone silent.
