Skip to content
datastore.sh

Pricing

One price sheet. Archives one-time, streams monthly.

Pricing is uniform across the catalog: archives are priced by how far back you need, streams by the pipeline. No seats, no metered queries, no surprises on the invoice.

01 · Coverage window

Latest month

The most recent month of history

$200/ dataset

Choose a dataset

02 · Coverage window

Last 6 months

The most recent six months of history

$500/ dataset

Choose a dataset

03 · Coverage window

Last 12 months

The most recent year of history

$1,000/ dataset

Choose a dataset

04 · Coverage window

Full history

Complete archive since genesis

$2,000/ dataset

Choose a dataset

Prices in USD per dataset. Purchases are one-time; payment is processed by Stripe on the dataset page.

Streams · live delivery

Live pipelines, priced per pipeline

A stream is one dataset delivered continuously into one sink you control — Kafka, ClickHouse, NATS JetStream, or S3. 24 datasets are streamable today; subscribe on any dataset page.

Starter

$99/ pipeline / month

  • 1 pipeline · 1 destination
  • All tables in the dataset
  • Start from chain head or a chosen block
  • Delivery-health status page
Choose a dataset

Pro

$299/ pipeline / month

  • 1 pipeline · 1 destination, priority capacity
  • All tables; custom table selection on request
  • Backfill + Tail: start at your archive's final block
  • Named engineer contact for the pipeline
Choose a dataset

Backfill + Tail

Archive + stream, stitched at one block

Buying the archive and the stream together? The stream starts at the exact block your archive ends — one schema, no gap, no overlap.

  • Every table in the dataset, live, into a sink you control
  • Cursor-committed delivery — the pipeline resumes exactly where it stopped
  • Gap and duplicate-risk tracking with a per-pipeline delivery-health record
How streams work

Archive price + stream subscription; the seam is guaranteed by a shared block number. Cancel any month.

Included with every purchase

The files, and everything needed to trust them

  • Every table in the dataset — one purchase covers them all
  • Partitioned, versioned Parquet files for the selected window
  • Per-table manifests with schema, lineage, and checksums
  • Corrections republished as new versions for the purchased window

Need more than a window?

Enterprise arrangements

Catalog-wide licensing, archives kept current with scheduled drops into your own S3 or GCS, invoicing and procurement support, and private delivery pipelines.

Questions buyers actually ask

What exactly am I buying?
A license to the selected coverage window of one dataset, delivered as partitioned, versioned Parquet files with the manifest and schema documentation. You download and keep the files.
How is the data delivered?
After payment, we deliver signed download links to your checkout email. Enterprise buyers can also receive drops directly into their own S3 or GCS buckets.
What happens when the dataset is corrected?
Corrections are republished as new immutable versions. If a correction affects a window you purchased, you receive the corrected version at no cost.
Do prices differ per dataset?
No — pricing is uniform across the catalog at launch. Every dataset uses the same four coverage windows.
What about ongoing updates after I buy?
A purchase covers a fixed historical window. If you need the archive kept current with scheduled drops into your cloud, talk to us about an enterprise arrangement.
Can I get an invoice or pay by wire?
Yes. Checkout runs on Stripe with card payment; for invoicing, wire transfer, or procurement paperwork, email orders@datastore.sh.
How does a stream subscription work?
You subscribe on the dataset page, then connect your sink through a secure link we email after payment. We verify credentials with a live test write, and the pipeline starts — typically within a few hours. Cancel any month; the pipeline stops at the end of the billing period.
What does “Backfill + Tail” guarantee, exactly?
When your archive is fulfilled we record its final block. Your stream's cursor starts at the next block, on the same schema version. Zero gap, zero overlap — a number both deliveries share, verifiable in your sink.
Is stream delivery exactly-once?
Delivery is at-least-once with deterministic dedup keys per message, plus continuous gap tracking and a public delivery-health record per pipeline. That combination is what lets your sink enforce exactly-once — honestly.