Skip to main content

Culvert

A cloud-agnostic, polyglot data-pipeline framework. One contract set — Source, Sink, Transform, Pipeline, RuntimeContext, BlobStore, Warehouse, JobControlRepository, and friends — realised in Java and Python, with cloud specifics behind adapters. Define the pipeline once against contracts; point it at an emulator on your laptop, a dev project, or production by wiring, not rewriting.

  • Contract-driven — the language-neutral spec is the portability boundary. Business logic depends only on contracts.
  • Two clouds today — GCP is the first full implementation; AWS is a real (Java) adapter family with the same pipeline proven on both. Azure is on the roadmap.
  • No application framework in the core — plain Python Protocols + entry-point auto-discovery; composes into Beam pipelines, Airflow DAGs, or a script on your laptop.
  • Local-first — the whole stack runs against emulators with zero cloud account; cloud is where you prove and ship, not where you develop.

Install

pip install culvert                 # core contracts only (no cloud SDKs)
pip install culvert[gcp]            # + BigQuery, GCS, Pub/Sub, Secret Manager, observability
pip install culvert[orchestration]  # + Airflow-side DAG factory, operators, sensors
pip install culvert[transform]      # + dbt integration
pip install culvert[all]

Python ≥ 3.10. For 0.1.0 the import packages keep their library names — the contracts live in data_pipeline_core:

from data_pipeline_core import autoconfig

config = autoconfig.discover()          # entry-point adapter discovery
blob_store = config.blob_store()        # GcsBlobStore if culvert[gcp] installed

The Java twin ships as com.enrichmeai.culvert:* on Maven Central — same contracts, Java owns the Beam/Dataflow execution layer; Python owns the Airflow runtime and dbt packaging.

Status

0.1.0 — first public release. Built and validated against a real GCP project (Cloud Run, BigQuery, Pub/Sub, event-driven end-to-end) before publishing. GCP adapters are production-shaped; the AWS family is Java-side; Azure is a roadmap skeleton. Honest limitations are documented per adapter in the source.

Docs, architecture, worked example deployments, and the engineering story: https://github.com/enrichmeai/culvert

Apache-2.0 licensed.

Metadata

Release files for culvert 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for culvert 0.4.0
File Size Uploaded
culvert-0.4.0.tar.gz 139.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for culvert 0.4.0
File Interpreter ABI Platform
culvert-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 339.7 kB

Release files / culvert-0.4.0.tar.gz

Download URL culvert-0.4.0.tar.gz
Size 139.1 kB
Tags Source
SHA-256 checksum
How to use checksums
e8bc40096c2bf2199f9955cd5354a71083a3d5f7925c79182b9d0ea63bbae6fe
BLAKE2b-256 checksum
How to use checksums
75c50f3b70c715638d24d114d4d5f36200aa58f30baf9813b32628a7189afff1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.

Transparency log

Release files / culvert-0.4.0-py3-none-any.whl

Download URL culvert-0.4.0-py3-none-any.whl
Size 200.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5d9da634969d16abed057878f097f087fe01ea26daf05400b6b1937611efd185
BLAKE2b-256 checksum
How to use checksums
424b97a1eb0f64fe2f1a28f6830ad6868eb75eb79c826039b25e415686f89747
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.0

2 release files

This release

0.4.0 This release

2 release files

0.3.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page