How the tools are built
Most of this catalog is native desktop software — six PySide6 applications on Windows and macOS, one built on Tauri and one on wxPython. The rest goes where a desktop program cannot: six Lightroom Classic plugins, a web app that installs nothing, and an Android app for car head units with no Play Store. Whatever the platform, they open fast and keep their data on your machine.
- Nothing phones home. No telemetry, no account, no licence server. Where a tool touches the network at all, it says what it contacts and why, and the privacy policy names each one.
- One version number per application, held in a single source and read back at runtime, so the number in the About dialog is the number that was built.
- Uncertainty is reported, not resolved. Several of these tools work on data where a confident wrong answer is worse than a flagged ambiguity, and they are written that way on purpose.
- Long operations show progress and can be cancelled, and batch runs end with real totals rather than a cheerful summary.
Releases and updates
The desktop applications that check for updates share one mechanism, which tries a local network share first and a public release channel second. A package is never executed before its checksum has been verified, and nothing installs without explicit confirmation. No credentials are embedded in any shipped application.
This site is the public record of what exists. Builds released to the public are on the downloads page, each file with its SHA-256 checksum; the rest stay in private distribution — see Access and releases for what each status means and how to ask about a build.
Licensing
Most of the catalog is released under the Apache License 2.0, copyright Bluebonnet Studios. Each tool page states the licence that applies to it, and names any bundled component or separately downloaded model whose own licence restricts how it may be used or redistributed. Where a licence has not been declared yet, the page says “Not stated” rather than implying one.
Where the name comes from
Lupinus texensis, the Texas bluebonnet: royal-cobalt petals, a pale banner spot that turns magenta once the flower has been pollinated, yellow-green buds at the top of the raceme that have not opened yet, and vivid grass underneath. That is the whole palette this site is built from, and the reason the mark is a flower on a stem rather than a logotype.
The status colours come from the same place, and mean what the flower means: grass for what is available, bud yellow for what has not opened, the pollinated magenta for what has been handed out on request, and no colour at all for what has not started.
