I'm also not sure what is making you think its "future is uncertain"? It has been around for 4+ years, has been actively developed since inception, has never t

I'm also not sure what is making you think its "future is uncertain"? It has been around for 4+ years, has been actively developed since inception, has never taken any funding and is a fairly popular OSS .NET project with a strong and active community. In that same time frame we've seen multiple generations of Web Service Frameworks in .NET (Mostly from Microsoft), where many of which are now deprecated: .asmx, CSF, WCF, WCF/REST, WSE, WCF DataServices, RIA, MVC (escaping complexity of earlier options) and now WebApi. We still think they continue to promote the wrong approach to web/remote services, as there are more natural benefits of SOA-inspired message-based designs: https://github.com/ServiceStack/ServiceStack/wiki/Advantages-of-message-based-web-services https://github.com/ServiceStack/ServiceStack/wiki/Advantages... ServiceStack's original IService<T> interface has remained unchanged for all its lifetime and we believe its solid design insulates it from re-writes and allows it to evolve naturally to adopt new features. It's simple and flexible core allows it for any plugin to extend and enhance its core functionality: https://github.com/ServiceStack/ServiceStack/wiki/Architecture-overview https://github.com/ServiceStack/ServiceStack/wiki/Architectu... A number of the plugins we maintain ourselves can be seen at: https://github.com/ServiceStack/ServiceStack/wiki/Plugins https://github.com/ServiceStack/ServiceStack/wiki/Plugins OSS software is itself immortal, even if the commercial company behind it collapses - the source will always be open. i.e. it can't be killed by competition, you will always be able to take a fork of an OSS project fix bugs and enhance it as much as you wish or simply contribute to someone else's fork.