Lapis Notes

License

License overview

Lapis Notes uses different licenses for the app, plugin API, examples, documentation, and brand assets.

Last updated May 28, 2026

Summary

  • Core app: AGPL-3.0-or-later The workspace shell, web host, desktop host, shared UI, notebook runtime packages, language service, and bundled first-party plugins are licensed as part of the reciprocal core app.
  • Plugin SDK/API: Apache-2.0 The public Lapis API package is licensed permissively so plugin authors can build compatible plugins under their own license choices.
  • Example plugins: MIT or Apache-2.0 Example and compatibility-oriented plugins may use permissive licenses when their package metadata says so.
  • Docs and site content: CC BY 4.0 Public documentation and website content can be reused with attribution unless a page or source note says otherwise.
  • Name and logo: trademark rights reserved The Lapis Notes name, logos, and related marks are not granted by the source-code or documentation licenses.

Package Metadata

Each workspace package declares its license in package metadata. If a package, source file, vendored file, or third-party dependency carries a more specific notice, that notice controls that material.

The repository-level license file summarizes the package groups and points to the canonical license text for each license family.

Third-Party And Vendored Code

Lapis depends on open-source packages and includes some vendored code. Those dependencies and vendored files keep their own copyright notices, license terms, and attribution requirements.

Public documentation adapted from upstream projects is attributed on the documentation attributions page.

Plugin Authors

The Apache-2.0 plugin API license is intended to keep plugin development practical. Plugins that merely use the documented API do not have to use the same license as the AGPL core app because of that API package alone. Plugin authors remain responsible for the licenses of their own code and dependencies.

Name And Logo

Open-source and documentation licenses do not grant permission to use Lapis Notes names, logos, icons, domain names, or confusingly similar marks as your own product identity. Forks and redistributed builds should avoid implying endorsement by the Lapis Notes project.

Terms Privacy Attributions