Licenses
What's open source, under which license, and what that means for the code you deploy.
| License | Source | |
|---|---|---|
| The runner | AGPL-3.0 | zeroko-io/runner |
| The panel | MIT | zeroko-io/panel |
| The SDK | MIT | zeroko-io/sdk |
| Zeroko Cloud | Closed | Runs the runner for you, at zeroko.space |
The runner is copyleft so that it stays open: whoever improves it and offers it to others shares the improvement. Everything you build with or on top of it, the panel, the SDK and your services, is yours to license as you like.
Questions
Does the AGPL apply to the services I deploy?
No. A service is your own program: the runner runs it, as an operating system runs a program, without the two becoming one work. Its code, and what you build with the SDK, stay under whatever license you choose, open or closed, on Zeroko Cloud or on your own machine.
Can I self-host the runner for my company, or my customers?
Yes, for any purpose, commercial too. If you change the runner itself and let others use your changed version over a network, the AGPL asks you to offer them its source. Running it unchanged asks nothing of you.
Can I change the panel or the SDK and keep my changes private?
Yes: they're MIT. Keep the copyright notice, and that's all.
What isn't open?
Zeroko Cloud's own parts: the site and panel at zeroko.space, and the orchestrator that runs a runner per workspace. Self-hosting needs neither: the runner and the panel are the whole product for one machine.