MemQL trademark policy
Effective October 10, 2026.
MemQL welcomes independent applications, integrations, distributions, and hosted services. This policy explains how to identify the technology while keeping the provider of a product or service clear.
Software rights and brand rights
ZNAS LLC uses the MemQL name and logo as trademarks identifying the MemQL project and its official offerings. This policy makes no claim that the marks are registered.
The software is licensed under the unmodified Apache License 2.0. Section 6 reserves trademark rights, with exceptions for reasonable and customary descriptions of the software's origin and reproduction of notices. This policy concerns trademark use only. It does not change copyright or patent permissions granted by the software license, or add a fee, notification requirement, or approval requirement for commercial software use.
Nothing in this policy limits fair use, nominative use, or other rights under applicable law. Permission is not required for uses the law already permits.
Descriptive references are welcome
You may truthfully describe your relationship to MemQL without asking first, including in commercial materials. For example:
- "Acme Planner is built using MemQL."
- "Acme Cloud provides independent hosting for MemQL."
- "Acme Connector integrates Shopify with MemQL."
- "Acme Graph is a modified fork of MemQL."
Use MemQL to identify the technology, with your own company or product brand clearly identifying the provider. Do not suggest endorsement, certification, or an official relationship that does not exist. Where context could confuse readers, make the independence explicit, for example: "Acme is an independent provider and is not affiliated with or endorsed by ZNAS LLC."
Articles, tutorials, comparisons, reviews, and other lawful discussion of MemQL do not require approval. A reference or criticism need not be favorable.
Branding that needs permission
Except where permitted by applicable law, obtain written permission from ZNAS LLC before using the MemQL marks as the brand of your own company, product, or service, or as an endorsement or certification mark. Examples include:
- Naming an independent company or service "MemQL" or "MemQL Cloud."
- Using the MemQL logo as your application's icon or your company's logo.
- Marketing yourself as an "official MemQL partner" or "MemQL certified."
- Using a domain name, account name, or presentation that would misleadingly suggest your service is operated or endorsed by ZNAS LLC.
This distinction applies to free and paid offerings alike. Charging money, hosting the software, serving many customers, or running a large company does not by itself create a branding-permission requirement.
Distributions, forks, and logos
Redistributing an unmodified MemQL release under its original name, with its bundled branding and required notices intact, is allowed. Identify yourself as the distributor or hosting provider; do not present your distribution channel or service as an official ZNAS LLC offering.
When marketing a modified distribution as your own product, use a distinct product brand and do not present your modifications as an official MemQL release. You may still identify its origin with language such as "a fork of MemQL." Do not remove legal notices that must be preserved under the applicable licenses.
For optional public acknowledgments, plain-text "Built using MemQL" or "Powered by MemQL" is welcome. It does not make you a partner or certify your product. A link to memql.io is appreciated, not required by this policy. Do not use or alter the logo to suggest an official badge, partnership, or endorsement without written permission. Lawful descriptive uses and rights already granted by applicable licenses remain unaffected.
Requests and partnerships
For a public branding request, open a GitHub issue describing the proposed product name, provider, intended use of the marks, and a mockup or example. The project maintainer is @znas-io. Request a private contact channel before sharing confidential business information.
A branding permission or partnership exists only when agreed in writing; an inquiry or silence is not approval. Any agreement covers its stated scope and does not reduce the rights already granted by Apache 2.0.
See the commercial-use FAQ for software licensing, attribution, hosting, and optional collaboration.