A plain-English guide
No WordPress. No plugins to update. No theme that breaks because something updated itself at 2am. If your picture of a website comes from WordPress, Wix or Squarespace, the sites we build work differently — and it’s worth understanding why before you compare anything. Here’s how they’re built, what running one involves, and how the options really stack up.
01 · How it’s served
Most people's picture of a website comes from the WordPress and Wix era: the site lives on one server, in one city. Every visit travels there, and the server assembles the page on the spot — querying a database, running code — before sending it back. Distance plus assembly is why those sites feel slow, and why they wobble under a traffic spike: one busy machine doing all the cooking.
Modern sites are built the other way round. Every page is built ahead of time, and copies are placed on servers all over the world. A visitor gets the finished page from the one nearest them — nothing to assemble, nothing to query. It loads in a blink in Seattle and in a blink in Sevilla.
It's the difference between cooked-to-order and already-on-the-shelf. Three things follow from that, and they're the real prize:
02 · What it runs on
There is no WordPress here, no plugin library and no admin to log into — but that doesn't mean there's nothing underneath. A site like this isn't one product you buy; it's a small orchestra of services, each doing one job. This is true of any modern site, whoever builds it:
Someone has to own each of these, keep them current, and — the part that catches people out — own every seam between them.
03 · Traditional hosting
This is the part worth knowing if you’re already paying one of them. The sites we build are publishing systems, not folders of files. Content updates trigger an automated rebuild. Forms and dashboards run on cloud functions. Every launch rides on a staging preview and a one-click rollback. That machinery is what makes the site fast, safe to edit and safe to publish.
Shared and managed-WordPress hosting were built for a different architecture and have none of that machinery. So a SiteGround or Bluehost account could certainly hold the files — it just couldn’t run the system that keeps them current.
And moving wouldn’t change much anyway: only the page-serving slice would relocate, while the database, email delivery, code, tooling and the person watching it all stay exactly where they are.
04 · What’s included
All six of those services sit on our accounts, on one bill, for a single monthly fee per site. That fee isn’t really buying servers — servers are the cheap part. It’s buying the fact that every one of them, and every seam between them, is somebody’s job rather than yours.
What it covers:
05 · The editor
Every content system we could have handed you falls into one of two traps: powerful enough that a wrong click breaks the layout, or locked down so hard it’s useless. So we built our own, and it comes with every site we run. It is not an off-the-shelf add-on, and there is nothing else quite like it to buy.
You never log into an admin full of menus, and you never touch code. You tell the site what you want changed, in plain words — the way you’d text a very fast web person:
It shows you the change, you approve it, and it’s live in minutes. No training, no manual, no hunting for which menu it was under.
It also comes with guardrails, which is the part that took the work: it edits words and content, not structure. Unlike a traditional site admin, it hands you the keys without handing you the ability to accidentally drive through the storefront.
Change your copy as often as you like. No credits, no allowances, no tier upgrade when you’ve used your twenty edits for the month.
Anything structural — new pages, new functionality, design changes — is a request to us, quoted at standing rates.
It’s also why “who updates the website?” stops being a staffing question.
06 · The boundaries
Clear boundaries make good relationships, so — one clean rule: the site fee watches the site. Anything else that runs carries its own fee, and every fee includes its own monitoring:
07 · Support
Most issues are found and fixed by the monitoring before anyone notices — that's its job. For everything else, you message one person:
That's what the fee is, in the end: keeping the site at its best — fast, healthy, growing — is our job, not yours.
08 · The comparison
All four are real options, and for plenty of businesses one of the cheaper ones is genuinely the right answer — this is only worth reading so the choice is an informed one. The honest side-by-side:
| Shared hosting + WordPress | DIY cloud accounts | AI site builders (Bluehost, GoDaddy, Wix…) |
Managed by Camalia | |
|---|---|---|---|---|
| Fast, global page deliveryServed from a CDN near every visitor | variestypically one shared server | ✓ | usuallytheir hosting, their speed | ✓ |
| Minimal attack surfaceNo plugins or theme code to exploit | ✗plugins are the classic way in | ✓ | ✓their platform, their problem | ✓ |
| Software kept updated & patched | —you, or whoever you hire | —you | ✓the platform updates itself | ✓ |
| Health monitored dailySomeone notices before your visitors do | ✗ | ✗ | platform onlynobody watches YOUR site | ✓ |
| Something needs fixing — whose job? | yoursfind help, brief them, wait | yours | yoursvia a support queue | oursusually before you notice |
| Edit your own content, safelyWords yes; breaking the layout, no | partialfull admin — powerful, breakable | ✗code changes only | partialtemplate editor — and AI edits are metered (e.g. 20/month) | ✓self-serve editor included — no meters, no credits |
| Preview changes before they go live | ✗edits publish immediately | partialif you build the workflow | ✗edits publish immediately | ✓private staging, every time |
| Backups verified + one-click rollback | partialadd-ons; restores rarely tested | partialdeploy history only | variesplatform-dependent | ✓ |
| Privacy & email compliance kept currentCookie consent, CAN-SPAM, sender authentication | ✗ | ✗ | ✗ | ✓ |
| Core capabilities built inSEO, security, backups, forms, caching, consent | via plugins*assembled piece by piece — the good ones are paid, and each needs its own updates | ✗you build or wire each one yourself | basics onlyanything custom hits the ceiling fast | ✓part of the build, no add-ons |
| A monthly report on how it's doing | ✗ | ✗ | ✗ | ✓ |
| One accountable person to call | ✗ | ✗ | ✗ | ✓ |
| Typical cost | $10–50/mo + plugin licenses + your time |
$25–60/mo across services + a developer on call: you |
~$10/mo teaser → $30+/mo base renews ~3× higher — and that's before extra AI credits, which cost more; how much more, and how many you'll need, is the mystery |
Quoted per site all of the above, handled — and the only column where the work is included, not just the tools |
The quiet cost of the WordPress model. Matching what's built into our sites typically means a stack of premium plugins — SEO, security, backups, caching, forms, cookie consent — commonly $300–600 a year in licenses, each one updating on its own schedule, before anyone has touched the site itself.
For a simple brochure page, they're genuinely fine, and the price is real. The ceiling is what you're deciding about: template design (your site looks like everyone else's), their walled garden (the site can't leave the platform), no custom anything (a searchable archive, a quiz, a content automation — not buildable there), and you're still the operator. And read the fine print: the headline prices are typically multi-year prepaid teasers that renew around triple the advertised rate — and even the editing is rationed (one current offer includes twenty AI edits a month. Twenty.) They generate a site in minutes; nobody said anything about the years after.
09 · The bottom line
Every option on that table costs money. What differs is what the money buys, and how much of the work it leaves with you.
Of a typical managed fee, the raw infrastructure — servers, CDN, database, email delivery — comes to roughly $30–40. The rest isn’t margin on hosting. It’s the work: monitoring that catches problems before you see them, updates and patches applied, backups verified rather than assumed, compliance kept current, and one person who is accountable when something goes wrong at 4pm on a Friday.
Assembling the pieces yourself is cheaper on paper and more expensive in practice — half a dozen accounts and bills, every seam between them, and every one of those jobs landing on somebody. Usually you, or somebody you have to find, brief and wait for.
So if there’s one question worth carrying into any of these comparisons, it’s this: whose job is the website? On every other column of that table, the honest answer is yours.