The product has to be runnable by someone who just discovered it. This page gives you the fastest paths: open the studio from source, bootstrap from a tagged GitHub release, or download the packaged assets directly.
Everything here is free and GitHub-native. The default experience is still local-first and zero-key.
This keeps the experience obvious: one command, browser opens, no key setup.
python app.py
Pulls the latest public release and installs the packaged binary.
curl -fsSL https://raw.githubusercontent.com/ByteWorthyLLC/honeypot-med/main/scripts/bootstrap/install.sh | bash
Downloads the latest tagged Windows package and adds it to the user path.
powershell -ExecutionPolicy Bypass -Command "iwr https://raw.githubusercontent.com/ByteWorthyLLC/honeypot-med/main/scripts/bootstrap/install.ps1 -UseBasicParsing | iex"
Useful when you want a clean demo environment without touching your local Python setup.
docker compose up --build studio
The links below hydrate from the latest GitHub release. If a card still says pending, the tag has not finished publishing yet.
The native package path for non-technical users who want a standard install flow.
Archive download for operators who prefer to inspect or redistribute the package manually.
Portable packaged binary for Linux hosts that want the public tagged build.
Portable Windows package when you do not want a full installer flow.
Release checksums for verification before internal distribution or security review.
Machine-readable inventory of every published asset, size, and SHA256 value.
The primary experience is unchanged: run locally, inspect the verdict, and export the proof bundle without API keys.
Open-source distribution gets more credible when the release page includes machine-readable assets and verifiable hashes.
People deciding whether a project is real look for a public install path, recent tags, and clean downloads.