When do I need a commercial license?

When your organization wants to modify LumaBrowser without publishing the modified source, combine it with proprietary software, build or ship private extensions, or needs warranty, indemnity or support terms the AGPL does not provide.

Does the commercial license unlock extra features?

No. The open edition and the commercial edition are the same code and the same installers. The commercial license is a contract, not a key.

Where is the source code?

On GitHub at github.com/amurgola/LumaBrowser, together with every release and its installers.

LumaBrowser 2.0 · GNU AGPL v3

LumaBrowser is open source.

The whole app is on GitHub: the browser, the local AI runtime manager, chat and agents, the Hub, the command line agent, the extensions, the docs and the tests. Every installer is built from that code and published next to it. Read it, build it, change it, and send improvements back.

View the source on GitHub Download

License: AGPL-3.0-or-later · Copyright Lumabyte, LLC · Commercial license available

The AGPL, in plain English

LumaBrowser is free software under the GNU Affero General Public License, version 3 or later. You may use it, study it, change it and redistribute it. The one string attached: improvements stay open.

You can, with nothing owed

Run the official builds at home or inside a company, on any number of machines.
Read every line, build it yourself, and audit what it sends where.
Modify it and publish your changes under the AGPL, including running your modified build as a service for others, as long as its users can get the source.
Write extensions and release them under the AGPL.

If you change it and share it

Distribute a modified version, or let other people use one over a network, and you must offer its source under the same license.
Mark a modified version as different from the original, and do not present it as an official LumaBrowser release or as coming from Lumabyte. This is the one additional term, allowed by section 7(c) of the AGPL.
Third-party components keep their own licenses, listed in THIRD-PARTY-LICENSES.

This page is a summary, not legal advice. The LICENSE file in the repository is what governs.

The commercial license

Lumabyte, LLC also offers LumaBrowser under a commercial license, for organizations the AGPL does not suit. Most people, and most companies, never need it.

Who does not need it

Anyone running the official, unmodified builds, at home or inside a company, on any number of machines.
Anyone modifying LumaBrowser and publishing those modifications under the AGPL.
Anyone writing extensions and releasing them under the AGPL.

Who needs it

Organizations that modify LumaBrowser and do not want to publish the modified source.
Organizations that combine it with proprietary software in a way the AGPL would treat as one work.
Organizations that build or ship private extensions. Extensions load inside the app's process and share its database, IPC and renderer, so they are normally derivative works under the AGPL.
Organizations that need warranty, indemnity or support terms.

A contract, not a key

The commercial license grants the right to use, modify and distribute LumaBrowser, and to keep modifications and extensions private, without the AGPL's source-disclosure obligations. The open edition and the commercial edition are the same code and the same installers. No feature is held back for it, and nothing in the app checks for it.

Scope, term and pricing are agreed per organization, and the agreement is sent on request. Email [email protected] with a line on what you are building.

Get involved

Report a bug

Open an issue on GitHub with your LumaBrowser version, your operating system and graphics card, and what you saw.

Send a pull request

Read CONTRIBUTING.md first. Because LumaBrowser is dual licensed, contributors sign a Contributor License Agreement once, by commenting on their first pull request.

Point your coding agent at it

Every code file has a matching page under Documentation/, with an index that lists them all in one line each, so Claude Code, Codex and friends can find their way around without reading the whole codebase.

Questions

Can my company use LumaBrowser for free?

Yes. Running the official, unmodified builds inside a company, on any number of machines, needs nothing from us.

Is anything missing from the open source version?

No. There is one codebase and one set of installers. The commercial license changes your obligations, not the software.

Where do the downloads come from?

Every installer is a release asset on GitHub Releases, next to the source it was built from. The download page links straight there and shows each file's SHA-256 checksum.

Can I build my own copy?

Yes. Clone the repository, run npm install and npm run dev. You need Node 20 and a C++ toolchain for the native SQLite module. If you share a modified build, mark it as unofficial.

What about ResonantJs and OpenGridJs?

Those are separate LumaByte libraries with their own licenses in their own repositories. See ResonantJs and OpenGridJs.