Skip to content

Command Palette

Search for a command to run...

Project

Trademark policy

The Phelix name, logo, and dashboard identity are trademarks of Mohammad Abdorrahmani. What you may do without permission, what needs permission, and the rules for forks.

Overview

"Phelix", the Phelix logo, and the visual identity of the dashboard at phelix.anophel.com are trademarks and brand assets of Mohammad Abdorrahmani. The goal is simple: people should never be confused about what is the official Phelix and what is a third party's separate work.

What you may do (no permission needed)

  • Refer to Phelix by name, factually - "works with Phelix", "compatible with Phelix", "based on Phelix", or "a fork of Phelix", as long as it is true and does not suggest we produce, endorse, or support your version.
  • Keep the copyright and license notices in the source, as the license requires - that is attribution, not a trademark grant.
  • Use the name in documentation, articles, tutorials, talks, and comparisons.
  • Discuss, review, or criticize Phelix.

What you may not do (without written permission)

  • Do not name your fork, distribution, product, or service "Phelix" or anything confusingly similar (e.g. "Phelix Pro", "Phelix Cloud", "OpenPhelix", "Phelyx"). Give a distributed modified version its own distinct name.
  • Do not use the Phelix logo or the dashboard's visual identity for your own product, service, site, or app.
  • Do not imply endorsement, affiliation, or partnership, or present your build as the official Phelix.
  • Do not use "Phelix" (or confusingly similar terms) in company names, product names, domain names, app-store listings, social handles, or published package names (npm, crates.io, Docker Hub, Homebrew, Go module paths).
  • Do not use the marks in advertising, SEO, or paid keywords to divert users to a competing offering.

Forks & redistribution

You are free (under the license) to fork the code and contribute changes back. If you publish or distribute your own build, you must:

  1. Rename it to something clearly distinct from "Phelix".
  2. Remove the Phelix logo and dashboard branding from your distribution.
  3. Keep the LICENSE file and copyright notices intact.
  4. Not describe your build in a way that implies it is the official Phelix.

Contributions submitted back to the official project (see Contributing) do not need to be renamed - they become part of Phelix.

Requesting permission

If you have a use that falls outside the above - a genuine integration you would like to co-brand, or a user group - reach out first via phelix.anophel.com. We would rather say yes to a reasonable request than chase down a misunderstanding later. Nothing here restricts rights you have under applicable law, including nominative fair use.