While a 'static' export of the site does solve the vulnerability issue (assuming it is a static export, and not just exporting to something else which could be vulnerable), I imagine lots of organisations would choose not to use it, specifically because some dynamic functionality won't work then.
For those who aren't able/willing to use a fully static version of the site, Varnish (or Apache Traffic Server, Squid, or Apache or Nginx's Cache mode) can provide a huge improvement in performance, and (definitely with Varnish and a custom VCL, possibly not as easy with others) can even handle stuff like grace mode (i.e. return cached, expired results if the origin is offline) and purging cached objects when they're updated in the WP DB (via a plugin which communicates with Varnish).
Im not sure what you mean about maintenance problems?
"Most WordPress websites are just "brochure websites": they don't expose anything dynamic to their visitors excluding comments, contact forms and search functionality. We already handle these scenarios out-of-the box. Also, every plugin you use that does not have any front-facing components, it's perfectly fine. It's not a hosting solution for every possible WordPress website out there, but it can handle a huge slice of the market, with big benefits for agencies/freelances."
Maintenance problems are those you have when you need to update your installation but you can not because the update break stuff around. I had lots of these :-)
> Most WordPress websites are just "brochure websites"
Thats possible for the overall majority of WP users, it just isn't what I've seen it used for.
> Maintenance problems are those you have when you need to update your installation but you can not because the update break stuff around.
How does this service solve that problem? Or do you mean, it allows you to not update immediately to patch a vulnerability, because the site is not the one publicly accessed?
The "admin" lives in a random-generated subdomain, is basic-auth protected and is alive only for the time needed for the editor to make the changes through the dashboard. For the rest of the time WordPress simply doesn't exist.
For those who aren't able/willing to use a fully static version of the site, Varnish (or Apache Traffic Server, Squid, or Apache or Nginx's Cache mode) can provide a huge improvement in performance, and (definitely with Varnish and a custom VCL, possibly not as easy with others) can even handle stuff like grace mode (i.e. return cached, expired results if the origin is offline) and purging cached objects when they're updated in the WP DB (via a plugin which communicates with Varnish).
Im not sure what you mean about maintenance problems?