Skip to content

A data catalog for S3-compatible storage

See your S3 data and trace where it came from.

Browse several S3-compatible storages from one screen. A web tool for checking file contents, audio, capacity, and data lineage.

Switch connections and move through buckets and directories. The screenshots use public sample data.
The Storage screen with a directory README and the file list

Switch connections and move through buckets and directories. The screenshots use public sample data.

mado at a glance

Preview

View file contents

Check text, images, video, and audio in place. Files inside a tar open one by one, and text is colored by its format.

Using previews →
The file list with a JSON preview
The file list with a JSON preview

The file list with a JSON preview

Audio

Compare audio side by side

Inspect audio with its waveform and spectrogram. Put several tracks in the synchronized player and play them from the same position.

Audio and the synchronized player →
The synchronized player with waveforms of several tracks
The synchronized player with waveforms of several tracks

The synchronized player with waveforms of several tracks

Capacity

Track capacity over time

Size and object counts of each bucket are measured on a schedule. See the breakdown by directory and the trend, and compare the cost and time of moving data.

Capacity and transfer estimates →
Bucket capacity over time and the breakdown by directory
Bucket capacity over time and the breakdown by directory

Bucket capacity over time and the breakdown by directory

Dataset lineage

Trace data lineage

Which data was it made from, and by which processing? See Datasets, Jobs, and Runs as a graph and jump to where they are stored.

Dataset Lineage →
A Dataset Lineage graph from source data to processed data
A Dataset Lineage graph from source data to processed data

A Dataset Lineage graph from source data to processed data

Team note & README

Keep notes next to the data

A README for each directory and one Team note shared across the team. Write them in Markdown and review changes in the edit history.

README and Team note →
A Team note written in Markdown
A Team note written in Markdown

A Team note written in Markdown

Apache License 2.0