Legal

Open Source Software

The projects Fuego is built on

Fuego is a proprietary application, but it would not exist without open source software. This page credits the main projects Fuego is built on and the license each one is distributed under. It is a selection, not an exhaustive inventory: every one of these libraries depends on further open source packages in turn.

Desktop framework

Wails — packages the Go backend together with a web frontend rendered by the operating system’s native webview (MIT)

Backend

Go Firestore SDK and the Firebase Admin SDK for Go — everything Fuego does with Firestore, Authentication and Storage (Apache-2.0)
gRPC (Apache-2.0) and Protocol Buffers (BSD-3-Clause) — the transport the Firestore APIs speak
bbolt — the embedded database that stores your projects, views and preferences on your computer (MIT)
ONNX Runtime, through onnxruntime_go — runs the anonymization models directly on your computer (MIT)
The Gemini (Apache-2.0), OpenAI (Apache-2.0) and Anthropic (MIT) Go SDKs, the Agent Development Kit (Apache-2.0) and the Model Context Protocol SDK (Apache-2.0) — the AI assistant

Interface

Vue, with Vue Router, Pinia, Vue I18n and VueUse — the whole interface (MIT)
PrimeVue and Nuxt UI — the component libraries, styled with Tailwind CSS (MIT)
Monaco Editor — the JSON and query editors, the same editor that powers Visual Studio Code (MIT)
Chart.js for the dashboard charts (MIT) and Leaflet for geopoint maps (BSD-2-Clause)
Tabler Icons — the icon set (MIT)
Luxon for dates and times, and Lodash (MIT)

Licenses

Most of these projects are distributed under permissive licenses — mainly the MIT License, the Apache License 2.0 and the BSD licenses. The full text of each license, along with its copyright notices, ships with the corresponding package and is available from the project links above.

A small number of components are covered by the Mozilla Public License 2.0; the source code of those files is available unmodified from the projects that publish them.

Questions or corrections

The complete, resolved list of every package that goes into a Fuego build is described by the go.mod / go.sum and package-lock.json manifests used to compile it, and we are happy to share it on request. If you believe an attribution is missing or incorrect, please contact us and we will fix it.