Downloads

What this page is

This page is the historical downloads index. It is kept at its original path so that older links continue to resolve. The contents have been written carefully - the page describes what the original distribution contained, what is available here, and what kind of state to expect anything in.

There is also a modern downloads page with the same information in a different shape. Both pages are accurate.

What was distributed historically

The original Ubigraph distribution included a viewer binary, a small set of example clients, and documentation. The viewer was the heavy piece. The examples were short. The documentation was a single document.

Three things to keep in mind:

• The distribution was platform-specific. There were builds for several common platforms but not for every combination of operating system and architecture.
• The distribution used a few system libraries that were normal at the time and are less normal today. Running an old binary on a current system sometimes works and sometimes does not.
• The examples were written against Python 2. Translating them to Python 3 is small work, covered on the docs index.

What is available here

This site does not host new binary builds and does not claim to. Anything on this page that points to a binary file is a pointer to historical material, with no claim that the file is the original untouched distribution unless that has been verified.

Three categories of file are likely to appear here as the site fills in:

1. Reference papers. Hosted at their original paths under /ubigraph/content/Papers/pdf/. Treat the files as references for the ideas they describe. The HTML companion pages under /papers/ summarise the contents.
2. Example clients. Short Python scripts that produce the demos. Translating these to Python 3 is straightforward.
3. Documentation. The text documents that accompanied the original distribution.

If a file you are expecting is not here, the most likely explanation is that we have not verified it yet. Email is on the contact page if you want to flag a specific file.

How files are verified

A file on this site that appears under a download link goes through three checks:

• Provenance. Where the file came from and how it reached us is recorded.
• Integrity. Hashes are recorded so the file can be re-verified at any time.
• Safety. The file is scanned against current malware databases. A file that fails this check is removed and not replaced until provenance can be re-established.

Files that have not passed all three checks are not posted as direct downloads, even if they exist on the file system. This is a stricter standard than older download portals used. It is the right standard for a site that mirrors older software in 2025.

Running older binaries on a current system

If you are trying to run a historical Ubigraph viewer on a current operating system, three observations are likely to apply:

• macOS. Older binaries are typically not signed in a way modern macOS accepts. You can sometimes work around this in the System Settings security panel. Sometimes you cannot.
• Linux. The viewer relied on a small set of libraries that have moved on since. Running the original binary inside a container with an older base image is usually more reliable than trying to satisfy the dependencies on a current host system.
• Windows. Older builds sometimes run in current Windows. The DPI scaling on modern displays may make the viewer harder to read.

None of those observations means the viewer cannot be used today. They mean that running it today is a small project of its own.

Practical alternatives

If you are reading this page because you want to do what Ubigraph did and the original viewer is not available to you, there are practical alternatives. They do not look or behave the same, but they cover the same problem.

The Ubigraph pillar page discusses this in more depth. The short version: any current force-directed graph viewer with a streaming API can be made to handle the same examples with a small adapter layer.

The graph visualisation alternatives lab note goes into specific tooling and the trade-offs.

Setup expectations

Whether you are working with the original viewer or a current substitute, the setup pattern is the same:

1. Start the viewer process and confirm it is listening on the expected port.
2. Run a small example client that creates a few vertices and edges. Confirm you see them in the viewer.
3. Run a slightly larger example that drives change continuously. Confirm the viewer keeps up.

If step 1 fails, the problem is environmental - the binary will not start, or the port is taken. If step 2 fails, the problem is the client side - the wrong host, the wrong protocol, or the wrong RPC path. If step 3 fails, the problem is performance - the viewer is starting but cannot keep up under load.

Splitting your debugging along those three steps will save you several hours.

A note on file naming

The historical file names are kept where the file is the original. New files added to this site are named clearly and dated where appropriate. We do not rename historical files to look more modern. We also do not invent historical file names for new content.

Where to go from here

• Docs index
• Demos index
• Papers
• Ubigraph pillar page
• Modern downloads page
• Graph visualisation alternatives lab note

If you came in from an old link, nothing has been moved. The downloads page lives at the same path it has always lived at.