Serving, publishing, and deploying your New Relic One app

There are two options for placing your application in New Relic One:

For details on permissions and access to data, see Permissions.


Serve locally

While working on your application, before it’s ready for final publishing, you can locally serve your Nerdpack to display it in New Relic One. If you are doing this for the first time, go through the get-start process from the Build a New Relic One application launcher in

To serve a Nerdpack locally: 

  1. Serve the Nerdpack by running the following in the parent root folder of your Nerdpack: nr1 nerdpack:serve.

  2. Go to The ?nerdpack=local URL suffix will load any locally served Nerdpacks available.

When you make a change to a locally served Nerdpack, New Relic One will automatically reload it.

For more on this, see Local development.



The CLI command nerdpack:publish places your Nerdpack in New Relic One. To publish and deploy, you must be a Nerdpack manager (a type of New Relic add-on role). Your New Relic account administrator can grant this role. For more on permissions, see Permissions and access.

Note: New Relic One requires that only one version (following Semantic versioning) of a Nerdpack can be published. Thus, the success of a nr1 nerdpack:publish command expects both the correct permissions (the aforementioned Nerdpack manager role as well as a unique version (as specified in the package.json's version attribute).

To publish, run: nr1 nerdpack:publish

To learn more about the command's capabilities:

nr1 nerdpack:publish --help



One of the CLI commands is nerdpack:deploy. Deploying a Nerdpack is how you choose which New Relic accounts have access to your application, and how you control which version of the application they’ll see.

When you deploy a Nerdpack, you choose its "channel." A channel represents the development status of an application. There are three-channel choices: DEV, BETA, and STABLE. When you deploy your application (or a new version of your application) you assign it to one of these channels. Channels are meant to be an easier way to control application version access than having to be concerned with many specific version numbers. 

For more on permissions, see Permissions and access