Snapzy
Native macOS app for screenshots, screen recording and annotation.
Young project: few releases and a small community so far. Evaluate carefully before production use.
Desktop app: installed on users' computers, not run as a web service.
Building on it: what may you do?
Short answers based on the licence, for the version in the catalog.
- B1 Change the code for internal use in your company Yes Yes. Keep the licence notices.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes Yes. You don't have to share your code.
- B3 Make a closed-source derivative and sell or distribute it Yes Yes, even closed. The licence and copyright notices must ship with it.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
This is guidance, not legal advice. Check with a lawyer before deciding.
The licence in brief
BSD 3-Clause License (BSD-3-Clause)
Permissive licence. Keep the licence notice and don't use the project's name to endorse your product.
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- BSD-3-Clause
- Licence type
- Permissive
- Maturity
- Young project
- Open core
- No
- GitHub stars
- 3.3k
- Latest activity
- Deployment
- Desktop (macOS)
- Login/SSO
- Unknown
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/duongductrong/Snapzy
- Source
- GitHub API, fetched 2026-10-03
Licence analysis per use case
Sign in to see what the licence means for eight use cases – from internal self-hosting to offering the tool as a service.
Sign in