Website hosting or maintenance: who does what?

Hosting supplies the infrastructure that makes a site available. Maintenance is the agreed work on the website: for example, changing approved content, investigating a broken link or updating software where that is in scope. A supplier may bundle them, but a hosting invoice alone does not tell you who will fix the website.

Start with the actual problem. An expired domain, a wrong phone number and a contact form that stops delivering messages need different checks and may involve different providers. Name the person who receives the issue, the person who can make the change and the person who approves the result.

Use the table as a worksheet, not as a description of what every supplier includes. Replace the suggested role with a named business contact or provider, then record the agreed scope and where the evidence is stored. One supplier can hold several roles; every row still needs an answer.

Keep account identifiers and recovery details in a private company record. Share access through the provider’s available role controls where possible; do not paste passwords or recovery codes into a quotation form.

Scroll the table sideways to read every column.

As checked on 13 October 2026, Biaway publishes hosting for Biaway websites at SAR 250 per year and maintenance at SAR 100 per month. Maintenance includes up to one hour of minor changes and technical checks each month within the published scope. Examples include text or image changes, contact information, service details, minor layout fixes and broken-link checks.

This small maintenance allowance is not a promise of unlimited development, round-the-clock security monitoring or a fixed emergency response time. A redesign, store build or new integration needs a separate scope discussion. Ask for written confirmation of any backup arrangement, restore work, third-party subscriptions, tax treatment and extra work before relying on them.

Use the existing website-cost guide for the broader build and recurring-cost budget. This checklist helps you decide who does the work and how it will be accepted.

References: Biaway website maintenance scope

For a typical WordPress site, a complete recovery needs both the files and the database. WordPress recommends database backups before upgrades or moving a site. Ask whether both parts are available together and whether restoration has been checked; downloading the website files alone is not a complete database backup.

For a static site on Cloudflare Pages, the platform can return to a successfully built production deployment; preview deployments cannot be rollback targets. That is a deployment feature, not evidence that a separate order database, mailbox or external form service has been backed up.

Write down the acceptable amount of lost work or data and the recovery target your business needs. The supplier should then confirm whether its proposed process can meet those requirements. Do not assume a response deadline or recovery guarantee that is absent from the agreement.

References: WordPress: website backups · Cloudflare Pages: deployment rollbacks

Illustrative example, not a Biaway client result: a supplier in Dammam wants to replace a discontinued product image, revise its Arabic and English service text and confirm that quotation enquiries reach the right team. It sends one request containing the exact page URLs, approved copy in both languages and the licensed replacement image.

The maintainer estimates the work before starting. If it exceeds the agreed allowance or reveals a larger fault, the business approves a separate scope first. Do not assume that a bilingual change or investigation will fit inside one hour.

• Check the Arabic and English pages on a phone and desktop; inspect the changed text, image proportions and relevant links.
• If the request affects a form, agree a clearly labelled test using dummy non-sensitive details. Confirm actual receipt with the authorized inbox owner; a success message on the website alone is insufficient.
• Record approval, deployment date and any remaining issue. Keep a recoverable prior version before making changes.

Scroll the table sideways to read every column.

Before appointing or replacing a provider, list the domain registrar, DNS, hosting, source files or repository, content system, forms, mail provider and analytics property used by your site. Mark anything that does not apply. Record who can grant access and who pays each renewal.

Agree which assets can be transferred, which licences depend on a provider account and what happens to ongoing support. Verify the new authorized access before withdrawing the outgoing provider’s access. The exact ownership and transfer terms belong in the agreed scope; this checklist does not create a contractual entitlement.

• A copy of the agreed work scope and current account inventory.
• Renewal contacts and upcoming dates, with private recovery information stored securely.
• The latest recoverable site version and the location of any separately agreed data backups.
• Outstanding faults, next maintenance tasks and the person responsible for each.

If your site works and you need occasional small changes, ask for a scoped maintenance plan. If the infrastructure itself is the issue, first identify the hosting or domain operator. If several key journeys are broken, request an assessment before treating the whole job as a minor edit.

A rebuild becomes a separate decision when the required features, content structure or technology change substantially. Describe the customer task that currently fails and provide examples. That gives a supplier a better starting point than simply asking to make the website modern.

References: Biaway website maintenance scope

For website maintenance in Saudi Arabia, agree on access, backups, approvals and a change window that suits the business. An illustrative company operating in Hofuf and Mubarraz in Al Ahsa should identify who approves a change affecting both locations. If its website also serves customers in Dammam and Khobar, check the relevant contact details and enquiry destinations after the change.

For orders or enquiries from Riyadh and Jeddah, include the applicable delivery, payment and service information in the same acceptance check. The business’s service area is separate from the hosting server’s location; do not assume that a Saudi-facing website is hosted in a particular city. Biaway provides remote hosting and maintenance within the agreed scope. Confirm response arrangements and any on-site requirements separately instead of treating them as included support.

Launch begins the operating phase. The business needs usable access, renewal information, a way to request changes and a clear response when something fails. A finished design should not leave you guessing who owns the domain, where enquiries arrive or how to restore the site after a mistake.

References: WordPress: website backups · ICANN: domain transfer questions for registrants · Biaway website maintenance scope

List the domain, DNS, hosting, content system or source code, forms, email delivery and analytics. Record the owner, authorized contacts and renewal responsibilities. Store recovery information privately rather than in a public project document.

Confirm which assets and licences are transferable and which depend on a supplier or platform subscription. Ask for the agreed files and documentation, and verify that the business can actually use the access provided.

Practice changing a phone number, updating a service, replacing an image and checking an enquiry where those tasks are part of the editing arrangement. Use a preview or controlled process and preserve a recoverable version.

If the business will not edit internally, define how requests are submitted, approved, priced and verified. A request should include the exact page, replacement content and desired outcome, not only 'please update the site'.

Clarify the period and scope for correcting delivered defects, ongoing hosting support, maintenance and new features. A redesign, new store or integration is different from a minor content change. Confirm response expectations instead of assuming unlimited emergency assistance.

Biaway's maintenance catalogue describes up to one hour of minor work monthly at the published SAR 100 rate checked on 14 October 2026. The actual agreement should confirm exclusions, additional work and any separate backup arrangement.

Keep service details for Hofuf and Mubarraz in Al Ahsa accurate as the business changes. Update delivery or visit conditions for Dammam and Khobar and remote or shipping arrangements for Riyadh and Jeddah. Saudi Arabia pages should reflect current operations in both Arabic and English; changing one language alone can leave customers with conflicting information.

Review important contact routes, renewals and time-sensitive content at appropriate intervals. Ask what is backed up, where it is stored and whether restoration has been tested. A deployment rollback does not necessarily restore a separate database or mailbox.

Keep an issue and change log so a future provider can understand the site. Post-launch care should preserve availability, accuracy and the customer journey. It is an operating responsibility, not an optional concern that disappears when the final design invoice is paid.

Ask Biaway for an account inventory, editing demonstration and a clear distinction between support, maintenance and new work.

Your designer can manage technical services without becoming the only person who controls your website. The useful distinction is between business ownership, delegated administration and the work included in a support package. Agree all three before the site launches so renewal, maintenance and a future supplier change remain manageable.

References: ICANN: domain transfer questions for registrants · Biaway website maintenance scope · WordPress: website backups

Record the domain registrar, registrant details where available, renewal date, billing contact and account recovery arrangements. Use business-controlled accounts and suitable access roles where the providers support them. Ask what happens if your designer is unavailable when a renewal or urgent change is due.

Do not treat a domain name printed on an invoice as complete evidence of control. Confirm the account arrangement directly and document how the business can recover access without depending on one person's private inbox.

Domain registration reserves the name; DNS directs its services; hosting serves the site. Email, databases, analytics and payment accounts may sit elsewhere. A hosting subscription does not necessarily include editing, security updates, backups or mailbox support.

Ask the supplier to list each responsibility, provider and renewal. Biaway's published catalogue checked on 14 October 2026 lists hosting and maintenance separately; confirm the actual deliverables and exclusions for your chosen website before buying either.

A managed service can suit an owner who lacks time or technical capacity. Confirm authorized changes, incident communication, response expectations and the limits of routine work. Avoid informal promises that every future issue is included.

Keep an access inventory without placing passwords in an ordinary shared document. Use the providers' supported permissions and appropriate account protection, and review access when responsibilities change.

For a service business covering Hofuf and Mubarraz in Al Ahsa, a broken contact form can interrupt local enquiries. A supplier serving Dammam and Khobar may depend on quotation uploads; customers in Riyadh and Jeddah may rely on remote consultations. Map these actual journeys across Saudi Arabia and name who checks them after hosting or DNS changes. These examples describe operating needs, not measured outages or promised response times.

Ask what can be exported, what backups include, how restoration is tested and what is needed to move the site. A static deployment backup may not include a separate mailbox or database. Confirm transition assistance and any charges in writing.

Domain transfer rules can depend on the registrar, domain and current restrictions. Check the relevant provider's process rather than assuming an instant move. A clear handover plan makes managed hosting useful while keeping the business able to choose another arrangement later.

Ask Biaway for a domain, hosting and maintenance responsibility list with ownership, renewal and handover details.

Hosting and maintenance are related, but their contracts do not necessarily cover the same responsibilities. Hosting provides the environment that serves the website. Maintenance covers agreed work on the website and its information or functions. A supplier may bundle them, yet you still need to know who handles each problem and which work is excluded.

References: Biaway website hosting scope · Biaway website maintenance scope · Biaway hosting and maintenance responsibility checklist

Separate the domain registration, hosting infrastructure, website application, content and external integrations. A problem can occur in any layer. A server responding normally does not prove that the contact form sends messages or the published price is correct.

Make a responsibility table using actual systems and tasks. For each row, name the owner, supplier, renewal date and support route. This prevents two providers each saying the problem belongs to the other while the business has no record of the agreed boundary.

References:

Biaway lists hosting at SAR 250 yearly with hosting, SSL, deployment, DNS configuration, basic security and applicable performance infrastructure, availability monitoring and basic hosting support. Its maintenance offer is SAR 100 monthly for up to one hour of minor website work. The quoted Biaway hosting offer applies to Biaway websites.

The maintenance examples include approved text and images, contact and service information, small layout fixes and basic checks. These are separate catalogue scopes, not an assurance that every application repair, backup restoration or emergency request is included in either price.

References:

Illustrative cases: an incorrect phone number is a content task; a disconnected form integration may need website and external-service access; an unavailable hosting service begins with the hosting support route. The visible symptom alone may not identify the responsible party, so allow a clear diagnostic handoff.

Ask who coordinates a cross-supplier issue and whether that work is chargeable. The business needs one understandable escalation path even when several companies operate different parts of the stack.

References:

Changing collection hours for Hofuf and Mubarraz in Al Ahsa is not the same job as maintaining the infrastructure. Revised delivery limits for Dammam and Khobar or remote-service instructions for Riyadh and Jeddah are business-approved content changes. Saudi Arabia coverage remains an owner responsibility to define accurately, regardless of which supplier hosts the pages.

References:

Compare invoices against named deliverables, not similar product names. If two suppliers both provide a clearly specified backup service, investigate whether both are needed; if neither promises restore work, do not assume a backup badge fills the gap. Independent copies can be useful, but the architecture must be intentional.

Before choosing a bundle, request the component scopes, exclusions and exit process. A single bill can simplify administration, but a clear division of responsibility is still necessary when an incident or supplier change occurs.

References: Biaway website hosting scope · Biaway website maintenance scope · Biaway hosting and maintenance responsibility checklist

Use Biaway's hosting and maintenance responsibility guide to map your current suppliers before buying another recurring service.

You cannot tell from the word hosting or managed alone. Read the current service description and your agreement, then ask the supplier to confirm specific tasks. This short entitlement audit helps avoid buying duplicate work while uncovering responsibilities that nobody has actually accepted. Treat an unanswered question as unknown, not automatically included or excluded.

References: Biaway website hosting scope · Biaway website maintenance scope · Biaway hosting and maintenance responsibility checklist

Find the current hosting plan, invoice, order confirmation, contract and any agreed amendments. Record the plan name and date because public packages may change. Identify whether the website is on a hosted builder, managed application service or infrastructure-only arrangement.

Do not rely solely on an old sales message or a general help article describing features available in some plans. The question is what your particular account and agreement include now, and which limits apply.

References:

Ask whether the supplier will replace an approved image, update a price, test an enquiry, install relevant software updates, investigate a bug and restore the site. For each task, request one of three answers: included with limits, separately available or not provided.

An illustrative Hofuf and Mubarraz business within Al Ahsa may already have infrastructure monitoring while still needing someone to correct its collection hours. Calling both activities support does not make them the same entitlement.

References:

Ask which data is backed up, how often, for how long and who performs restoration where offered. Clarify whether the host supports only its environment or also your theme, plugins and custom integrations. A service may provide a tool without taking responsibility for operating it for you.

Record any task the owner must perform. A plan can be perfectly suitable with shared responsibility, but only if the business understands and can fulfil its part. Unclear assumptions are more dangerous than clearly stated exclusions.

References:

Updating delivery conditions for Dammam and Khobar or remote-service instructions for Riyadh and Jeddah is a business-content task. Confirm who supplies approved Arabic and English text and who implements it. Saudi Arabia service accuracy is not automatically handled by a company that keeps the server running.

Biaway's catalogue separates hosting at SAR 250 yearly from minor maintenance at SAR 100 monthly for up to one hour. Use that distinction as a concrete example, while checking your own supplier's actual terms rather than assuming all packages are identical. The quoted Biaway hosting offer applies to Biaway websites.

References:

Create a responsibility table with task, current coverage, limit, owner and next action. Buy additional work only for an identified need. If two services overlap, ask whether the overlap is intentional and useful, such as independent recovery arrangements, rather than cancelling one without understanding dependencies.

Save the supplier's answers and review them when the plan changes or a new feature is added. The audit is complete when important tasks have a clear owner and escalation route, not merely when the invoice has fewer lines.

References: Biaway website hosting scope · Biaway website maintenance scope · Biaway hosting and maintenance responsibility checklist

Bring Biaway your current hosting scope and a task list so any additional maintenance covers a real gap.

Prepared with AI assistance, with platform and accessibility claims checked against the primary sources below at publication. The planning frameworks are Biaway’s editorial recommendations. Examples labelled illustrative are not client stories or measured results. Platform features and requirements can change.

• Biaway website maintenance scope
• WordPress: website backups
• Cloudflare Pages: deployment rollbacks
• ICANN: domain transfer questions for registrants
• Biaway website hosting scope
• Biaway hosting and maintenance responsibility checklist