Rerun uses its own URL scheme to access information across the network.

The following schemes are supported: rerun+http://, rerun+https:// and rerun://, which is an alias for rerun+https://. These schemes are then converted on the fly to either http:// or https://. Rerun uses gRPC-based protocols under the hood, which means that the paths (/catalog, /recording/12345, …) are mapped to gRPC services and methods on the fly.

The following are examples of valid Rerun URIs:

for uri in [
    // Access the catalog server.
    "rerun://rerun.io",
    "rerun://rerun.io:51234/catalog",
    "rerun+http://localhost:51234/catalog",
    "rerun+https://localhost:51234/catalog",

    // Proxy to send messages to another viewer.
    "rerun+http://localhost:51234/proxy",

    // Links to a recording on the catalog server (optionally with timestamp).
    "rerun://127.0.0.1:1234/dataset/1830B33B45B963E7774455beb91701ae/data?segment_id=sid&time_range=timeline@1.23s..72s",

    // Links to a folder (dataset-name prefix) within the catalog.
    "rerun://rerun.io/folder/perception.detection",
] {
    assert!(uri.parse::<re_uri::RedapUri>().is_ok());
}

re_uri

Part of the rerun family of crates.

Parsing and constructing Rerun URIs (rerun://, rerun+http://, …).