Getting started

The short way in, in three steps: open an archive that is already running, run one of your own, then put your own data in it. Nothing here needs you to read the papers first.

See one running

A live RankeDB serves an archive at archive.rankegraph.org, and opening it costs nothing. Ranke-Explorer draws the graph and lets you walk it claim by claim, and the same explorer ships inside every RankeDB release, ready to point at an instance of your own. What that particular archive records is described on the demo page.

Run your own

RankeDB ships as a single binary, built for macOS and Linux on both Intel and ARM. Take the one for your platform from the latest release, write a configuration naming the storage it should use, and run it. One process serves one archive, and that archive is described entirely by the configuration you hand it at launch.

Bring your data in

Data enters through adapters, small clients that talk to the server and map a source into claims. Today that means git: ranke-git imports a repository, whole history or single commit, and restores it byte-identical. Email and chat threads, issue trackers, CI build logs, and security scan reports are next.