Docs

Licensing

Which licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. Which licence covers what
  2. The pages
  3. The short answers

This section is for anyone who wants to know what they may do with Sypnia’s code, its documentation and its name: run it, change it, ship it inside an app, build on it, or contribute to it. It covers the open-source parts Engine and says where Sypnia Cloud Cloud is different.

Which licence covers what

PartLicenceIn short
The engine (the sypnia binary) and the ConsoleAGPL-3.0Use it, change it, share it. If people use your changed version over a network, offer them your source.
The SDKs: @sypnia/browser, @sypnia/node, @sypnia/nextMITShip them inside any app, open or closed.
@sypnia/mcp and the agent skillsMITThe same.
This documentationCC BY 4.0Copy and adapt it, with credit. Its code examples can be used without credit.
The name «Sypnia» and the logoTrademarksNot given by any licence above. See Trademarks.
The Sypnia Cloud app, accounts, billing and the GitHub AppProprietaryNot published. You use them as a service.

The pages

  • The licences in plain words

    What the AGPL-3.0 of the engine, the MIT licence of the SDKs and the CC BY 4.0 of the docs let you do when you self-host, modify, embed the SDK in a closed app or offer Sypnia as a hosted service.

  • 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.

  • Contributing

    Where to ask for help with the open-source engine, how to report a bug or send a change, and the terms a contribution is accepted under, including the sign-off on every commit.

The short answers

You want toMay you?
Run the engine for your own apps, at work, for freeYes.
Put the SDK in a closed-source appYes.
Change the engine for your own useYes. If other people use your version over a network, offer them its source.
Offer the engine to others as a hosted serviceYes, under the AGPL, and under another name than ours.
Call your product «Sypnia»No.
Copy the Sypnia Cloud appNo. It is not open source.

Each answer, with its conditions, is in The licences in plain words.

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