Choosing business hosting and support: questions to ask
Compare responsibility, backups, restoration and incident handling to understand what your hosting and support agreement covers.
When a website fails, you need to know who can help and what that help covers. Start with responsibility and recovery, rather than storage space and a low monthly price alone.
List the essential functions: website, enquiries, shop or login. Email and domain services need their own agreement even when supplied by the same company.
Separate hosting from website changes
Who manages the server and who maintains the website? A hosting agreement may keep a service running without including repairs to custom integrations, plugins or new features.
Ask what happens when a form stops delivering: who investigates, which systems are included, and when does additional paid work require approval? Ask the same about failures after updates.
Compare the same requirements
| Area | Question |
|---|---|
| Website | Which technology and resources does the package support? |
| Backup | Which files and databases are copied, and for how long? |
| Recovery | Who restores, how is it requested, and what can it cost? |
| Maintenance | Who updates the website, themes, plugins and dependencies? |
| Support | How are faults reported, when is help available, and what is included? |
| Migration | What can you export and who helps you leave? |
Describe actual needs. Ask the supplier to justify the package and explain how it can grow.
Test that backups are usable
“Daily backup” needs a defined scope and recovery process. Shop orders and images may live in different systems. Ask how the pieces fit together during restoration.
Arrange a test in an isolated environment. Inspect the website and important features without sending real customer messages or payments. Document who can authorise a live restore. Decide how much recently changed information the business can afford to lose.
Understand support time commitments
A ticket acknowledgement is not a resolved fault. Distinguish receipt, the start of investigation and ongoing updates. Put required service levels in the agreement. “Personal support” does not automatically mean 24-hour staffing or every type of repair.
Retain control of the services
Document who administers the domain, billing, exports and recovery requests. Use appropriate permissions and secure handovers when people or suppliers change.
Check notice periods and what happens to content and backups after termination. Record where the domain, site and email are held before a change is needed.
Discuss your particular package
Glomiva Hosting describes domain, hosting, email and support services. Current packages and prices are in the hosting panel. Review maintenance responsibility for your chosen package.
For a supplier change, use our website migration checklist.
Keep reading
Choose a platform · 2 min read
WordPress or custom development? Choose for your workflow
Compare publishing, functionality, ownership and ongoing responsibility before choosing your website technology.
Choose a platform · 3 min read
Business email on your domain: plan a careful migration
Separate domains, mailboxes and forwarding, then plan addresses, old messages and delivery tests before moving email.
Choose a platform · 3 min read
Shopify or WooCommerce? Compare costs, responsibility and workflow
Test the same product and order workflow, then compare ongoing costs, maintenance, integrations and exit options.
