Licensing
AIOS is open source. Running it inside your company is completely unrestricted, at any scale, however much you modify it — and that does not change.
The server is AGPL-3.0; the parts meant to live inside your own software are Apache-2.0. Both are OSI-approved open source licences.
What is under which licence
The Team Brain and the Workspace
AGPL-3.0The server side — the thing we host. AGPL is what stops someone selling hosted AIOS without contributing back.
SDKs, connectors and the design system
Apache-2.0Built to be embedded in your software, including commercial and closed-source. Copyleft would defeat the point.
The engineering harness
Apache-2.0It installs into your codebase. Adopting it never licenses your repository.
If your policy bans AGPL
We will give you a commercial licence at no charge for internal use. It covers running AIOS inside your organisation — as many users, as many instances, modified however you like — provided you are not offering it to third parties as a service.
There is no fee, no seat count, no expiry and no sales process. Email cn@fluora.ai with your organisation's name and we will send it. We answer within a couple of business days.
If instead you want to offer AIOS, or something derived from it, as a hosted service without the AGPL's obligations, that is a paid commercial licence — tell us what you are building and we will work something out.
Questions people actually ask
Can I use AIOS inside my company for free?
Yes, and without restriction. The AGPL creates no obligation for internal use — any number of people, any number of instances, modified as much as you like. You owe nobody source code, notification, or money. This is not a trial.
Do I have to publish anything if I self-host it?
No — not unless you do two things together: modify AIOS, and offer network access to your modified version to third parties. Running it unmodified publishes nothing. Modifying it for internal use publishes nothing.
Does AGPL affect my other software that calls the AIOS API?
No. The AGPL reaches code combined into the same program. Separate services talking over a network are ordinarily not that, and an HTTP API caller is the clearest case of it. Your application’s licence is entirely your own business.
What do I owe if I do modify it and host it for others?
The source of your modified AIOS, offered to the users of that service. Not your infrastructure, not your Terraform, not your other services, not your data or your prompts.
My company bans AGPL. What now?
Email us and we will give you a free commercial licence for internal use. No charge, no seat count, no expiry, no sales call. A blanket ban is usually a policy about licence text rather than about what you actually plan to do, and it should never be the reason you cannot try AIOS.
What about the older MIT versions?
They remain MIT, permanently. The change is going-forward only — nothing has been retracted, and the MIT text is preserved in each repository so the prior terms stay on the record.
Why did you change?
Straight answer: AIOS is self-hostable and our business is hosting it. AGPL keeps someone else from taking it, running it as a paid hosted service, and contributing nothing back. We picked AGPL over BUSL, SSPL or the Elastic Licence deliberately, because those are not open source and AGPL is — OSI-approved and listed by the FSF as free software.
Not answered here? Email cn@fluora.ai. We would rather answer it than have you guess.