Uptime
- Every minute from three US regions. Alert after two failures.
Tell us what needs to change. We will help you scope it.
Start a project →Monthly care for WordPress, WooCommerce, Shopify and Laravel. Updates go to staging first, backups get restored on a schedule to prove they work, and a human replies inside a named window.
Site down, hacked or broken after an update?
Send the URL. A senior engineer replies within two business hours (9am-5pm ET), quotes a fixed repair fee, and you decide. Care plans come after the fire is out.
Prices are in the proposal and depend on platform, traffic and included hours. What is included never changes by client.
Response windows apply 9am-5pm US Eastern, Monday to Friday. Outside those hours, monitoring alerts us and critical outages are handled on a best-effort basis, which we state plainly rather than promising 24/7 we can't staff.
Written into every care agreement, so nobody argues about scope while something is broken.
| Area | Covered | Not covered |
|---|---|---|
| Updates and security | Core, theme, plugin and app updates on staging first; security patches; malware scans | Rebuilding a theme or app that can no longer be updated |
| Backups | Daily backups, a quarterly restore drill and restores after an incident | Cleaning a site compromised before onboarding, which needs a repair engagement first |
| Changes | Content and layout changes within the included hours | New features, templates or integrations beyond the hours, quoted separately |
| Hosting and accounts | Monitoring of hosting, SSL, DNS and domain renewal dates | Hosting, license and third-party fees, billed by those providers |
| Growth work | Core Web Vitals watched in the field on Professional and Growth | SEO campaigns, content writing and ads, run by our sister agency BizAttic |
Hours spent on covered work are listed in the monthly report.
Response is when a human acknowledges and starts. Resolution targets depend on the issue, and we report against both.
| Severity | Example | Essential | Professional | Growth |
|---|---|---|---|---|
| S1 · Down | Site offline, checkout broken, hacked | 4 bh response | 2 bh response | 1 bh response |
| S2 · Degraded | Forms failing, major layout break, slow pages | 1 bd | 4 bh | 2 bh |
| S3 · Change | Content update, new section, plugin question | 3 bd | 1 bd | 1 bd |
| S4 · Improvement | New template, integration, speed work | Quoted | Quarterly sprint | Monthly planning |
bh = business hours · bd = business days · US Eastern
Every check below runs automatically. The monthly report shows what fired and what we did.
Updates applied, alerts fired, hours used, Core Web Vitals trend, the restore drill result, and what we recommend next. If nothing happened, the report says nothing happened.
Updates applied, alerts fired, hours used, Core Web Vitals trend, the restore drill result, and what we recommend next. If nothing happened, the report says nothing happened.
A fixed two-to-four-week sprint on your existing WordPress, WooCommerce or Shopify site. We fix what moves the field numbers: images, fonts, scripts, apps, caching, server response. Then we prove it in CrUX, not just a Lighthouse screenshot.
Week one is an audit and an inventory: access, backups, plugins, hosting, open issues. You get a written state-of-the-site report before the first invoice. Then we take over quietly.
Yes. It starts with the onboarding audit so we know what we are taking responsibility for. Some sites need repairs before a plan makes sense, and we will say so.
Up to one month. Hours are there to be used, and the quarterly sprint on Professional and Growth exists to spend them well.
No, and we would rather say that than fake it. Monitoring runs 24/7. Humans respond 9am-5pm ET, with best-effort handling of critical outages outside those hours.
New features beyond the included hours, content writing, SEO campaigns (BizAttic), third-party service fees, and recovering sites that were compromised before onboarding without a repair engagement first.
Any month, with 30 days' notice. Everything stays in your accounts. You keep the documentation and the last report.
Send the URL through the contact form. A senior engineer replies within two business hours, 9am-5pm ET, and quotes a fixed repair fee. You decide before any work starts, and no plan is required.
Updates go to a staging copy first, where we check key pages, forms and checkout. Only then do they reach production, with a fresh backup taken just before. If a production update misbehaves, we roll back to that backup.
That the backup can actually rebuild the site. Each quarter we restore a recent backup to a separate environment and check pages, forms and logins. The time it took and the result go into the monthly report.
Mostly. Shopify runs its own servers, so there are no server patches to apply. A Shopify plan focuses on theme and app updates, checkout tests, monitoring and change work.
Named engineers on our team, each with their own account, which you can revoke at any time. Access is listed in the onboarding checklist. The owner accounts stay yours.