Trademarks
How the name Sypnia and its logo may be used, what you can do without asking, what needs permission, and what to call a changed version or a hosted service.
This page is for anyone who wants to use the name «Sypnia» or its logo: in an article, in the name of a plugin, on a fork, or on a service they sell. It applies to everything, open source Engine and Sypnia Cloud Cloud alike.
Why the name is separate from the code
The licences give you the code and the documentation. They do not give you the name. Those are different things on purpose:
- The code is open so that anyone can run it, change it and share it.
- The name says who made something. If a changed engine, or a service run by someone else, were also called Sypnia, nobody could tell what they were getting, or whom to ask when it breaks.
So you are free to do almost anything with the software, and asked only to be truthful about the name.
The marks: the names «Sypnia» and «Sypnia Cloud», and the Sypnia logo.
What you can do without asking
| You want to | Example |
|---|---|
| Say that you use it | «We find our bugs with Sypnia.» |
| Say that something works with it | «Acme Deploy sends releases to Sypnia.» «Compatible with the Sypnia API.» |
| Name an integration after what it is for | «Acme plugin for Sypnia», acme-sypnia-exporter |
| Write, teach or talk about it | An article, a course, a video, a talk, a comparison, a review, also a critical one |
| Say what a changed version comes from | «Based on Sypnia», «a fork of the Sypnia engine» |
| Share the software exactly as we released it, under its name | A mirror of the image, a package for an operating system, built from our releases without changing what it does |
| Run the engine for others and say what it is | «Acme Monitoring, running the open-source Sypnia engine» |
| Use the logo to point at Sypnia | Next to the name in a list of tools you use or integrate with, in an article or on a slide, unchanged |
Three rules cover all of these:
- Be truthful. Say what the relation is: uses, works with, based on. Do not suggest that we made, approve or support something we did not.
- Your name comes first. In «Acme plugin for Sypnia», Acme is the name and Sypnia says what it is for.
- Leave the logo as it is. Do not recolour it, redraw it or build it into another logo.
What needs our permission
| You want to | Why it needs asking |
|---|---|
| Put «Sypnia» in the name of a product, a company, an app or a service: «Sypnia Pro», «Sypnia Hosting», «OpenSypnia» | It reads as ours. |
| Offer a hosted service called Sypnia, Sypnia Cloud, or «Managed Sypnia» | The same. Name the service after yourself and say it runs the Sypnia engine. |
Register a domain, a social account or a package name that is or starts with Sypnia: sypnia-cloud.example, the @sypnia scope | People will take it for the official one. |
| Use the logo as your own: an app icon, your site’s mark, on merchandise | A logo says who made the thing. |
| Call a changed version «Sypnia» | See below. |
Ask at support@sypnia.com with «Trademark» in the subject. Say what you want to name and where it will appear. We say yes to most things that do not confuse anyone.
Changed versions and forks
The AGPL lets you change the engine and share your version. The name does not travel with a changed version:
- Give it another name, and remove the logo from its Console.
- Say where it comes from if you like: «based on Sypnia» is welcome.
- Small changes for packaging are not a changed version: a build for another platform, a different default path, as long as it does what our release does.
The same holds for the SDKs: a changed SDK is published under your own package name, not under @sypnia.
Writing the name
- Sypnia, with a capital S. Not SYPNIA, not sypnia, except in code, where the binary, the packages and the settings are lowercase.
- Sypnia Cloud for the paid service. The Sypnia engine, or «the engine», for the open-source part. The Console for its built-in page.
Other names in these docs
Names of other products and companies that appear in these docs, such as the cloud providers, databases and coding tools Sypnia works with, belong to their owners. They are used here to say what Sypnia works with, and imply no partnership.
Related
- What you may do with the code and the docs.
- How to send a change, and its terms.