Hi Rob,
Thanks for reaching out. This has caused some heartburn to us. While Loopback was and is always intended to be an open source framework as has been the case since the past 2 years and has seen great adoption by the community and 46 connectors + SDKs... API Gateway was different.
We had put out an experimental (Labs) gateway project, which was more of a hard-coded example app. It was intended to seek feedback around use cases and was not really a configurable gateway or product. We did not see much collaboration or input from the community on it.
Keeping the hard-coded repo alive also means supporting it and it's a drain for a small startup like ours...particularly as it did not add any considerable value and wasn't widely adopted. Folks we reached out to asked for a Production ready product with robust configuration tooling and use cases like Federated Identity, JWT token, Policy management, API analytics, Proxy, API Portal, mediation, orchestration etc...which they expect from a solid Gateway.
Hence the decision to deprecate it in favor of a robust product. In the short term, we don't envision an open source version of this. We did add the Gateway to our Standard plan to provide it a very low cost (fraction of commercial gateways) to Startups. Thanks for the heads up. We will update our blog from last year.
--
Kind Regards,
Shubhra
Product Marketing Mgr. - StrongLoop