Requirements
What it needs to run.
One of three operating systems, and a folder you can write to.
That is the list. The rest of this page is what it does not need, because that is the part an approval normally has to cover.
The one requirement: a supported platform
Each platform has its own build. There is no common runtime underneath them, so a machine either has one of these operating systems or it is not supported.
- Windows, 64-bit · tested on Windows 11
Runs from any folder the user can write to, including a network share or a USB stick. - Linux, x86-64 · built and tested on Linux Mint
A single executable. Mark it executable and run it. - Raspberry Pi OS, 64-bit · tested on a Raspberry Pi 500+
The same program, compiled for ARM64.
No other platform is supported, and none is claimed. The three downloads →
What it does not need
Each of these is something an approval would otherwise have to establish, and each can be checked before anyone signs anything.
No installerNothing is installed: no files in Program Files, no settings in the registry or a user profile. No administrator rights, so no ticket to raise before the program can be tried.
No runtime to installNo Java, no .NET, nothing bundled. On Linux it uses the GTK libraries your distribution already ships and patches; on Windows, the system's own. You patch nothing extra.
No account, no telemetryNothing to register, nothing reported back. No subprocessor, so no data-processing agreement and no hosting question to answer.
No write access to the planThe program cannot alter a plan. A reviewer can state that the file they examined is the file they were sent.
What a rollout involves
Each line below is a step that does not apply, and each follows from the section above rather than from anything we promise.
DistributionCopy the file to a share, or send it. There is nothing to package for a deployment tool, nothing to run per machine, and no reboot.
UpdatesReplace the file. No update service, no agent, and no version that must be kept in step with a server.
Access controlNo user accounts, so no joiners-and-leavers process, no access reviews, and nothing to revoke when someone changes role.
DecommissioningDelete the file. The program leaves no settings in the registry, in a profile or on a server to clean up afterwards.
What this does not say is how long an approval takes. That depends on your own process; this page is about how little of it has anything to attach to.
What a reviewer can verify
Before it is run
Each archive's SHA-256 is published beside its download, so the bytes received can be checked against the bytes published. The program is not code-signed, and the download page says so.
While it is in use
It writes a file only when the user saves one — a chart image or a diagnostic dump, to a folder the user chooses — and keeps no settings of its own. The Open and Save dialogs are the operating system's, and like every program that uses them, they remember the last folder used. The only network request it makes is to an address the user types or clicks. Removing it is deleting the folder, so decommissioning is not a process.
The reasoning behind all of this is on the home page. A single file that installs nothing →
Why we built this project viewer
Ocean Consulting GmbH has worked on banking data warehouses, mobile-operator migrations and datacenter moves since 1999, writing the plans and steering the teams that worked to them. The viewer was built in 2018 on one of those projects, because half the team could not open the plan they were working to.