We actually won't be offering MSSQL (Krydos was unaware it costs extra, and none of us know much about it either...I've built Windows web servers before but they all ran MySQL or Postgres because they were for hosting PHP applications under IIS). As of now, we honestly don't have any concrete plans as to what will be offered by the Windows box beyond ASP.NET/IIS. My initial goal is to just get IIS running since it will be a learning curve for all of us. Unlike Apache which we've been running for over 10 years, we've never tried IIS before. The simplest solution to get up and running quickly will be to pass IIS through a cPanel server by letting Apache proxy it (Java is handled this way now...). That way users have IIS hosting (and thus ASP.NET, among other things), but retain the full suite of other functionality (databases, mail, DNS management, etc.) from cPanel. As we progress with it, more functionality will be added to the Windows box. Here's some things I am looking into: How it'll be administered by the users. IIS has a ton of options that normally require access to the desktop or the Windows RSAT.Databases...if we put a cPanel server in front, MySQL and Postgres are redundant. MSSQL isn't free.Perhaps MariaDB, or a NoSQL solution like MongoDB?Whether we can use Lily as a means to offer Ruby on Rails on a server other than Johnny.