Question about using "n8n" in a project domain name

Hi everyone,

I’m working on an open-source TypeScript SDK that makes it easier to integrate n8n as a headless backend into web applications. The project is still in early development.

Before I register a domain to host the documentation, I wanted to check with the community (and hopefully the n8n team): Is it okay to use “n8n” as part of a third-party project domain name?

I want to be respectful of n8n’s trademark and don’t want to cause any confusion or issues. The domain would clearly be for an unofficial community project, not affiliated with n8n.

Has anyone else navigated this, or could someone from the n8n team clarify the policy?

Thanks in advance!

Hi @AIscream

I’m not part of the official support team, but based on what I found in the documentation:

  • “n8n” is treated as a trademark/brand, and the license explicitly says you may not alter or obscure licensing/copyright notices and that “any use of the licensor’s trademarks is subject to applicable law.” [License FAQs]

  • You’re encouraged to build community projects around n8n (community nodes, templates, local communities, etc.), and those can be branded as community/unofficial projects, but there’s no explicit guidance on whether “n8n” can appear in a domain. [Building community nodes; China community thread]

Because of that gap, the safest path is:

  1. Ask n8n directly about trademark use and your planned domain (e.g. n8n-xxxx.dev), so you have written confirmation:
  • Use the license contact email listed in the docs: [License FAQs]

  • Or post in the forum explicitly asking for an official answer from the n8n team.

  1. When you do proceed, make sure:
  • The site clearly states it’s an unofficial / community project and not affiliated with or endorsed by n8n.

  • You don’t mimic n8n’s official branding in a way that could confuse users (logo, “official” wording, etc.).

Given the lack of explicit written policy in the docs, getting a direct confirmation from the n8n team is the only way to be fully sure your planned domain is acceptable.

1 Like