Naming and trademarks

When we name things at Red Hat, we follow the parent brand strategy and use a descriptive name that makes it clear what the name represents. Before you create a new name for anything at Red Hat, you must get approval from the Naming team and Legal department.

Descriptive naming

Every name should clearly explain what it represents using descriptive language. For products, teams, and internal tools, the words ‘Red Hat’ should always be included. This strategy helps our employees, customers, partners, and end users quickly identify Red Hat® offerings and initiatives, which makes documentation, navigation, searching—and ultimately purchasing—easier.


Diagram with product names highlighting the parent brand, subbrands, and descriptor of each name.

Product names

Product names start with Red Hat followed by a name that describes what the offering is and does. Product names that include a subbrand like OpenShift® or Ansible® include additional descriptive text in their name.

The Red Hat Enterprise Linux and Red Hat Ansible Automation Platform product logos.

Product logos

Every product logo incorporates the full Red Hat logo and the full name of the product. Learn more about product logos.

Teams, tools, and programs

Diagram with a team, program, and tool name highlighting the parent brand, entity name, and descriptor of each name.

Team, tool, and program names

Teams, tools, and programs start with the Red Hat name followed by a professional and customer-facing descriptive name. They should also include a descriptor like “program” or “team” in the name to make their relationship to Red Hat clear.

The Red Hat logo and IBM logo divided by a line.

Universal logos

Teams, tools, and programs use the universal logo format. This format pairs the name with the fedora icon and a dividing line, making the relationship to the company clear. Learn more about universal logos.

Components, features, and operators

Diagram with a component, feature, and operator name in lowercase.

Component, feature, and operator names

Components, features, and operators are integrated with or added to a product to enhance it but are not available for individual purchase. For this reason, their names do not start with “Red Hat” and they are not capitalized.

Technology icons on a gray background.

Technology icons

Components, features, and operators do not have logos because they are not products. You should type out the name in our font rather than using a logo. These offerings can also have a technology icon to distinguish them in catalogs and marketplaces. Learn more about technology icons.


Diagram with initiative names highlighting the parent brand, initiative name, and descriptor of each name.

Initiative names

Initiatives are groups or programs that engage with Red Hat employees, communities, partners, and customers in unique ways. Like other Red Hat groups, their name always starts with Red Hat followed by a descriptive name.

An initiative logo and the Red Hat logo on a gray background.

Initiative logos

Initiative logos don’t include the fedora icon so they must always be used in conjunction with the full Red Hat logo. Learn more about initiative logos.

Referring to Red Hat

The Red Hat trademark is always written as two separate, capitalized words. Always use the same typeface for “Red Hat”’ that you use for the rest of the text, and keep both words on the same line whenever possible. We do not translate “Red Hat” into other languages.

A registered trademark symbol (®) should be used afer the first use of “Red Hat” as an adjective (for example: “Try a Red Hat® product today”). We do not add ® after “Red Hat” when referring to the company itself.

The word Red, a space, and the word Hat.
Do this

Type Red Hat as two separate, capitalized words.

Image showing misuse: Red Hat typed in various ways without a space or with lowercase letters.
Red X saying do not do this

Do not combine Red Hat into one word or use the words in lowercase.

A line of example text where the words “Red Hat” are on the same line.
Do this

Whenever possible, keep the words “Red Hat” on the same line of text.

Example of misuse: A line of example text where the words “Red Hat” are split across two lines.
Red X saying do not do this

Avoid splitting the words Red Hat across two lines of text.

Two lines of example text in Japanese and German where “Red Hat” is in English, typed in Latin characters.
Do this

Regardless of the language of the content, always refer to Red Hat in English, in Latin characters.

Example of misuse: Two lines of example text in Japanese and German where the words “red hat” have been translated.
Red X saying do not do this

Do not translate “Red Hat” into another language, even when the rest of the text is not in Latin characters.

Product names and trademark usage

The following is a comprehensive list of Red Hat product names with trademark symbols incorporated where necessary. Note the registered trademark symbols only need to be used in the first reference to the product name.

Red Hat® Ansible® Automation Platform (see note 1)
Red Hat® Ansible® Automation Platform on Microsoft Azure
Red Hat® Enterprise Linux® (see note 2)
Red Hat® Enterprise Linux® for SAP® Solutions
Red Hat® OpenShift® (see note 3)
Red Hat® OpenShift® Service on AWS (see note 4)
Microsoft Azure Red Hat® OpenShift® (see note 5)
Red Hat® OpenShift® on IBM Cloud
Red Hat® OpenShift® AI
Red Hat® OpenShift® Container Platform
Red Hat® OpenShift® Data Foundation
Red Hat® OpenShift® Dedicated
Red Hat® OpenShift® Kubernetes Engine
Red Hat® OpenShift® Platform Plus

Red Hat® Ceph® Storage
Red Hat® Certificate System
Red Hat® Data Grid
Red Hat® Device Edge
Red Hat® Insights
Red Hat® Integration
Red Hat® JBoss® Enterprise Application Platform
Red Hat® JBoss® Web Server
Red Hat® OpenStack® Platform
Red Hat® OpenStack® Services on OpenShift®
Red Hat® Quay®
Red Hat® Runtimes
Red Hat® Satellite


1. You can use Ansible Automation Platform after the first use.
2. You can use RHEL after the first use of the full product name in technical, customer-facing documentation.
3. You can use OpenShift on its own after the first use.
4. Only use ROSA after the first use of the full product name or in headlines and other call-outs with character restrictions.
5. Never shorten to ARO.

Copyright and boilerplate

Every web page and the last page of a printed document should have a copyright notice and trademark attribution in the footer. The boilerplate wording is specific to the number of trademark entities on the page. Start with a basic boilerplate (© 2023 Red Hat, Inc.) and customize it with the specific information about trademark attributions necessary.


Red Hat partners with questions about how to articulate their partnership with Red Hat should contact their partner account manager or regional representative.

Red Hat associates can view the Naming page on The Source (Red Hat credentials required) or contact their marketing account manager.