License & attribution

OpenWatari is released under the MIT License — free to use, modify, and redistribute, including commercially.

Do you need to “acquire” a license?

No. MIT is a public template, not something you buy or register. To adopt it you keep the LICENSE file (with its copyright line) in copies of the code. That's the whole obligation for your own code.

Dependencies keep their own licenses

Almost all are permissive (MIT / BSD / Apache-2.0 / Unlicense) and ask only that you retain their notices — that's what THIRD_PARTY_NOTICES.md is for. The one copyleft dependency is py-tgcalls / ntgcalls (LGPL-3.0), pulled in only by the optional channels extra for streaming music into a Telegram voice chat. Using it as an unmodified pip library is compatible with shipping your own MIT code; omit it for a 100%-permissive stack (Telegram text still works via MIT-licensed Telethon).

Cloud services are Terms of Service, not licenses

ElevenLabs, Deepgram, your OpenAI-compatible LLM provider, Tavily, Google, Notion, Home Assistant, GitHub, ntfy — these are bring-your-own-key services governed by their own Terms, which you accept when you sign up. The framework ships no keys.

Naming & trademark

The project is OpenWatari and the assistant is Watari — names chosen so the public brand doesn't rely on a franchise-associated mark. Jarvis is referenced only as the blueprint/inspiration and is not used as the project's brand; the internal package keeps the code identifier jarvis. MIT grants copyright, not trademark — if you fork under a different public name, make it your own.

Before a public release, run uvx pip-licenses --format=markdown over your locked environment as a final check.