Hosting should cover where the site lives, an SSL certificate, backups you can actually restore from, and monitoring that tells someone when the site goes down. Maintenance should cover platform and plugin updates, security patching, form testing, and someone paying attention before your customers notice a problem.
Hosting is where your site lives and maintenance is what keeps it working, and they are two different purchases. Both tend to get treated as an afterthought at the end of a website project, usually as a line item nobody explains, and then something breaks and it turns out nobody was watching, there is no recent backup and the site has been down since Friday.
It is worth knowing what each one should cover before you agree to either.
Hosting is where your site lives
What we host for you is server space and the software that runs your site, which for WordPress means keeping the platform on supported versions and for a custom site means somewhere reliable to serve the files. We include an SSL certificate so browsers show the lock and do not warn people away, and that should be automatic rather than an upgrade, because in 2026 it is not optional.
Backups belong here too, and we think two questions matter more than the word itself. How often are they taken, and has anyone ever tested restoring one? A backup nobody has restored is a hope rather than a plan. Monitoring matters for the same reason, because we would rather know the site is down before you hear it from a customer. Capacity is the last piece we look at, including the spikes, since a site that is fine on a normal Tuesday and collapses during your busiest promotion is not hosted correctly.
We offer hosting through the platform of your choice, and we support custom, WordPress and Webflow sites.
Maintenance is what keeps it working
Hosting keeps the site available and maintenance keeps it correct, which is the part people skip.
Platform and plugin updates are the bulk of what we do each month. WordPress core, themes and plugins release updates constantly and many of them are security fixes, so skipping them is how sites get compromised, and the gap gets more dangerous the longer it runs. Security upkeep goes with that, so we patch known problems, watch for anything strange and keep the versions you run supported.
Form testing deserves its own mention, because contact forms fail silently more often than anything else on a website. Email settings change, a plugin updates, a spam filter gets aggressive, and nobody notices until you wonder why the phone stopped ringing. We submit your own forms on a schedule for exactly that reason. Broken links and missing pages accumulate in the same quiet way, especially after a few years of edits, and pages get heavier over time as images and scripts are added, so we watch whether the site still loads quickly. Small content changes like new hours, a new team member or a price change round out the list, and whether those are included or billed separately is a fair question to ask.
Our hosting includes monthly maintenance on your site and regular security upkeep by our developers, which is the proactive version of this rather than waiting for something to break.
Why proactive is the word that matters
There are two ways to buy support. You can call someone when the site breaks and pay for the fix, or you can pay us to look before it breaks.
The first feels cheaper right up until the site is down during your busiest week, or a form has been quietly failing for a month, or an outdated plugin gets exploited. The cost of the fix is rarely the real cost, because the lost calls and the lost trust are.
This is the same reasoning behind maintenance on custom software, and it applies even more to websites, since the platform underneath them changes constantly whether or not you touch anything.
What to ask before you sign up
Whether it is us or someone else, five questions will tell you what you are buying.
Ask what exactly is included each month and get the list in writing, because we have seen maintenance mean very different things from one provider to the next. Ask how often backups are taken and how fast one can be restored, and look for an actual answer rather than a yes. Ask who you contact when something is wrong and how quickly they respond, since during business hours is a fine answer and no answer is not. Ask whether you own your site and your domain, because you should, and if leaving means losing the site then that is not hosting. Then ask what is not included, meaning new pages, design changes and new features, since knowing the line prevents the awkward conversation later.
Who needs a plan
If you are on WordPress, we will tell you plainly that you need maintenance. The plugin and core update cycle does not stop, and unpatched sites are how small businesses end up compromised.
If you have a custom site you still need patching and someone paying attention, even though we have less of it to do. If your site takes payments, handles logins or is the main way customers reach you, the cost of a bad week is much higher than the cost of a plan. If the site is a simple brochure that rarely changes, we will tell you that basic hosting with security updates is probably enough, because there is no reason for us to oversell it.
How to compare two quotes
Hosting and maintenance quotes are hard to compare, because the same words cover very different work. Four things make them comparable.
Get the monthly list in writing, including updates, backups, monitoring, security patching, form checks and how much content editing is included, since a quote that only says maintenance is not a quote. Separate the hosting cost from the labor cost, because server space is a commodity and someone paying attention is not, so if the two are bundled you should ask what each is worth. Ask about response rather than uptime alone, since a 99.9% uptime promise means little if nobody answers for two days when the other 0.1% happens. Then ask what is excluded, including new pages, design changes, new features and anything on a system they do not host.
Warning signs worth walking away from
The first is not owning your own domain. It should be registered to your business in an account you can log into, and anything else gives someone else power over your business. The second is not being able to get a copy of your own site, because if leaving means starting from zero, that is lock-in rather than service.
The third is backups nobody has ever restored, so ask when one was last tested and treat a vague answer as the answer. The fourth is updates handled as needed, because on WordPress needed is constant and that phrasing usually means nobody is doing it until something breaks. The last is no named contact and no stated hours, since you should know who to reach and when they will respond before you need to know it.
Who should hold the accounts
This is boring and it saves people real pain, so it is worth stating plainly.
Your domain should be registered to your business in an account you can log into, rather than your web company's account or a former employee's personal email. Your hosting can be managed by someone else, and you should still be able to get in, or at least be able to get a full copy of the site on request. Your analytics should belong to you with your provider added as a user, because years of history sitting in someone else's account disappears the day you part ways.
The test is simple. If you ended the relationship tomorrow, could you still reach your domain, your site files and your data? If not, that is worth fixing while everyone is on good terms.