• EnglishEspañol日本語한국어Português
  • Log inStart now

Product and capabilities: capitalization, trademarks, and usage

This page is the definitive resource for capitalizing products, features, and capabilities for use by all New Relic content creators. These guidelines have been vetted by members of legal, content design, product marketing, and docs, as well as leaders from around New Relic.

In general, we use title case for our company name, product/platform name, and a few capabilities and integrations that require it for legal reasons. The following sections also call out first and subsequent uses of terms. First use refers to the first mention in the body copy. It's okay to use the subsequent versions in space-constrained areas such as titles, headers, tables, web navigation, the UI, social media posts, and so on. If you're writing UI copy, see our UI capitalization guidelines.

In general, outside of these product and UI guidelines, use sentence case capitalization.

Do not use acronyms specific to or coined by New Relic externally; only use industry-recognized acronyms such as APM externally.


Find capitalization guidelines for user types and product editions.

Trademarks defined

A trademark is a word, name, symbol, or a combination of the three that identifies a particular product or service. A trademark is how customers recognize you in the marketplace and distinguish you from your competitors for those goods and services.

A trademark name is the name of a company conducting business. The New Relic trademark name is New Relic, Inc.

How to use the New Relic brand name

Here are the general trademark guidelines when using the New Relic brand name:

  • Do not make New Relic or its platform, capabilities, and so on possessive using apostrophes. For example, use “New Relic platform functions” or “New Relic functionality” instead of “New Relic's platform functions” or “New Relic's functionality.”
  • Do not pluralize New Relic or its platform, capabilities, and so on.
  • Do not abbreviate or combine New Relic or its platform, capabilities, and so on.
  • Do not hyphenate New Relic or its platform, capabilities, and so on, and do not allow them to break across a page line when used in text.
  • Avoid confusion by clearly separating and identifying New Relic trademarks from other companies' names and/or trademarks.

Note that it’s generally a best practice to apply these trademark guidelines to other companies’ trademarked names and products too, unless the company’s trademark policies require a different approach.

It’s not necessary to use trademark characters after product names in headings and text on newrelic.com webpages.

Third-party trademarks

In general, it’s not necessary or recommended to use trademark characters after third-party product names on newrelic.com webpages or documents (including PDFs). New Relic is typically not in the position to know if a particular mark is registered. Assuming a third-party product name or other third-party mark is registered can lead to unintended and undesired consequences for New Relic. Thus, avoid using the ® or ™ symbol unless a third party that New Relic partners or works with specifically requires the use of the symbol as a part of its trademark policy.

In some instances, a third party requires the use of the ® or ™ symbol by contract or through its trademark policy. For example, LEGO. A recent FutureStack event promoted an activity in which a LEGO master would create a LEGO model. In this case, LEGO required that the first occurrence of LEGO in New Relic copy should be followed by ®. For example, "You can win a one-of-a-kind LEGO® model of the New Relic Data Nerd Knuckles."

If a company we're working with has its trademark policy publicly available or has privately provided the policy to New Relic, please consult that policy and follow the company’s policy for use of the ® or ™ symbol. If you're unsure of whether you need to acknowledge a third-party trademark in your copy, contact Legal in the #suplegal channel in Slack.

When to use title case

You must use title case for our trademarked names including our company name plus our product/platform name and a few capability and integration names.

This table is kept up to date and is the source of truth for capitalization. Most capability and feature names are lowercase because New Relic is one platform. However, some terms and capabilities are capitalized for trademark or pricing reasons (for example, it's a separate SKU). Note that the use of "capability" here is different than our use of that word in the user management space.


What it is

Use this

Not this

New Relic*

our company

First use: New Relic, Inc. (corporation/entity), New Relic® (printed assets), or New Relic (digital assets)

Subsequent uses: New Relic, our company, we, or it

Do not use: New Relic's, new relic, New relic, NR, their

New Relic platform

our product/platform

First use: New Relic (docs, UI, titles) or New Relic observability platform (marketing content)

Subsequent uses: New Relic or New Relic platform

Note: New Relic observability platform is recommended for marketing content where users might not be familiar with our product.

Do not use: New Relic's, New Relic One, NR1



our annual user group conference

First use: FutureStack® or {Future}Stack® (printed assets), or FutureStack or {Future}Stack (digital assets)

Subsequent uses: FutureStack

Do not use: Future Stack, Futurestack, Future stack


our GraphQL API

First use: NerdGraph® (printed assets) or NerdGraph (digital assets)

Subsequent uses: NerdGraph

Do not use: Nerd Graph, Nerdgraph, nerdgraph, nerd graph


component of New Relic apps; a specific UI view represented by a React JavaScript package

First use: Nerdlet® (printed assets) or Nerdlet (digital assets)

Subsequent uses: Nerdlet

Do not use: nerdlet, NerdLet


component of New Relic apps; the package containing all the files needed by that app

First use: Nerdpack® (printed assets) or Nerdpack (digital assets)

Subsequent uses: Nerdpack

Do not use: nerdpack, NerdPack, Nerd Pack, nerd pack


component of New Relic apps; used to store and retrieve simple sets of data

First use: NerdStorage® (printed assets) or NerdStorage (digital assets)

Subsequent uses: NerdStorage

Do not use: Nerdstorage, nerdstorage, Nerd Storage, Nerd storage, nerd storage

New Relic AI (formerly, New Relic Grok)

our generative AI observability assistant

The product is New Relic AI, and that's how we want to present it.

  • First use: New Relic AI
  • Subsequent uses: New Relic AI. You can also use "our GenAI" or “our GenAI assistant” if the text is lengthy and consistent use of the term New Relic AI becomes redundant.

Do not use: NR AI, New Relic Grok, or AI. Only use "AI" when talking generally about the concept of AI, but never to refer to one of our products.

Note: There are other AI tools not associated with New Relic. For these, always specify the company name to ensure readers understand that we're not referring to New Relic AI.

New Relic CodeStream

IDE extension that integrates with New Relic

New Relic CodeStream (for the New Relic integration with CodeStream) or CodeStream (for just the CodeStream app)

Do not use: New Relic CodeStream's, New Relic Code Stream, Code Stream

New Relic Compute

New Relic pricing model based on compute capacity consumed instead of host or individual user licenses

First use: New Relic Compute

Subsequent uses: New Relic Compute or Compute

Do not use: compute (when referring to New Relic Compute), NRC

New Relic Compute Add On

New Relic add-on that applies to usage-based billing for queries you run against interactive application security testing, Live Archives, and other add-ons as made available. It measures your usage based on Compute Capacity Units (CCUs).

First use: New Relic Compute Add On

Subsequent uses: Compute Add On

Do not use: New Relic Compute Add-On, New Relic Compute add-on

Note: Any instances of other New Relic add-ons are spelled with a hyphen and are lower case; that is, "New Relic add-ons."

New Relic Data Plus

our all-in-one data option with capabilities for Federal Risk and Authorization Management Program (FedRAMP), extended retention, configurable logs obfuscation rules, cloud provider choice, and more

First use: New Relic Data Plus

Subsequent use: Data Plus

Do not use: data plus, NRDP, DP

New Relic database

our database stores ingested data and returns query results

First use: New Relic database (NRDB)

Subsequent use: NRDB

Do not use: New Relic Database

New Relic Explorer

former capability of New Relic

The New Relic main landing page where users can see and explore monitored entities and access Lookout and Navigator. In the platform, it's referred to as the All entities UI page. We can refer to it as the entity explorer, or the entity list view, or in other informal ways (for example: "the first page you see when you open New Relic").

Do not use: New Relic Explorer or Explorer. This is an end-of-life name and should no longer be used in New Relic docs or marketing materials.

New Relic Infinite Tracing*

our fully-managed, tail-based, distributed tracing solution

First use: New Relic Infinite Tracing® (printed assets) or New Relic Infinite Tracing (digital assets)

Subsequent uses: Infinite Tracing

Do not use: Infinite tracing, infinite tracing, New Relic Edge with Infinite Tracing

New Relic Instant Observability

ecosystem of quickstarts for New Relic

First use: New Relic Instant Observability or New Relic Instant Observability (I/O)

Subsequent uses: Instant Observability or New Relic I/O (avoid using the acronym externally, if possible)

Do not use: New Relic instant observability, instant observability, NRIO, IO, I/O

New Relic Live Archives

capability of New Relic that offers long-term storage of log data

First use: New Relic Live Archives

Subsequent uses: Live Archives

Do not use: New Relic live archives, live archives, New Relic LA, LA

New Relic Lookout

capability of New Relic

First use: New Relic Lookout

Subsequent uses: New Relic Lookout

Describing actions in the UI: Lookout

Do not use: New Relic Lookout's, Lookout (okay when directing what to select in the UI), lookout

New Relic Navigator

capability of New Relic

First use: New Relic Navigator

Subsequent uses: New Relic Navigator

Describing actions in the UI: Navigator

Do not use: New Relic Navigator's, Navigator (okay when directing what to select in the UI), navigator

New Relic Query Language

query language similar to ANSI SQL; used to to create queries or run calculations to retrieve detailed New Relic data and get insight into applications, hosts, and business

First use: New Relic Query Language (NRQL)

Subsequent uses: NRQL or New Relic Query Language

Do not use: New Relic query language, or NRQL on first occurrence

New Relic Vulnerability Management

add-on capability of New Relic; used to aggregate vulnerabilities and display them for observability and remediation. (As of January 2023, Vulnerability Management is title case.)

  • When writing about the activity of managing vulnerabilities: vulnerability management
  • When referring to the capability on first mention in body copy: New Relic Vulnerability Management
  • When referring to the capability in headings or on subsequent mentions in body copy: Vulnerability Management

Do not use: VM, vulnerability management monitoring, vulnerability monitoring

* Trademarked


  • New Relic is a registered trademark of New Relic, Inc. It was founded in 2008. We call our employees Relics.
  • The New Relic support team can answer all of your questions about New Relic. They're happy to help.
  • The New Relic observability platform lets you ingest data from practically any source. New Relic gives you access to our curated UI experiences like application performance monitoring, , mobile monitoring, and more.
  • Optimize code performance and feature planning with access to telemetry data from production and pre-production environments directly in your IDE via the New Relic CodeStream integration.
  • New Relic Infinite Tracing is a fully managed, cloud-based solution. Infinite Tracing can analyze 100% of your trace data and choose the most actionable data.

What not to capitalize

Do not capitalize our capability and feature names (what you get with our platform) unless they begin a sentence (and then only capitalize the first word) or are included in the table above. If a capability or feature name includes the name of a trademarked product, then only capitalize the trademarked name (for example, Pixie or Kubernetes).

Feature and capability defined:

  • A feature is an individual experience or element of functionality in the New Relic platform or a New Relic capability.
  • A capability is a collection of features that enable a customer to achieve a use case. A capability is considered a superset of features and often tends to be an outside-in term that customers associate with an existing category such as application performance monitoring, alerts, infrastructure monitoring, and . In other words, capabilities are the things we'd treat as SKUs if we sold them all separately.

Notes about features and capabilities:

  • These are largely internal terms used so that we can discuss New Relic and its structure more clearly. For public resources, we should attempt to avoid these terms and their distinctions and simply talk about how something works.
  • Note that this use of “capability” is different from how we define “capability” in the user management space.

View a diagram of the relationship between our product, features, and capabilities.


What it is

Use this

Not this


installable software used in monitoring; see Usage dictionary # agent and Glossary # agent for more info.


Do not use: Agent

AI monitoring (formerly, New Relic AIM or AIM)

Note: For more information, see our blog, Introducing New Relic AI monitoring, the industry’s first APM for AI

capability of New Relic that monitors AI apps; it bridges the gap between traditional application performance monitoring (APM) and the nuanced needs of AI applications

AI monitoring

Do not use: New Relic AIM, AIM, New Relic AI Monitoring

AIOps (artificial intelligence for IT operations)

capability of New Relic that uses AI to track IT operations; it uses AI to analyze data generated by software systems, predict possible problems, determine the root cause, and drive automated fixes; "AI" refers to both a New Relic capability and a generic term

First use: if space permits, artificial intelligence for IT operations (AIOps); if space does not permit, AIOps

Subsequent uses: AIOps

Do not use: AI for IT Ops


capability of New Relic; detection and notification of issues


Do not use: Alerts

anomaly detection

feature of the alerts capability in New Relic that helps distinguish between typical and atypical system performance

anomaly detection

Do not use: Anomaly Detection, Anomaly detection

application performance monitoring

capability of New Relic; using real-time data to track the uptime and reliability of an application

First use: application performance monitoring (APM)

Subsequent uses: application performance monitoring, APM, or application monitoring

Do not use: Application Performance Management, Application Performance Monitoring, Application Monitoring


feature of New Relic; automatically displays relationships between entities in topology view


Do not use: auto map, Auto Map, Auto map

auto-telemetry with Pixie

Pixie integration with New Relic

First use: auto-telemetry with Pixie

Subsequent uses: auto-telemetry with Pixie, the Pixie integration with New Relic, our Pixie integration, or the integration with Pixie

Do not use: Pixie (okay if referring to px.dev and the open-source Pixie project), Pixie's, Auto-telemetry with Pixie

browser monitoring

capability of New Relic; our real-user monitoring (RUM) solution along with mobile monitoring

browser monitoring

Do not use: Browser Monitoring, Browser monitoring

code-level metric(s)

feature of the New Relic CodeStream capability that allows you to see the golden signals (throughput, error rate, response rate) at the method level within your code.

code-level metric or code-level metrics

Do not use: code level metric(s), Code-Level Metric(s), Code-level Metric(s), Code-level metric(s) (unless at the beginning of a sentence), CLM

compute capacity unit

New Relic Compute is measured in compute capacity units (CCUs), representing the capacity consumed to complete a successfully run customer-initiated action

First uses: compute capacity unit (CCU) or compute capacity units (CCUs). Note: For contractual, licensing, and legal docs, use "Compute Capacity Unit (CCU)" or "Compute Capacity Units (CCUs)."

Subsequent uses: CCU or CCUs

Do not use: Compute Capacity Unit


a method to package software for release


Do not use: Containers


capability of New Relic that uses NRQL to build custom visualizations


Do not use: Dashboards

data ingest

bringing metrics, events, logs, and traces (MELT) data into New Relic

data ingest

Do not use: Data Ingest, Data ingest

digital experience monitoring

a combo of New Relic frontend monitoring capabilities (browser, mobile, synthetics)

First use: digital experience monitoring (DEM)

Subsequent uses: digital experience monitoring or DEM

Do not use: Digital Experience Monitoring, Digital experience monitoring, digital monitoring

distributed tracing

feature of New Relic; a solution for observing service requests as they flow through a distributed system

distributed tracing

Do not use: Distributed Tracing, Distributed tracing

errors inbox

capability of New Relic; our error tracking solution for triaging and resolving full-stack errors

errors inbox

Do not use: Errors Inbox, Errors inbox

event correlation

feature of the alerts capability in New Relic that automatically groups alerts to decrease noise

event correlation

Do not use: Event Correlation, Event correlation

incident intelligence

feature of the alerts capability in new Relic that correlates incidents and offers suggested responders

incident intelligence

Do not use: Incident Intelligence, Incident intelligence

infrastructure monitoring

capability of New Relic that collects performance data on hosts and servers (IT infrastructure) to understand health

First use: infrastructure monitoring

Subsequent uses: infrastructure monitoring, infra monitoring, or infra (for space-constrained areas only)

Do not use: Infrastructure Monitoring, Infrastructure monitoring


solutions that integrate with/gather data from third parties; all our integrations can be found as quickstarts in New Relic Instant Observability


Do not use: Integrations

interactive application security testing

capability of New Relic that's fully integrated with New Relic Vulnerability Management to continuously find, fix, and verify high-risk vulnerabilities across the software developer lifecycle (SDLC)

First use: New Relic interactive application security testing (IAST)

Subsequent uses: interactive application security testing or IAST

Do not use: New Relic Interactive Application Security Testing or Interactive Application Security Testing

Kubernetes cluster explorer

feature of the Kubernetes monitoring capability that ​provides a multi-dimensional representation of a Kubernetes cluster and enables teams to drill down into Kubernetes data

Kubernetes cluster explorer

Do not use: Kubernetes Cluster Explorer, kubernetes cluster explorer

Kubernetes monitoring

capability of New Relic; form of reporting that helps with proactive management of clusters

Kubernetes monitoring

Do not use: Kubernetes Monitoring, kubernetes monitoring

log management

capability of New Relic; collecting, formatting, and analyzing log data to optimize systems

First use: log management

Subsequent uses: log management or logs

Do not use: Log Management, Log management, Logs

logs in context

feature of the log management capability in New Relic; tracing logs throughout a complex service

logs in context

Do not use: Logs in Context, Logs in context

metrics and events

feature of New Relic; navigating data in New Relic without NRQL know-how

metrics and events

Do not use: Metrics and events

metrics, events, logs, and traces

what you monitor for full-stack observability

First use: metrics, events, logs, and traces or metrics, events, logs, and traces (MELT)

Subsequent uses: metrics, events, logs, and traces or MELT

Do not use: Metrics, Events, Logs, and Traces

machine learning (ML) model performance monitoring

New Relic capability that monitors machine-learning (ML) models in production; our monitoring solution for MLOps (machine-learning operations)

machine learning (ML) model performance monitoring

Do not use: Model Performance Monitoring, Model performance monitoring, ML model monitoring, ML model performance monitoring, MPM

MLOps (machine-learning operations)

a set of practices designed to increase the quality, simplify the management process, and automate the deployment of machine-learning models in large-scale production environments

First use: if space permits, machine-learning operations (MLOps); if space does not permit, MLOps

Subsequent uses: MLOps, ML ops

Do not use: ML Ops, ML ops


modern application architecture (vs. monolith)


Do not use: micro services, Micro Services, Microservices

mobile monitoring

capability of New Relic; our RUM solution along with browser monitoring

mobile monitoring

Do not use: Mobile Monitoring, Mobile monitoring


Use monitoring when you're describing specific capabilities and the data from those capabilities. (For more information, see Usage dictionary: Observability vs. monitoring.)

First use: monitoring

New Relic capabilities that include monitoring in the name are also lowercase; for example, application performance monitoring, browser monitoring, and infrastructure monitoring.

Do not use: Monitoring, observability

network performance monitoring

capability of New Relic; understanding how a network is experienced by users

First and subsequent uses: network monitoring

Do not use: Network Performance Monitoring, Network performance monitoring, Network Monitoring, Network monitoring


In general, use observability to describe the New Relic platform and the health of a system holistically based on different types of data. Observability is using the outputs of a system, including different types of data, to understand its health, enabling engineers to gain insights and diagnose issues effectively. (For more information, see Usage dictionary: Observability vs. monitoring.)

First use: observability, full-stack observability, end-to-end observability, New Relic observability platform

Subsequent uses: o11y (derived from removing the 11 letters between the “o” and the “y” in “observability”; note that it’s two number “1”s and not two letter “l”s)

Do not use: Observability, Full-Stack Observability, Full-stack Observability, Full-stack observability, monitoring

query, queries, querying

feature of New Relic; NRQL- or Prom-QL-style way of asking bespoke questions of data

query, queries, or querying

Do not use: Query, Queries, Querying

query builder

feature of New Relic; previously known as chart builder

query builder

Do not use: Query Builder, Query builder


feature of New Relic Instant Observability; pre-built open-source integrations that include dashboards and alerts


Do not use: quick starts, Quick Starts, QuickStarts, Quickstarts

real user monitoring

see Usage dictionary # Real user monitoring

First use: real user monitoring (RUM)

Subsequent use: RUM

Do not use: real-user-monitoring, real-user monitoring, Real User Monitoring, Real-User-Monitoring, Real-User Monitoring

serverless monitoring

capability of New Relic for Lambda and serverless functions

serverless monitoring

Do not use: Serverless Monitoring, Serverless monitoring

service levels

feature of New Relic; used to measure the performance of a service

service level or service levels

Do not use: Service Levels, Service levels, SL, services levels, Services Levels

service maps

feature of New Relic; visual representation of a service

service maps

Do not use: Service Maps, Service maps

session replay

capability of New Relic; provides you with video-like playback of user sessions so you can reproduce and resolve issues

First use: New Relic session replay

Subsequent use: session replay

Do not use: Session Replay

synthetic monitoring

capability of New Relic; simulating users across geographies to identify bottlenecks or experience issues; aka synthetic tests for APIs or browsers

First use: synthetic monitoring

Subsequent uses: synthetic monitoring or synthetics or synthetic monitors

Do not use: synthetics monitoring, Synthetic Monitoring, Synthetic monitoring


feature of New Relic; used to aggregate the health and activity of all entities that provide a business logic

workload or workloads

Do not use: Workloads, work loads, Work Loads, Work loads

If you don't see a feature or capability in one of the above tables, assume that it is not capitalized.


  • Application performance monitoring (APM) helps you instantly understand application performance, dependencies, and bottlenecks. APM gives you a complete view of your applications and operating environment.
  • Covered entities can now send application, infrastructure, digital experience, and network monitoring data to New Relic while maintaining HIPAA compliance.
  • When you need to correlate log data with other telemetry data, enable logs in context in New Relic.
  • NRQL is a query language you can use to query the New Relic database.
  • With a quickstart, you can quickly install dashboards, alerts, and other resources.

Capitalization changes to platform components

We used to capitalize our platform components (below). However, we no longer position our platform this way. Check out how we're positioning our platform and the recommendations for how to refer to these platform components in the following table.


What it is

Use this

Not this

Full-Stack Observability

formerly a separate product—now in lowercase, it describes an outcome of using New Relic

full-stack observability

Do not use: Full-Stack Observability, Full-stack Observability, Full Stack Observability, full stack observability, FSO

Telemetry Data Platform

formerly a separate product—now part of New Relic

telemetry data platform (avoid this term altogether when possible)

Do not use: Telemetry Data Platform, Telemetry data platform, TDP


  • A set of dashboards with data from all New Relic products gives you full-stack observability of your metrics, events, logs, and traces.

Downloadable or printable New Relic documents that are available to the public require a copyright disclaimer in the footer for all registered and unregistered trademarks used within the document. In any instance where the registration marks are not used in downloadable/printable documents, include the following statement in the copyright area of the footer:

© 2008-22 New Relic, Inc. All rights reserved. New Relic and the New Relic logo are registered trademarks of New Relic, Inc. All product and company names herein may be trademarks of their registered owners.

Update the copyright year to reflect the current year.

For purely internal documents, neither the copyright or the trademark notices are required because we are not publishing the documents or putting third parties on notice. Instead, add the following disclaimer to the footer:

New Relic confidential; for internal use only

You should also add the word “internal” to the file name.

Relationships between products, features, and capabilities

This is not an exhaustive diagram, but it provides a model for how our features and capabilities fit together into our product.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.