Licensing
What you may do with Beskos
The product is source-available: the code is public, you can run it, and after four years each released version becomes Apache 2.0. What it is not is a licence to resell it as a service. This page says which is which, in plain terms; the licence files in the repository are the text that governs.
Running it for your own organisation
Allowed, in production, with no seat limit and no fee. That includes your affiliates, and it includes paying an integrator to install, configure and support it for you. You do not need a licence key and you do not need an account with us.
Offering it to third parties as a service
Not allowed under the Business Source Licence. Making the product, or a substantial part of what it does, available to other people as a hosted, managed or embedded service needs a separate commercial licence. That is the one thing the licence exists to reserve, and it is what funds the rest being free.
The Pro features
Meeting recording, your own branding, organisation-wide security policies and organisation-wide AI agents live in the ee/ directories, under a separate licence, and are unlocked by a key issued per organisation. The key is not on sale yet and its price has not been announced; when it is, the key is verified offline and nothing calls home.
What happens after four years
Every released version converts to the Apache Licence 2.0 four years after its release. The clock runs per version, so the conversion is automatic and does not depend on us still being here to grant it.
Contributing
Pull requests are welcome. Once the contributor agreement is in place you will be asked to accept it on a first contribution; until then there is nothing to sign. You keep the copyright in what you write.