[snowwrestler]

I too have self-hosted dozens of Wordpress sites over the years, including reverse proxy servers to terminate SSL and cache pages, and CDNs to mitigate DDOS and reduce roundtrip times.

I don't bother anymore. I think your biggest competition today isn't self-hosted Wordpress sites, it's Wordpress.com, WP Engine, Pantheon, GoDaddy Managed Wordpress, etc.

I don't want to seem negative, but I'm having a hard time seeing why I would prefer your system to those. From my perspective the static site generation + services adds complexity, it doesn't remove it. And I'd still have to maintain the Wordpress instance since it provides the backend.

If Wordpress is the backend, then a static copy, to me, just seems like one particular implementation of a caching strategy. I would not expect S3 to serve HTML pages any faster than Varnish, for instance.

[zener79]

Actually there are a couple of things that I'd like to clarify:

1) There is no WordPress backend to maintain as it doesn't exists unless you turn it on in a temporary/hidden/virtual environment to make your changes. For the rest of the time it simply doesn't exists. No PHP, no MySql, nothing that can break. You don't even need to keep your installation updated if you don't want to.

2) The pages are not served from an S3 bucket but from a CDN with 20 edge server around the world. The bucket is only a "source of true" where the CDN loads the files when the "cache" is invalidated. This reduce the TTFB (Time to first byte) up to 10x from any location respect a traditional hosting service.

[snowwrestler]

I think you've identified the right problems--security, pain of maintenance, performance. I don't think you're solving in them in the best way, but don't let that stop you! Hope your business is successful.