Licence
One repository. The whole directory.
Halo is the Go server, the console and the deploy files, in a single public tree under the Apache License 2.0. The guides are on this site. There is no second edition hiding behind a login.
- Licence
- Apache-2.0
- Editions
- One
- License key
- None
- Hosted cloud
- Not yet
The tree
The code is in the repository. The guides are here.
Sign-in, the console and the install live in the Halo repository. The guides that describe them are published on this site.
- 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.
- /docs/self-hostingThe installDocker Compose, the proxy and the install script. Backups, upgrades and rotating the secret key are in this guide.
- /docsThe guidesHow to run Halo and connect applications. They are published here, not in a folder of the Halo repository.
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.