In short
The one mistake that can end a business is reselling a project whose licence forbids it. This cheatsheet sorts the popular AI stacks into three columns: safe to white-label, client-install only, and read-the-licence-first.
The three columns
| Safe to white-label (MIT/Apache) | Client-install only | Read the licence first |
|---|---|---|
| LibreChat, Langflow, Letta | n8n (Sustainable Use) | Open WebUI (branding) |
| Qdrant, LiteLLM, Supabase | Dify (custom terms) | Cal.com (AGPL white-label) |
| RAGFlow, Activepieces | Flowise | Postiz, SearXNG |
The safe play when resale is barred
- Install on the client's own infrastructureTheir account, their server — you are a contractor, not a reseller.
- Charge for the install and the care planThis is normally permitted and is the high-margin default anyway.
- Keep the licence text with the installSave it per project; re-check before every release.
Rules that never change
- Never rely on memory — licences change between releases.
- AGPL is fine to self-host; obligations bite if you offer it as a service.
- For anything you strip and resell as your own, build on MIT/Apache only.
Get this as a PDF + future updates
Free. We'll email you the downloadable version and new resources as we publish them.