Managed hosting and ongoing care for healthcare portfolios
The kind you never have to think about.
Your sites live somewhere, and somebody has to patch them, watch them, and answer for them at two in the morning. That's us, on one bill, with one place to look.
A circuit with no end. Watching, patching, backing up, and reporting, going round on their own, with the site sitting still in the middle of it.
Hosting only gets your attention when it fails
It's Saturday morning and a site is down. Nobody can say which host it's on, because there are three hosting accounts and a spreadsheet of logins that one person maintains. A plugin nobody updated has turned into an incident on a different site, and you find out from a patient. Then someone in the C-suite asks whether patient data is safe, and the room goes quiet.
Every one of those is a hosting problem wearing a marketing hat.
IT thinks marketing owns the hosting. Marketing thinks IT handles it. Meanwhile nobody has patched anything in six months.
What comes off your plate
- Chasing plugin updates across every site
- Wondering whether the backups actually work
- Finding out from a patient that a site is down
- Maintaining three hosting accounts and a spreadsheet of logins
- Scrambling for an answer when compliance asks
What you get
Watched by someone on call
Uptime monitoring runs continuously with a defined escalation path and a person at the end of it. Most outages are resolved in under 10 minutes.
Patched before it becomes an incident
Plugins, themes, and core, on a schedule, across every site you run. A web application firewall and DDoS protection come standard, and SSL certificates renew themselves.
Backups you can restore from
Daily automated backups with 30-day retention, and recovery that gets tested rather than assumed. A backup nobody has restored isn't a backup.
Built for the way healthcare sites run
Patient information stays out of the website layer by design, sites hold a 96 average Lighthouse score, and the reporting is written so a marketing lead can read it without calling IT.
In healthcare, the breach usually comes through a plugin
A vulnerability gets published the moment it's found, so the people who would use it and the people who have to fix it learn about it in the same hour. From there it's a race, and every site running that plugin is in it whether anyone at your group knows or not.
96%of the 7,966 new WordPress vulnerabilities logged in 2024 were in plugins
An example. A vulnerability is disclosed at 2:07 in the morning. From that moment the exposure window opens, and it widens the longer a site goes unpatched. On a portfolio we run, the patch lands at 7:31 the same morning and the window closes. Left alone, it keeps widening.
0m
Every site running that plugin is exposed, and the window widens the whole time.
Vulnerability counts from Patchstack, State of WordPress Security 2024, which logged 7,966 new WordPress vulnerabilities that year, up 34% year over year.
Compliance starts with keeping PHI off the site
The safest place for patient information is somewhere the website can't reach, so we design it out. A patient request passes through the site and lands in the system already built to hold it.
Holds nothing
Forms and requests
A patient request passes straight through to the system that owns it. The site keeps no copy.
Analytics and third-party tags
Nothing that could identify a patient reaches a tag. We configure that on every site we run.
Holds the patient information
Your system of record
The place already built and contracted to hold patient data, which is where it stays.
Hardened underneath
Encrypted storage, hardened infrastructure, and access limited to the people whose job needs it.
One view of every site you run
Portfolio statusAn example
| Site | Certificate | Last patched | State |
|---|---|---|---|
| Cedar Park Dental | Renews Mar 14 | Aug 9 | Healthy |
| Northgate Family Dental | Renews Feb 2 | Aug 9 | Healthy |
| Summit Pediatric Dentistry | Renews Nov 28 | Aug 11 | Healthy |
| Lakeline Orthodontics | Renews Jan 19 | Aug 9 | Watching a traffic spike |
| Brookside Dental | Renews Dec 6 | Aug 12 | Healthy |
| Riverbend Family Dentistry | Renews Apr 3 | Aug 9 | Healthy |
What moving to us looks like
Most migrations run one to three weeks, depending on how many sites there are and what shape the current setup is in. Portfolios above twenty sites move in phases, and we stabilize the busiest ones first.
What a routine hosting move turned up
Butterfly Effects hired us to move their hosting. We assess a site before we move it, and the assessment turned up three problems they didn't know they had.
Patient information was reaching a place it shouldn't have been. A Salesforce integration had been dropping leads. Analytics was wired wrong, so months of reports had been telling them the wrong story. We found all three, told them, and fixed them.
What it costs
Priced per site, per month, so the number moves with the size of your portfolio rather than sitting as one flat retainer.
Standard
$95per site, per monthWeb application firewall and DDoS protection, certificate management, daily backups, proactive patching, and continuous monitoring.
Premium
$149per site, per monthEverything in standard, with dedicated resources, enhanced performance, and priority incident response.
Enterprise
Customfor larger portfoliosDedicated servers, a custom SLA, and a named account manager. This is where most groups land above about twenty-five sites.
Migrations are scoped separately, once we know what you're running. If your compliance team needs specifics on how we’d handle your environment, bring them to the call and we'll go through it with them.
The team that hosts your sites should be the team that fixes them
Hosting keeps a site up. It doesn't write the new provider bio, rebuild the form that broke, or take the call when a doctor wants a page live by Friday. Website Support is that work, and when one team owns both, nothing falls into the gap between a host and a vendor while each waits for the other to claim it.
Common questions
What's the difference between standard and premium?
How do you handle an outage or a security incident?
Our compliance team will have questions. Who talks to them?
What's the real risk of an outdated plugin?
How long does a migration take?
What happens if we outgrow our tier?
When we're not the right host
- You have an internal infrastructure team that wants root access and its own tooling. We'd be in the way.
- You run a single site and hosting has never once been a problem. A basic managed plan costs less.
Stop guessing whether the sites are fine
Book a call and we'll look at what you're running now.