Who actually hosts my website, and who do I call if it goes down?
Short answer: If your site was built on an all-in-one tool like Wegic, hosting isn't a separate thing you manage; the platform hosts it for you as part of your subscription, serving your site's static files from a global CDN rather than a traditional server. That's simpler day to day, but it also means you're fully dependent on that one company staying up and responsive if something breaks. Paid Wegic plans include what's described as priority support, but no specific uptime guarantee or response-time commitment was published on Wegic's own pages at the time of this check, so confirm that directly rather than assuming a number.
Something went wrong with your site, or you're just realizing you don't actually know who to call if it did, and that's a bad position to discover you're in during an actual outage.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
This page may contain affiliate links from which Blur Studio earns commissions.
A surprising number of small business owners genuinely don't know who hosts their own website. If you built it through an agency years ago, hosting might be with the agency, a separate hosting company, or something the original developer set up and never documented. If you built it through an all-in-one tool like Wegic, the answer is much simpler, but it comes with its own trade-off worth understanding before you need it.
How hosting works inside an all-in-one builder
On Wegic, hosting isn't something you manage separately at all. Your site's files are hosted on the platform's own infrastructure, bundled into your subscription, and served from a global CDN. You don't pick a hosting provider, configure a server, or manage uptime yourself; it's all handled as part of what you're already paying for. Wegic's own documentation explains a specific technical choice behind this: the platform is built using client-side rendering (CSR) rather than the server-rendering approach some other site builders use, a decision the company has written about directly rather than leaving unexplained. Worth noting separately: Wegic also has a feature it calls Wegic Cloud, but that's a distinct thing, a data-storage and admin-dashboard feature for contact-form submissions, questionnaires and booking info, not the name for the general hosting infrastructure described here.
The practical upshot: you have essentially zero hosting administration to do, which is the main appeal of a tool like this for a non-technical owner. The trade-off is that you have correspondingly little control and little visibility into what's actually happening if something breaks. You can't SSH into a server and check logs; you're entirely dependent on the platform's own status page (if it has one) and support team to tell you what's wrong and when it'll be fixed.
What support actually looks like
Paid Wegic plans (both Starter and Premium) include what's described in the plan comparison as priority support, implying a faster response than whatever free-tier or trial users get. What isn't published anywhere I could verify is a specific response-time commitment or an uptime guarantee, the kind of number a dedicated managed-hosting provider often states explicitly in its terms. That's not unusual for a tool in this category, but it does mean "priority support" is a qualitative promise, not a measurable one, and you should confirm directly with the company what that actually means in practice before you're relying on it during a real outage.
What to check right now, before anything goes wrong
- Find out definitively who hosts your current site, by name, not "I think it's with whoever built it." If you don't know, ask whoever set it up, or check your domain's DNS records (an A or CNAME record pointing somewhere will tell you which service is actually serving the site).
- Save your logins for the hosting platform, your domain registrar, and any site-builder account, somewhere your whole team (not just one person) can access if needed. If the site is not yet on your own address, see how to put your website on your own company web address.
- Decide in advance who's responsible for noticing and responding if the site goes down. "Someone will notice eventually" is not a plan.
- Check what support level you're actually entitled to under your current plan, and what the realistic response time has been for others, via reviews or direct questions to the vendor, not just the marketing copy.
- Set up a simple uptime monitor (several free tools exist) that emails or texts you the moment your site goes down, rather than waiting for a customer to tell you first.
Managed hosting vs. an all-in-one platform like Wegic
A managed WordPress host, for comparison, typically publishes a specific uptime guarantee (99.9% is a common published figure across the category) and a defined support tier, sometimes with a stated response time in writing. You're paying for hosting as its own line item, separate from the website-building tool itself, and you generally have more visibility, sometimes direct server access, into what's actually happening when something breaks. A code-based host is a third option, compared in Netlify vs WordPress hosting.
The trade-off runs the other way too: managed hosting assumes you (or someone you hire) is handling the actual website software, updates and security separately, which is exactly the administrative overhead an all-in-one tool is designed to remove. Neither approach is simply better; they're solving for different priorities. An all-in-one platform optimizes for "I don't want to think about any of this." Managed hosting optimizes for "I want a specific, contractual guarantee about uptime and support."
What I'd actually tell you
If you've genuinely never thought about who hosts your site, that's a sign you've been lucky, not that it doesn't matter. Most owners only discover the gap in their hosting knowledge during an actual outage, which is the worst possible time to be figuring out who to call. Spend the ten minutes now to confirm who hosts your site and what support you're entitled to, whether that's through Wegic, a managed host, or whatever your original developer set up.
If you're specifically choosing a tool like Wegic for a new site, I'd treat the lack of a published uptime guarantee as a real, if minor, factor in the decision, not a dealbreaker. Most all-in-one platforms in this category don't publish hard numbers either, so it's a category-wide gap, not a Wegic-specific weakness, but it's worth knowing going in rather than assuming a guarantee exists that you never actually read.
A worked example: a site going down during a weekend rush
Say your site goes down on a Saturday morning, exactly when weekend bookings usually come in. If you're hosted on an all-in-one platform like Wegic, your options are: check whether it's a known, wider outage (a status page, if one exists, or a quick search for other users reporting the same issue), and contact support through whatever channel your plan entitles you to, then wait. You have no server to restart yourself, no logs to check directly, and no alternative but to wait on the platform's own team. If you're on managed hosting with a published guarantee instead, you'd typically have a defined support channel with a stated response time, and potentially someone you can call directly who has server-level access to diagnose and fix the specific problem. Neither option gets your site back up instantly, but one gives you more visibility into what's actually happening while you wait, and the other is simpler the rest of the time when nothing's wrong.
When this matters enough to actually switch platforms
If your website going down for even a few hours has a real, direct cost (you lose bookings, orders, or leads that don't come back), that's the threshold where a specific, contractual uptime guarantee stops being a nice-to-have and starts being worth paying for directly, even if it means more administrative overhead on your end. If you decide to move, 10 website hosting options for a small business lists the choices.
How I'd approach this
When I build something for a client, hosting, uptime and who's responsible for what are decided and documented upfront, not discovered during an outage. If you're currently on a platform like Wegic and the lack of a hard uptime guarantee genuinely bothers you given how central the site is to your business, that's exactly the kind of thing worth discussing before you need it, not after. Get in touch if you want a setup with a clear answer to "who fixes it."
Questions people ask
Who hosts a website built on Wegic?
Wegic hosts it directly, on its own infrastructure, serving the site's static files from a global CDN, bundled into your subscription. You don't manage a separate hosting provider or server. (Wegic Cloud is a different, specific feature for storing form and booking submissions, not the name for this general hosting setup.)
Does Wegic publish an uptime guarantee?
Not that could be confirmed at the time of this check. Paid plans include "priority support," but no specific uptime percentage or response-time commitment was found published on Wegic's own pages. Confirm this directly if it matters to your business.
What's the difference between this and managed WordPress hosting?
Managed hosting is typically a separate, dedicated service with a published uptime guarantee (often 99.9%) and a defined support tier, but it assumes you're separately handling the website software itself. An all-in-one platform bundles hosting into the subscription with less visibility but also less to manage.
How do I find out who currently hosts my existing site?
Ask whoever built it directly, or check your domain's DNS records, which will show an A or CNAME record pointing to whichever service is actually serving the site.
Should I set up uptime monitoring myself?
Yes, regardless of who hosts your site. Several free tools will alert you by email or text the moment your site goes down, which is faster and more reliable than waiting for a customer to mention it.
What should I do if my site goes down right now?
Confirm first whether it's actually down (try a different device or network, since it could be a local connection issue) and check the status of your hosting provider or platform directly, then contact support through whatever channel your plan entitles you to.
Is it worth paying more for a guaranteed uptime commitment?
If downtime directly costs you bookings, orders or leads that don't come back, yes, it's usually worth the extra administrative overhead of a dedicated managed host with a published guarantee. If an occasional short outage is a minor inconvenience, an all-in-one platform's informal support is often enough.