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.
On this page
- The three licences
- If you self-host the engine as it is
- If you change the engine
- If you put the SDK in a closed-source app
- If you build something on top of the engine
- If you want to share or fork the engine
- If you want to offer Sypnia as a hosted service
- If you reuse the documentation
- What no licence here gives you
- Sypnia Cloud
- Quick answers
This page is for anyone deciding whether they may do what they have in mind with Sypnia. It is about the open-source parts Engine. Sypnia Cloud Cloud is a service, used under its terms of service; its app is not open source.
The three licences
| Licence | Covers | What it lets you do | What it asks |
|---|---|---|---|
| AGPL-3.0 (text) | The engine and the Console | Run it for any purpose, read it, change it, share it, charge for it. | Keep the licence and the notices. If you share it, changed or not, share it under the same licence with its source. If you change it and let other people use your version over a network, offer those people the source of your version. |
| MIT (text) | @sypnia/browser, @sypnia/node, @sypnia/next, @sypnia/mcp, the agent skills | Anything, including shipping it inside a closed-source product. | Keep the copyright and licence notice with the copies you ship. |
| CC BY 4.0 (text) | This documentation, and the files in spec/ | Copy it, translate it, adapt it, also commercially. | Give credit, link to the licence, and say if you changed it. |
All three come with no warranty: the software and the docs are provided as they are.
Why two code licences. The SDKs run inside your app, so they must not put any condition on your app: MIT. The engine is a server, and the AGPL makes sure that improvements to a server people depend on stay available to them, whoever runs it.
If you self-host the engine as it is
You may, for any purpose, including at a company and for apps you sell. It costs nothing, there is no limit set by us, and you do not have to publish or tell anyone anything.
- Your app is not affected. Your app talks to the engine over the network, through an SDK that is MIT. The AGPL of the engine does not reach your app’s code.
- Configuration is not a change. Settings, environment variables, the proxy in front, your own function on the alert webhook: none of that modifies the engine.
- You have no source to offer, because you run the published version. Anyone can already get it.
If you change the engine
You may change it in any way.
- For your own use only, with nobody else using your version: nothing more is asked.
- If other people use your changed version over a network, the AGPL asks you to offer them the complete source of your version, under the AGPL, at no charge. This is the clause that makes the AGPL different from other licences, and it is the reason the engine uses it.
Who counts as «other people using it» is where careful readers differ. Your colleagues who open the Console or call the API certainly do. The cautious reading also counts the visitors of your app, whose browsers send to your engine. The way to be safe under every reading is the simple one: publish your changes, for example as a public fork.
Better still, send the change to us. A change that is merged is one you no longer have to maintain. See Contributing.
If you put the SDK in a closed-source app
You may. This is what the MIT licence is for.
- Your app stays yours, under whatever licence you choose. Nothing has to be published.
- Keep the notice. The licence text travels inside the package; if you list third-party licences in your product, add the Sypnia SDK to the list.
- You may change the SDK and keep the change private.
- The same holds for the script tag, for
@sypnia/mcpin your tooling, and for the agent skills in your repositories.
This is true whether your app sends to Sypnia Cloud or to your own engine.
If you build something on top of the engine
A dashboard of your own, a script, an integration, a product that reads Sypnia’s data through the HTTP API or the MCP server: that is a separate program that talks to the engine. It is yours, under your own licence. Using the API does not change the engine.
If you ship the engine together with your product, the engine part stays under the AGPL: pass on its licence and its source, changed or not. Your separate program stays yours.
You may also write your own SDK or client for the event schema and the API. The specifications are CC BY 4.0.
If you want to share or fork the engine
You may give copies to anyone, changed or not, free or paid.
- Pass on the licence and the notices, and give the source or say where to get it.
- You cannot add conditions of your own or put it under another licence.
- A changed version needs its own name. «Based on Sypnia» is fine; calling it Sypnia is not. See Trademarks.
If you want to offer Sypnia as a hosted service
The AGPL allows it. You may run the engine for other people and charge them for it. What applies:
| About | What applies |
|---|---|
| Your changes | If you changed the engine, your customers are people using your version over a network: offer them its source, under the AGPL. |
| The name | Your service needs its own name. You may say, truthfully, that it runs the Sypnia engine. You may not call it Sypnia, Sypnia Cloud, or anything that suggests it is ours or approved by us. |
| What you get | The engine and the Console. The Sypnia Cloud app, accounts, billing, e-mail alerts and the GitHub App are not open source and are not part of what you may host. |
| The licence | Your customers receive the engine under the AGPL, like you did. You cannot give it to them under other terms. |
| Another licence | There is no other licence for sale at launch. Contributions are accepted under the AGPL only, and that binds us too: Sypnia Cloud runs the engine as published. |
If you reuse the documentation
Copy it, quote it, translate it, build a course on it. Say that it comes from the Sypnia documentation, link to the page and to the licence, and say if you changed it.
Code examples in these docs are meant to be pasted into your project. Use them without credit, under the MIT licence.
The name and the logo that appear in the docs are not part of this: see Trademarks.
What no licence here gives you
- The name and the logo. Trademarks.
- The Sypnia Cloud app. It is proprietary and its code is not published.
- A warranty or support. Community help is in the repositories; paid plans of Sypnia Cloud have e-mail support. See Support.
- Other people’s code. The engine and the SDKs include open-source components under their own licences. Each repository lists them.
Sypnia Cloud Cloud
Using Sypnia Cloud is governed by its terms of service, not by the licences on this page. Two things carry over all the same: the SDK in your app is the same MIT package, and the engine behind the service is the published one.
Quick answers
| Question | Answer |
|---|---|
| Does the AGPL force me to open my app? | No. Your app is a separate program, and the SDK inside it is MIT. |
| Must I publish my configuration, my Compose file, my template parameters? | No. |
| Must I publish changes I made to the engine? | Offer them to the people who use your changed version over a network. With nobody else using it, no. |
| May a company use the engine internally? | Yes. |
| May I charge for hosting or supporting it? | Yes, under your own name. |
| May I take the Console’s code into my proprietary product? | Only if that product follows the AGPL. The Console is part of the engine. |
| May I copy the Sypnia Cloud app’s design or code? | No. It is not open. |
| May I train my staff with these docs, or republish them translated? | Yes, with credit. |
| Who holds the copyright of a contribution? | Its author. See Contributing. |