# Datasets: status

> geolith Datasets is in development, not deployed. What exists today, what does not exist yet, and the checks that must pass before the label changes. As of 18 Nov 2026.

::warning
**Status: In development, not deployed.** As of 18 Nov 2026. The Datasets API is not a product yet. There is no dataset endpoint on api.geolith.app, no hosted API and no keys for datasets.
::

## Live

- **Rainfall pages.** The rainfall pages on geolith.app are [the first public pages built with the engine](https://geolith.app/data/in/rainfall): one page per India district and state, with embeds and share cards. Live since 18 Nov 2026.

## In development

- **Engine.** The `geolith dataset` command (`areas`, `normals`, `build`) turns CHIRPS v3 rainfall and Overture districts into a map layer and numbers per district. Its `--crosswalk` flag adds the official LGD district codes for India. It is on geolith/geolith `main`, not in a geolith release yet. See [Self-host](/datasets/overview#self-host).

## Not yet

- Greenness (NDVI).
- Downloads (CSV, Parquet, GeoParquet). When Datasets launches, file downloads will need the Scale plan, the highest plan.
- A Datasets API, keys for it and its plans.
- Uploading your own raster to a hosted service. This is not planned for the first version.

## Before the label changes

The label "In development, not deployed" stays until all of these pass:

1. The deployed numbers equal an independent reference within tolerance for every area.
2. Every output carries its attribution line.
3. A page with old data shows a warning.
4. The launch is approved.
