Ionity (Pty) Ltd · AEDI · Free forever
Your whole dev environment, installed for you
Runtimes, editors, SDKs, shells, databases and AI tooling — installed on Windows, macOS or Linux in one run, then kept in sync and repaired for you.
Runtimes, editors, SDKs, shells, databases and AI tooling — installed on Windows, macOS or Linux in one run, then kept in sync and repaired for you.
No wizards to babysit, no half-finished PATH. Pick a profile, press go, walk away.
Over a hundred curated packages across runtimes, IDEs, shells, databases, embedded, ML and MCP tooling — resolved to winget, Chocolatey or Homebrew per machine.
Checks GitHub Releases on its own schedule, verifies each download against the published SHA-256, and updates itself in place.
A tray monitor for CPU, memory, disk and network, with live probing so you find out something broke before your build does.
Registry repair, PATH reconstruction and a dry-run mode that shows exactly what would change before a single byte moves.
The AI profile brings MCP servers, model runners and agent tooling in one pass instead of a weekend of README archaeology.
Node standard library only. Nothing to audit but the code you can already read, under Policy 986 AED.
ProGramerly opens in the IONITY Ai-OS operator layout: one ask box wired to the local model, the workstation DOME — five strata, 24 segments, drillable — stats, tiles and a dock. Every workspace and every Ionity tool opens as an app window over it.
Every build is produced on GitHub's own runners — Windows on windows-latest,
macOS on Apple's toolchain, Linux on ubuntu-latest — and published with a
SHA256.txt you can check before you run anything.
| Platform | File | Get it |
|---|---|---|
| Windows 10/11 (x64) | ProGramerly-Setup-*-x64.exe | Latest release |
| Windows (ARM64) | ProGramerly-Setup-*-arm64.exe | Latest release |
| Windows portable | ProGramerly-Portable-*.exe | Latest release |
| macOS (Apple Silicon) | ProGramerly-*-arm64.dmg | Latest release |
| macOS (Intel) | ProGramerly-*-x64.dmg | Latest release |
| Linux (any distro) | ProGramerly-*.AppImage | Latest release |
| Debian / Ubuntu | programerly_*_amd64.deb | Latest release |
| Fedora / RHEL / openSUSE | programerly-*.x86_64.rpm | Latest release |
| Checksums | SHA256.txt | Latest release |
Builds are currently unsigned: Windows shows “Windows protected your PC” → More info → Run anyway,
and macOS asks for right-click → Open the first time. On Linux nothing gets in your way — mark the
AppImage executable with chmod +x and run it, or install the package with
sudo apt install ./programerly_*_amd64.deb / sudo dnf install ./programerly-*.rpm.
Signing turns on automatically the moment the certificates are added to the repository secrets.
ProGramerly is the combined workstation: the Ionity tools below are built into it as capabilities of the Command Center, not shipped as separate downloads. They arrive with the Windows release, are pinned by size and SHA-256 inside the app, and are verified every time before they run.
Every fan channel with live RPM and duty, every temperature source, and a curve editor that shows what a curve would command beside what the fan is actually doing. Curves are designed and stored here; the driver-level apply belongs to the Ionity FanControl build (Fanzi).
ProGramerly is the IONITY Ai-OS shell: top bar, ask box, workstation dome, stats, tiles and dock — with every workspace opening as an app window over the deck.
The IONITY CiC workstation utility, one tile away in the Command Center.
The machine as navigable structure: Hardware, System, Storage, Toolchain, Intelligence — each segment bound to a real data set, scored live. 28 sets are registered as readable by the local model, each tagged measured, catalogue, manifest, state or computed, so every figure it quotes can be traced. Ten standing presets ask the questions worth asking the same way twice.
Ollama with a small default model (llama3.2:1b, about 1.3 GB, runs on CPU) so the copilot answers on a laptop without sending anything anywhere. Larger models are one click away in the AI workspace.
As soon as the shell is up, the local model reads the registered sets and reports on the deck — which model answered, how many sets it read, and the figures it took from each. Every workspace carries its own Ask control scoped to what that workspace covers, every preset is one click from the dock orb, and the whole dome can be written out as a Markdown report.