Skip to end of metadata
Go to start of metadata

StrongLoop Node.js API Server 2.0

These components make up a complete Node.js server that you can use together or separately.  The parts are modular so you can mix and match them as needed.

If you are developing a new Node application or API, use the LoopBack framework.  It features isomorphic models, mobile SDKs, AngularJS integration, security, code-less API composition, and a host of additional evolving features with a thriving community; see the LoopBackJS Google Group.

If you have an existing Node application, use StrongLoop Controller (slc), to manage, monitor and scale your application or API.

Get started

To get started with StrongLoop, see:

Collaborate with us

Most of StrongLoop's code is free, open-source, and available from public GitHub repositories.

The exceptions are:

  • The StrongLoop Controller monitoring agent (strong-agent).
  • Certain LoopBack connectors to enterprise backends (for example, ATG).
  • StrongLoop Studio (coming soon), the graphical developer tool that will require you to register for a free account.
  • Other upcoming components in beta release (you'll know if you have one of these).

StrongLoop distributes all its software using npm.

Node.js and the community

In addition to the components described here, we help maintain Node.js and underlying components such as libuv. Our team contributed the most code to the upcoming Node.js v0.12 release and our founders made the majority of contributions to the v0.10 release before that. We offer Node.js training and consulting to help with your project. Think you've got what it takes to call yourself a Certified Node Developer? Take our Certification Test.

LoopBack, slc, our connectors, and other modules leverage community modules many of which we support, for some of which we have become the lead maintainers, and for all of which we are grateful to the work others are doing. Rather than inventing our own everything, StrongLoop leverages and integrates community work wherever possible. We upstream our patches whenever we can, and try hard not to maintain forks unless our path is diverging from the upstream project.

In addition to writing code, we also sponsor many regional meetups and conferences throughout the year. 

Support and enhancement requests

If there is something that doesn't work the way you think it should or would like it to:

  • If you are a paying customers, file a support case so we can respond according to our Support SLA.
  • If you are a non-paying community member, you are welcome and encouraged to seek support on the mailing list, to file GitHub issues, or to submit pull requests.


  • No labels