KickSide/License
The KickSide Community License, in plain language
KickSide is source-available. The code is public, you can read it, change it, run it in production at any size, and fork it. It's licensed under Apache 2.0 with a small number of extra conditions. This page is the summary. The licence text is what counts, and it will be published in full at wippy.ai/license.
Pay us for KickSide and that's resale. Pay each other for work, and that's free.
If a third party pays you for access to KickSide, that is resale, and it needs a commercial licence.
If a third party pays you to build or run software that happens to run on KickSide, that is services, and it is free at any scale, with no notice to us and no cut of your revenue.
Build with it, sell what you build, keep the money.
Nearly every question about this licence is answered by working out which of those two sentences you are in. The rest of this page is just that rule applied to the cases that come up most.
Free, and what needs a licence
Free. No licence, no fee, no notice to us.
- Internal use by a company of any size, in production, with any number of users.
- Inside your own product, as long as KickSide itself isn't what your customer is paying for.
- Building for clients, including running a copy for a client who owns and controls it.
- Your own modules: build them, run them, publish them anywhere, public or private, free or paid.
- Installing modules from GitHub, GitLab or any public address, and building the connectors that do it.
- A private module registry for your own organisation.
- Forking KickSide and giving your fork away free, under a different name.
Needs a commercial licence
- Offering KickSide as a hosted or managed service that third parties pay to access.
- Embedding or white-labelling it where KickSide is what the customer is paying for.
- Reselling or sublicensing it.
- Selling a fork of it as a platform, toolkit or runtime under any name.
- Running a module registry as a paid or gated service for third parties.
We grant these as a matter of course to hosting and platform partners, including on a revenue share. Write to licensing@wippy.ai or tell us what you're building.
The details that come up
Is it open source?
Not by the Open Source Initiative's definition, and we don't call it that. It's source-available: Apache 2.0 with the conditions above. The engine underneath, the Wippy runtime, is open source under MPL-2.0 and is licensed separately.
What's an unverified module?
Anything installed from somewhere other than the Wippy Hub. It installs and runs normally. KickSide may show it as unverified, and verification, support and indemnity only apply to verified modules.
What counts as getting around the rules?
Faking verification, or removing the checks from a licensed module. Installing modules from another source is not that. Turning off telemetry or history sync is explicitly allowed.
Can the licence change on me?
Each version of KickSide keeps the licence it shipped with. A change only applies to versions released after it, so the copy you are running today cannot be relicensed out from under you.
What if we get it wrong?
You get written notice and thirty days to fix it. Rights come back once you do, the first time. We are trying to stop a hyperscaler reselling this, not catch you out.
Who does it apply to?
KickSide itself. It does not cover the Wippy runtime, the Wippy Hub, KickSide Cloud, or Module Suites from Spiral Scout, whether paid or free. Each of those has its own terms, listed below.