Patching & dependency updates
CMS core, plugins, packages and server OS updated on a fixed cadence — staged first, smoke-tested, then promoted. Critical CVEs are out of band, inside 24 hours.
A monthly care plan for the site or application you already depend on: security patches applied on a cadence, uptime watched, backups restore-tested, performance held to a budget. Written SLA, monthly report you can forward to your board, and a block of change hours that never expires unused in the same month.

Most sites do not fail dramatically. They drift — an unpatched plugin, a certificate nobody renewed, a backup that was never restored, a page that got slow one release at a time. A care plan makes each of those someone's job on a schedule.
CMS core, plugins, packages and server OS updated on a fixed cadence — staged first, smoke-tested, then promoted. Critical CVEs are out of band, inside 24 hours.
Synthetic checks every minute from three regions, plus TLS expiry, DNS and domain renewal watches. Alerts route to a human on call, not an unread inbox.
Nightly offsite backups of database and files, 30-day retention, and a full restore into staging every quarter. An untested backup is a hope, not a control.
Field data tracked per template with a budget attached. Drift raises a ticket with the regression identified — usually a new script, an unoptimized image or a plugin.
Contact and quote forms tested weekly end-to-end, broken links and 404s swept monthly, analytics and conversion tags verified so reporting does not silently go dark.
Content edits, new sections, small features, accessibility fixes. Requested by email or ticket, prioritized by you, delivered in the same month or rolled once.
Severity is assigned by business impact, not by how upset the ticket sounds. The response target starts when you report it or when our monitoring catches it, whichever comes first — usually ours.
The same rhythm every month, plus a deeper review each quarter. You get one report at the end of it: what was patched, what broke, what changed, what we recommend next.
Updates staged, smoke-tested against key journeys, then promoted. Forms tested end-to-end and monitoring reviewed.
Your queue, your priority order. Content, fixes and small features shipped through the same review and deploy pipeline as a project.
Uptime against SLA, patches applied, incidents and their causes, Core Web Vitals trend, hours used, and the next recommended action.
Restore test from backup, dependency and end-of-life audit, accessibility spot check, and a roadmap call on what the site needs next.
Priced on what has to be watched and how fast we have to answer, not on page count. Sites we did not build start with a paid takeover audit so the SLA is based on the real state of the code.
For a brochure or marketing site where downtime is embarrassing rather than expensive. Business-hours response, everything patched and monitored.
For sites that generate pipeline and portals people log into daily. Faster clocks, deeper monitoring, and enough hours to keep improving rather than only holding the line.
For applications where an outage stops work or revenue. 24/7 on-call, a named engineer who knows the codebase, and incident practice before you need it.
Taken from the same monthly reports clients receive. Where we missed an SLA target we issued the credit and said so in the report — that is what the number below is net of.
“We moved to a care plan after a plugin update took our quote form down for nine days without anyone knowing. The first monthly report found two more things we would have missed the same way.”
If your current site cannot be responsibly maintained, we will say so during the audit and tell you what it would take to get there — including when the honest answer is a rebuild.
Security patching of the CMS, plugins and server packages; uptime and certificate monitoring; nightly offsite backups with a quarterly restore test; Core Web Vitals and error monitoring; broken-link and form checks; a monthly written report; and a block of change hours you can spend on content, fixes or small features.
Essential care is CAD $850 per month for a marketing site with 4 change hours. Managed care is $2,400 per month with 12 hours, business-hours SLA and staged updates. Business-critical care starts at $6,500 per month for portals and applications with 24/7 response, on-call escalation and a named engineer. There is no setup fee, and plans are month-to-month after the first 90 days.
Yes, after a paid takeover audit. We review the codebase, dependencies, hosting, backups and known vulnerabilities, then give you a written remediation list with a fixed price. Some sites need work before they can responsibly go under an SLA — we tell you that before you sign anything, not after.
Severity 1 — the site or a revenue path is down — is acknowledged within 30 minutes on business-critical plans and one business hour on managed plans, with work continuing until service is restored. Severity 2 degradation is four business hours. Every plan includes a written SLA with the target, the escalation path and the credit if we miss it.
They roll over for one month, so a quiet January can fund a busy February. They do not bank indefinitely, because a maintenance plan is capacity we reserve for you rather than a prepaid balance. If you consistently need more, we move you up a plan rather than billing overage.
WordPress, Odoo Website and eCommerce, Next.js and Astro sites with headless CMS backends, and custom Node or Python applications. We do not maintain unsupported PHP versions, abandoned page builders, or sites we cannot deploy from source control — those need a replatform first.
Hosting runs in your own cloud account and is billed by your provider, not marked up by us. We manage the infrastructure as code, so you keep ownership of the accounts and the DNS. If you would rather we held the hosting relationship, we can — at cost plus a management fee stated on the invoice.
With 30 days notice after the initial 90-day term. On exit you get current documentation, credentials, infrastructure code and a final backup — the same handover package we would give a new developer. Nothing in the plan is a lock-in mechanism.
A takeover audit covers dependencies, hosting, backups, known vulnerabilities and performance, and comes back as a written list with a fixed remediation price. It is yours to keep whether or not you take a plan.