earthflux

HOW IT WORKS

Open at the bottom. Hosted at the top.

The scientific engine and the services built on it evolve separately. Every result carries a recipe and provenance object you can persist, export and — where licensing allows — recompute.

  1. Decision surfacesWeb app · Scenario Lab · reports
  2. ServicesStress-Test API · jobs · audit trail
  3. Registry & provenanceRecipes · lineage · validation
  4. Computeclimate_indices · Rust · xarray/Dask
  5. Public dataNOAA · NASA · ERA5 · PRISM · CMIP
  • HOSTED

    Where we earn: scale, workflow, support

  • OPEN

    Always: algorithms, specs, public data

A hazard index is not a loss estimate.

We keep each layer of climate risk explicit, so nobody mistakes a drought percentile for a dollar figure.

  1. HazardWhat Earthflux computes: published, validated physical and statistical indices.
  2. ExposureWhat you bring: asset locations, polygons, operating areas and thresholds.
  3. VulnerabilityDomain models from partners — always named, never hidden inside a score.
  4. LossNever implied by an index alone. Only where a defensible damage model exists.

What’s free, what’s hosted.

We charge for hosted compute, workflow, integration, and support — never for the method or the result.

Free and hosted terms for the Registry, the Scenario Lab, the Feature Store, the Stress-Test API, and customer inputs.
SurfaceFree & openHosted & paidBuilt for
RegistryRead and query, with no accountNone — the Registry stays free to readResearch orgs, agencies, enterprises
Scenario LabExamples on published Curated DatasetsA Place assessment and its report-ready exportScientists, planners, consultants
Feature StorePlanned: read feature definitions and their Registry lineage, with no accountPlanned: hosted feature serving and support. Terms are not setML and data-science teams
Stress-Test APIPlanned: published-data compute at documented rate limitsHigher scale, integration, and supportEngineering, utilities, insurers, asset owners
Customer inputsYour own Pipeline on your own infrastructureOptional, planned Earthflux-hosted processingAgencies, regulated and technical teams

Commitments that don’t change.

Open science guides our work. We focus on reproducible methods, traceable sources, clear citations, and visible uncertainty.

  1. 01climate_indices stays permissively open and never requires Earthflux to compute.
  2. 02Provenance and validation conventions are published as open specifications.
  3. 03Software releases and key derived datasets get DOIs and citation workflows.
  4. 04Uncertainty and validation status are shown, never collapsed into one confidence badge.

What we’re building, in this order.

  1. NOW

    Registry & provenance schema

    Reproducible dataset pages and a published taxonomy for validation evidence.

  2. NEXT

    Scenario Lab beta

    User workspaces, an intercomparison harness and scenario datasets.

  3. NEXT

    Feature Store

    ML-ready features computed from Registry datasets, versioned and served with data, method, and validation lineage attached.

  4. LATER

    Stress-Test API

    Domain packages and compound-hazard methods with customer-specific validation.

Shape it with us.

Design partners help set validation priorities, reference datasets, and the first workflows.