Move asp.net application out of IIS

We have a VS 2012/.NET 4.51 app, uses MVC, asp.net, and a bunch of other pieces.

For all the usual reasons, we are finding IIS to be a deploy/ops nightmare (how much script are we expected to write to install/configure IIS? crazy!)

Actually, the app is two web sites: - REST API, based on WCF - Web site, based on MVC, ASP.NET, and several other pieces (a whole big .js/handlebars rich js app)

I looked at moving to Nancy, but that would appear to be a lot of work. (It is not clear to me that asp.net would be happy under nancy. But in all events, it does not look like a drop in.)

What are my alternatives? (IIS is the biggest mess of our whole deploy process. Apache or nginx would be cake.)

OWIN + Katana looks close, but from my understanding you cannot (yet?) run a full ASP.NET app in OWIN/Katana.

We have done some work with powershell DSC. It can solve a lot (and is really great... the IIS part is the biggest pain).

We do not use TFS (we are a Visual Studio + Perforce shop).

Is there magic in the next VS/.NET/Windows/IIS to address this?

Alternate perspective : Migrate ASP.NET app on .net 4.5 to ASP.NET v5 - docs? concepts?