Free for Open Source

Why private npm?

To simplify your code management, builds,
deployment and compliance.

Manage all your organization's Javascript: on the server, in the browser,
and meeting the demands of mobile-first applications with the most popular
web-based technologies:

"The innovation in the node modules published to npm has been core to the success and growth of the node.js platform and ecosystem. In fact, the key to growth has been innovation through modularity."
  • Secure production node.js code in one place: If you’re not running a private npm registry today, that means that anything your developers publish to npm is public. This is fine for Open Source projects, but how do you manage a modular codebase of private packages?

    Many companies running node.js in production still rely on other storage backends, such as git, for these private packages which leads to complications managing SSH keys and other parts of the deployment workflow. By switching to a private npm registry you can securely install all of your private node.js packages from a single, easy to manage location.

  • Always know what modules and versions you're using: All node.js packages use semantic versioning to specify their dependencies. The one downfall of semantic versioning is inconsistent dependencies for a single application deployed at different times. For example, if your application has “*” in your package.json:
    { dependencies: { "express": "*" } }

    and you deploy your application on Monday the dependencies installed could be different from when you deploy your application on Friday. Although this can always be resolved by best practices, in a large enough organization you want to be sure that simple developer error does not cause defects in your applications.

"Every one of your developers who publishes a module to your private npm registry feels a sense of ownership that is much greater than that from contributing to a larger codebase. It is theirs; they own it."
  • Simplify user management: Save you and your team from the tedious process of managing multiple npm accounts: your team members authenticate with their public npm credentials.
Nodejitsu has unmatched operational knowledge from running the public npm registry. That means we know how to manage and scale a private npm registry for you and your organization.
  • Isolated npm infrastructure:By installing your node.js packages from an isolated public replica private npm registry you can greatly decrease your deployment times and avoid any downtime from npm.