Docs

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.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. Why the name is separate from the code
  2. What you can do without asking
  3. What needs our permission
  4. Changed versions and forks
  5. Writing the name
  6. Other names in these docs
  7. Related

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 toExample
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 itAn 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 nameA 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 SypniaNext 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:

  1. 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.
  2. Your name comes first. In «Acme plugin for Sypnia», Acme is the name and Sypnia says what it is for.
  3. Leave the logo as it is. Do not recolour it, redraw it or build it into another logo.

What needs our permission

You want toWhy 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 scopePeople will take it for the official one.
Use the logo as your own: an app icon, your site’s mark, on merchandiseA 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.

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close