On most sites maintenance means applying updates. On a bundled WPBakery site the harder question is what to do about the updates that never arrive, because the builder and the slider are licensed to a theme author who may have moved on. We track both, and tell you when waiting stops being reasonable.
Australian team
Based here, working your hours — not a timezone away
144+ projects delivered
Over 10+ years building and maintaining sites for Australian businesses
One developer, start to finish
The same person every time — no re-explaining your site
Straight answers, on your terms
We only take work we can finish. Ask us anything first — no obligation
If you want new sections, templates or a theme replacement, the WPBakery development page covers that. This page is about keeping what exists working and safe.
Every month we check the bundled builder and slider versions on your site against the current releases, and the theme against its own last update. None of that appears in your WordPress updates screen, because a bundled plugin does not report to it — which is exactly why these sites drift years behind without anybody noticing. You get the gap in plain numbers, and a recommendation only when the gap becomes a reason to act rather than a reason to worry.
The parts you can update are applied on a staging copy first, with the pages that use the builder most heavily checked before anything reaches the live site. That ordering matters more here than on a typical site: a core or PHP change can alter how old shortcodes render, and the failure is usually visual rather than an error, so nothing alerts you. The check is a human looking at the pages that earn money.
Generic hardening is worth little on a site whose exposure is a known vulnerability in a component that cannot be patched. What helps is specific: blocking the request patterns that target the historic slider exploits, restricting who can upload and what, and watching the files those exploits write. If a site is compromised anyway, cleanup starts from $299 and we would rather have prevented it.
A backup of a bundled-theme site is only useful if the theme and its licence state come back with it, which is the part most backup plugins are quietly bad at. We take a copy that includes the theme as installed, keep enough history to go back past a problem you did not notice for a fortnight, and restore one to a scratch environment periodically to prove the restore works. An untested backup is a belief, not a safeguard.
Text corrections, price updates, a new staff photo, a seasonal banner — the work most sites need monthly. On a WPBakery site each of these carries a small chance of a layout shifting, so we make them, check the published page at the widths that matter, and keep a note of what changed. Plan hours cover these, and the notes are what make the next change quicker rather than a fresh archaeology exercise.
The genuinely useful thing a plan gives you here is a date rather than a worry. We keep a running position on how long this arrangement remains reasonable, based on the theme's update history, the severity of anything published against the bundled versions, and how much the site earns. When that position changes, you hear it early and with options — a direct licence, a theme replacement, or a staged move — rather than in the week something breaks.
Care starts at $159/mo a month and covers monitoring, updates, backups and small changes. The development plan at $700/mo adds a standing allowance of build time, which suits sites that change most months rather than occasionally. Anything beyond a plan's hours runs at the same published rates as everywhere else — $750 and $1,400 for blocks, $165 hourly. Plans are monthly and can be cancelled; nothing here is a contract you have to argue your way out of.
Month to month, no lock-in — change or cancel any time. Prices in AUD.
Essential
$159 /mo AUD
Keeping a site secure, updated and online. No development time included.
What is covered
Billed monthly in AUD. Cancel any time — no lock-in.
Dev
$700 /mo AUD
Your site stays up, stays secure and stays current — and when something breaks, a developer fixes it rather than logging it.
What is covered
Billed monthly in AUD. Cancel any time — no lock-in.
Master
$1,300 /mo AUD
Where Dev fixes and maintains, Master builds — pages, integrations, and the email and domain problems nobody else will own.
Everything in Dev Plan included +
Billed monthly in AUD. Cancel any time — no lock-in.
Ultimate
Quoted scoped to the work
When the roadmap needs more than Master, or the work is better run as a project.
Get a quoteEverything in Master Plan included +
Yes, and it is often the most sensible spend available. Maintenance keeps the parts that can be patched patched, catches a compromise early, and gives you a considered date for the bigger decision instead of an emergency. What it cannot do is patch a bundled component whose author has stopped shipping, and we will not pretend otherwise.
No. The recommendation changes when the facts change — a new published vulnerability, a PHP version your theme will not survive, a support channel going quiet. Otherwise the answer stays the same and we do not bill you for hearing it again.
This is the most common way these sites break, and it is usually predictable. Older bundled builders use PHP that newer versions removed, so the failure arrives the week the host upgrades. We test against the next PHP version before your host forces it, which turns an outage into a scheduled piece of work.
Only if the theme is still supported and you want it kept current. If the licence has lapsed or the author has gone, we work without it and say plainly what that costs you in update terms.
Yes, and you do not need their cooperation. We need admin and hosting access. The first month usually finds things nobody was watching — a bundled version years behind, a backup that had been failing silently, a slider nobody knew was installed.
Cleanup starts at $299 and is a separate piece of work. On a plan we would expect to catch it early, which is usually the difference between a few hours and a rebuild — and we would tell you honestly which of the two it turned out to be.
Yes. Plans are month to month. Your site, your hosting, your backups — nothing is held to make leaving difficult, and we will hand over notes on what we found rather than making the next person start again.
A short call, a fixed quote, and no obligation either way.
Get a fixed quoteWhy CloudyWP
Care for sites on a bundled WPBakery: we track the builder and slider versions your dashboard never shows, and act before the gap becomes a breach.
Get a fixed quote02 — How we work
Every CloudyWP project runs the same way, whether it is a one-page site or a store with a thousand SKUs. Here is exactly what happens.
01
A single scoping call, then a written plan: what gets built, what it costs, and when it ships. No discovery-phase invoices, no moving targets.
02
Custom WordPress or Shopify on clean code you own outright. Every build ships fast, passes Core Web Vitals, and is handed over documented.
03
Your site talks to the tools you already run — CRM, invoicing, email, stock. The repetitive admin stops being someone's job and starts running itself.
Scope
A fixed quote, in writing
Deliverables, price and dates agreed before a line of code is written.
48 hrs to your quote
