Licence
One repository. The whole directory.
Halo is the Go server, the console, the deploy files and the docs, in a single public tree under the Apache License 2.0. There is no second edition hiding behind a login.
- Licence
- Apache-2.0
- Editions
- One
- License key
- None
- Hosted cloud
- Not yet
The tree
Four directories, one licence.
Anything Halo decides, from a passkey sign-in to an access review, is in one of these. The pages on this site describe that code. They are not a separate claim.
- cmd/haloThe serverSign-in, sessions, policies, tokens and the audit log. This is the program the console talks to.
- webThe consoleThe account portal and the administrator interface. Same repository as the server, not a separate product.
- deployThe installDocker Compose, the proxy, and the install script. What a host actually runs.
- documentationThe docsThe same guides as halo.scala.gg/docs, kept next to the code they describe.
In practice
What the licence does, and what it does not.
Apache-2.0 lets you use, modify and distribute Halo, including for your own organization, if you keep the licence and the notices. It does not operate the database.
| Halo | A hosted directory | |
|---|---|---|
| Where the code lives | github.com/ScalaStudios/Halo | The vendor |
| Where the directory runs | A Linux host you administer | Their cloud |
| What you pay Halo | Nothing for the licence | A subscription |
| What you still pay for | The machine, disks, backups | Usually nothing extra for compute |
| A release you can pin | Not yet. Today you run main | Numbered releases |
Keycloak is Apache-2.0 as well. Halo is not the only directory you can read. It is the one that puts access requests, reviews, lifecycle rules and SSH certificates in that same tree. Halo and Keycloak, and the install.