Yes. Hosting appears in our service catalog, including website hosting and dedicated WordPress hosting. The right arrangement depends on your website and on which operating tasks you want us to handle. A new website project does not automatically include every hosting or care responsibility.
What does it cover when we provide website hosting?
Hosting provides the environment where your website runs. Managing the website is a separate question. Your site may also rely on a domain registrar, DNS provider, email service, form delivery service, payment provider, and backups. Someone needs to own each account and know what to do when one connection stops working.
Before you choose an arrangement, ask who will own the hosting account, pay the provider, control DNS, maintain the application, keep backups, and handle support requests. The written scope should identify these responsibilities. It should also say whether ongoing monitoring or content changes are part of website care or a separate service.
Can I keep my current host?
You may not need to move. If you already have hosting, share the provider, platform, access level, and any known problems. We can assess whether your current setup supports the planned work. A host change should solve a specific need, such as platform fit or operational ownership, not happen simply because a new website is being designed.
If a move is appropriate, the scope should cover the site files and database, DNS, email dependencies, forms, redirects, testing, and the changeover plan. Domain and email ownership deserve particular attention because those services may sit outside the website host.
How do I choose?
Start with the site you have or plan to build, then decide who needs to operate it after launch. A simple brochure site and a store with orders, accounts, and integrations can need different support. Ask for the hosting responsibilities and recurring costs in writing before approving a build or migration.
Which decisions belong in the hosting agreement?
Ask where the site is hosted, who holds the account, who pays recurring charges, what backup arrangement applies, and who can restore the site if there is a problem. Clarify what the provider handles and what remains the website owner’s responsibility. Hosting, software updates, security monitoring, content changes, and emergency response are related but not interchangeable services.
The domain is another important boundary. A website can live on one provider while the domain and email live elsewhere. Before making DNS changes, identify which records support the website and which support email or other business tools. A migration plan should preserve those dependencies and include a way to check the site after the change. We should not promise zero interruption without understanding the existing setup.
What if the site is already running elsewhere?
There may be no need to migrate. We can review whether the current host supports the platform, access, performance needs, and operating model the project requires. If your current provider is working well and you want us to handle design or development only, the agreement can define how we coordinate with that provider. If a managed arrangement is proposed, it should explain exactly what management adds beyond the underlying server.
When comparing options, look beyond an advertised monthly rate. Include renewal terms, storage and resource needs, backup retention, license costs, support boundaries, and the work required to move. The right choice is the one whose responsibilities your team understands and can sustain.
Tell us where your site lives today and what you want help managing. We can discuss whether to use your current host or scope a hosting service around the site.