Multi-tenancy
A kernel per tenant. One gate each.
One OrchKernel deployment serves one organisation, and agencies run one per client. Multi-tenant hosting runs a separate kernel for each tenant.
How it works
One organisation per deployment
Each deployment of OrchKernel serves one organisation.
01
Your own organisation
Run one deployment for your company, on your own servers.
02
One deployment per client
Agencies and service firms run a separate deployment for each client organisation.
03
A kernel per tenant
Multi-tenant hosting, with a separate kernel for each tenant, so one host can serve many organisations.
The license
Why tenancy and the license go together
OrchKernel is source-available under the Business Source License 1.1. Its rule is one organisation per deployment.
01
Allowed
- Use, modify and run it in production for your own organisation.
- Operate a deployment for one client organisation.
- Run separate deployments for separate clients.
02
Needs a commercial license from OrchStack
- Offering OrchKernel, or a modified version, as a hosted or managed service in which one deployment serves more than one organisation.
That is multi-tenant hosting.
Each version becomes Apache-2.0 four years after it is first published. Client libraries are Apache-2.0.
Frequently Asked Questions
Need multi-tenant hosting?
Tell us how you would host OrchKernel, and we will set up the right license.
OrchKernel is source-available and self-hosted.