Mesh is specifically the serverless environment that MS runs for you in Azure, so there's no real concept today of running Mesh somewhere else (probably except for Azure Stack) - you have to manage the servers then, so it's not serverless anymore :)

But the thing to keep in mind is that all the capabilities that you're thinking about are in the core product. So you could take SF and run it standalone and tell some people "hey you run the cluster" and another set "hey you write the services" and at least with the resource based model you have a pretty good separation of concerns. It's not Mesh because it's not serverless with MS running the cluster for you, but you can do almost all the same stuff.

Re: the Windows build, yeah what Mikkel said. Slow and steady.

(Hi I'm Mikkel - also from the Service Fabric team)

We are working through this. There are some hard dependencies on internal build systems we need to untangle, but it is coming along.