EDIT: Oh sorry, I didn't realize that Prose was based on Jekyll! I guess this suggestion is a bit redundant, but this way you don't need Github if you have your own server, I guess.
More general than a CMS, but the idea is similar.
http://developmentseed.org/blog/2012/june/25/prose-a-content...
This would have to work independently of the platform used to build the original site and ideally the service would also provide a means of getting the newly created static site onto it's hosting platform (be it Dropbox, Digital Ocean or whatever other platform you want to host the static site).
Looking to get away from the speed and security issues of CMS based sites but still having the flexibility and ease of use when building/maintaining a site. Basically using any CMS to build and deploy static HTML web sites.
The CMS version would be a private site (not accessible by the general public) which is compiled into a static HTML site which is publicly accessible.
There should be a way to deal with formerly dynamic elements, such as contact/comment forms, site search, etc. (possibly using third party APIs)
There also should be a way to deal with updates to the CMS version of the site, so that these changes are detected, compiled and processed into the static version of the site.