The short version
- Use it at home or at work, free
- Run it for a company of any size
- Read and change the code
- Share your changed version
- Include the licence
- Keep the copyright and NOTICE
- Mark the files you changed
- Use the SORN GIT name or logo for your own version
- Hold us liable if something goes wrong
Using SORN GIT for yourself or your company? There's nothing to do and nothing to pay. The rules below only matter if you give copies of SORN GIT to other people.
What you can do
The Apache License 2.0 lets anyone use, copy, change and share SORN GIT, for any purpose, without paying. That includes running it inside a business, installing it for clients, and building your own version on top of it.
If you share it
If you give SORN GIT to someone else, changed or not, as source code or as a program:
- Give them a copy of the Apache License 2.0.
- Keep the copyright notices, and pass on the
NOTICEfile, which reads "Copyright 2026 Amiplay Co.,Ltd." - Make it clear which files you changed.
You can put your own changes under a different licence if you like, as long as SORN GIT's own parts keep these terms.
Patents
Everyone who contributes code to SORN GIT also gives you a licence to any of their patents that the code uses. That grant ends for anyone who sues, claiming SORN GIT infringes a patent.
No warranty
SORN GIT is provided "as is". We work hard on it, test every release and back it up for you, but the licence makes no promises, and Amiplay isn't liable for damage or lost data. If you need a promise, for example support for a business, talk to us.
Your code stays yours
The licence covers SORN GIT itself, not what you keep in it. Your repositories, files and history belong to you, under whatever licence you choose. SORN GIT only sends your code where you tell it to, such as an off-site backup or a mirror you set up. It doesn't report usage to us: the only thing it fetches from us is signed updates. There are no backdoors or hidden scripts: see every connection SORN GIT makes.
The name and logo
The Apache License doesn't give rights to the SORN GIT name or logo. You can say your product is "based on SORN GIT", but if you share a changed version, please give it a different name and logo, so nobody mistakes it for ours.
Open-source parts inside SORN GIT
SORN GIT is built on the work of other open-source projects. Each keeps its own licence, and all of them allow use in SORN GIT. These are the main ones:
| What it does | Project | Licence |
|---|---|---|
| Certificates (Let's Encrypt) | certmagic, acmez | Apache-2.0 |
| Database | modernc.org/sqlite | BSD-3-Clause |
| Passkeys | go-webauthn | BSD-3-Clause |
| Sign-in codes | pquerna/otp | Apache-2.0 |
| Encrypted off-site backups | age (filippo.io) | BSD-3-Clause |
| Cryptography, SSH, networking | Go's x/crypto, x/net, x/sys, x/text | BSD-3-Clause |
| README and Markdown | goldmark | MIT |
| Safe HTML | bluemonday | BSD-3-Clause |
| Code highlighting | chroma | MIT |
| Diffs | go-gitdiff | MIT |
| Settings file | go-toml | MIT |
| Logging | zap | MIT |
| The Go language and standard library | Go | BSD-3-Clause |
Smaller helper libraries are under MIT, BSD, Apache-2.0 or public-domain (CC0) terms.
The full licence
This page is a plain-language summary, not legal advice. If anything here differs from the licence itself, the licence wins. Read the full text at apache.org/licenses/LICENSE-2.0. Questions? Email info@amiplay.com.