Strata Hub
Start with a working database.
Find the right dataset for your project, clone it, and start building.
Then open it with strata ./ml.
Strata Hub Dataset Catalog
Titanic PassengerstitanicPassenger records with raw and cleaned branches for classification demos.classificationJSONKV3branchesOpen
Passenger records from the 1912 RMS Titanic voyage - the canonical beginner classification dataset. This bundle carries the **complete** Kaggle "Titanic: Machine Learning from Disaster" distribution: all 1309 passengers, the official 891/418 train/test split, and the `gender_submission` baseline, restructured for Strata so the split and the curation steps are branches rather than a folder of CSVs.
Inside the database
- JSON
One document per passenger (passenger:<id>) with class, fare, embarkation, survival, and cabin fields.
- KV
Aggregates under meta: - survival rate, passenger counts.
- branches
raw keeps the nulls; cleaned imputes them, with every curation step preserved as document history.
A/B Test Resultsab-test-resultsA deterministic A/B test with each experiment arm on its own branch.ab testingJSONKV4branchesOpen
A synthetic, deterministic A/B test - one experiment, three arms - laid out so each arm lives on its own Strata branch (`control`, `variant-a`, `variant-b`). It exists to demonstrate the cross-branch comparison workflow: the same query, run per branch, is the entire analysis loop. ## What's in the data
Inside the database
- JSON
One document per session (session:<n>), plus a per-arm summary:metrics document.
- KV
The experiment definition under meta: - hypothesis, arm sizes.
- branches
control, variant-a, and variant-b forked from the shared definition - the same query per branch is the whole analysis.
World Bank Indicatorsworld-bank-indicatorsCountry-level population, GDP, and inflation records.reference dataJSONKV1branchOpen
Population, GDP, and inflation for every country and region the World Bank tracks, 2000-2025 - the "how big / how rich / how fast are prices moving" table agents reach for in analysis tasks, one document per country instead of six thousand API rows.
Inside the database
A detailed manifest has not been published for this dataset yet.
IANA HTTP Referenceiana-http-referenceHTTP status codes, methods, and headers as local lookup data.reference dataJSONKV1branchOpen
The three IANA HTTP registries - status codes, methods, and header fields - as one-read lookups. The reference an agent writing or debugging HTTP calls needs constantly, without bundling a copy or guessing from memory.
Inside the database
A detailed manifest has not been published for this dataset yet.
Iris FlowersirisFisher iris measurements with curation history included.classificationJSONKV1branchOpen
Fisher's 1936 iris measurements - the smallest, most familiar dataset in machine learning, restructured for Strata as a tutorial-grade bundle whose version history walks through the dataset's real, documented curation corrections.
Inside the database
- JSON
One document per flower (iris:<row>) with the four measurements and species - corrections visible via json history.
- KV
Per-species counts under meta:.
SemVer Test Corpussemver-test-corpus108 version strings with their validity verdict under Semantic Versioning 2.0.0, 45 ordered precedence pairs, and a full precedence ranking of every valid string - the edge cases dependency logic gets wrong, as one-read lookupsreference dataJSONKV1branchOpen
108 version strings with their validity verdict under Semantic Versioning 2.0.0, 45 ordered precedence pairs, and a full precedence ranking of every valid string - the edge cases dependency logic gets wrong, as one-read lookups. Plus a second branch that reads the same corpus through the tolerant dialect real tooling actually uses, so `v1.2.3` is one `--branch` flag away from being valid.
Inside the database
A detailed manifest has not been published for this dataset yet.
GitHub Eventsgithub-eventsDeveloper activity stored as append-only event streams.event streamEventsKV1branchOpen
GitHub Events-shaped developer activity - pushes, pull requests, issues, stars, forks - restructured for Strata as an append-only event log grouped into streams by event type, the natural shape for "what happened, in what order" questions over developer activity.
Inside the database
- Events
PushEvent, PullRequestEvent, IssuesEvent and more, in arrival order - the natural shape for what-happened-when questions.
- KV
Per-type event counts under meta:count:.
Agent Memory, With Experimentsagent-memory-with-experimentsSynthetic agent memory with retention-policy branches.agent memoryEventsJSONKV4branchesOpen
A fully synthetic, deterministic snapshot of a working AI agent's memory - episodic memories, an append-only event trace, and live working state - pre-forked into three experiment branches that each apply a different memory-retention policy, so you can compare retention strategies against identical starting conditions with a single clone. ## What's in the data
Inside the database
- JSON
Episodic memories (memory:episodic:<n>) plus live working state under state: - working memory, task queue, profile.
- Events
An append-only observation / tool_call / reflection trace with hash-chained sequence integrity.
- KV
Run metadata under meta: - seed, step count, policy notes.
- branches
Three retention policies forked from one baseline; the raw event log is identical on every branch.
SPDX License Referencespdx-license-referenceThe SPDX License List - 727 licenses and 84 exceptions, release 3.28.0 - as one-read lookupsreference dataJSONKV1branchOpen
The SPDX License List - 727 licenses and 84 exceptions, release 3.28.0 - as one-read lookups. What an agent reviewing dependencies, generating a NOTICE file, or gating redistribution needs from the list, without bundling a copy of it or recalling it from memory.
Inside the database
A detailed manifest has not been published for this dataset yet.
ISO Reference Codesiso-referenceCountry, currency, and language codes for local lookups.reference dataJSONKV1branchOpen
Country, currency, and language codes from three ISO standards, compiled directly into Strata as a lookup table - the small, dependency-free reference data an agent developer reaches for constantly and shouldn't have to bundle by hand.
Inside the database
- KV
Direct lookups - country:US, currency:JPY, language:fr - with catalog totals under meta:.
- JSON
A detail document per entry across all three code tables (249 countries, 178 currencies, 184 languages).
MovieLens 100Kmovielens-100kMovie records, catalog stats, and genre vectors for recommendation tests.recommendationJSONKVVectors2branchesOpen
The GroupLens MovieLens 100K catalog restructured across three Strata primitives - movie metadata as JSON documents, catalog aggregates as KV, and per-movie genre vectors in a similarity-searchable vector collection - so a single clone gives you a recommendation sandbox with no preprocessing step.
Inside the database
- JSON
One document per movie (movie:<id>) with title, year, genres, and rating summary stats.
- Vectors
Collection movie-genres - 19-dimension cosine vectors, so nearest-neighbor queries work right after clone.
- KV
Catalog aggregates under meta: - movie count, genre list, source id.
- branches
The sample branch trims the catalog to the ten most-rated movies - the small/full split without duplicating storage.
Strata Benchmark Resultsstrata-bench-resultsBenchmark runs stored as an event log.benchmarkingEventsJSONKV1branchOpen
Thirty real benchmark runs from Strata's own performance suite, replayed as an event log - a first-party history of how the engine's latency, scaling, and workload numbers moved across roughly two months of development, and a worked example of storing run history as events rather than a flat CSV.
Inside the database
- Events
latency, scaling, and workload suite runs in order - two months of the engine's own numbers.
- JSON
One full result document per run (run:<id>).
- KV
Latest-run pointers under meta:latest:.
Wikipedia ArticleswikipediaArticle metadata with a title-to-slug index.retrievalJSONKV1branchOpen
Wikipedia article metadata restructured for Strata as one JSON document per article, with a KV title-to-slug index over the top - the shape a future retrieval-augmented-generation corpus would build on once article text and embeddings are added.
Inside the database
- JSON
One document per article (article:<slug>) with title, categories, internal links, and word counts.
- KV
An exact-title index (title:<Title> → slug) plus catalog totals under meta:.
Stack Overflow Q&AstackoverflowPython Q&A threads as JSON documents with comments inline.qa retrievalJSONKV1branchOpen
Stack Overflow questions and answers restructured for Strata as JSON documents with their comment threads embedded inline, so a single `json get` returns a full discussion - no join against a separate comments table.
Inside the database
- JSON
Questions and answers keyed post:<id>, with their comment threads inline - no join against a comments table.
- KV
Per-tag post counts under meta:tag:.