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.3.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.3.0
File Size Uploaded
culvert-0.3.0.tar.gz 139.1 kB Details

Built distribution (wheel)

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

Total release size: 339.7 kB

Release files / culvert-0.3.0.tar.gz

Download URL culvert-0.3.0.tar.gz
Size 139.1 kB
Tags Source
SHA-256 checksum
How to use checksums
8c6ade35a6ea5279f740206b24074f5db6f69e2990bd588c92644a116cf714be
BLAKE2b-256 checksum
How to use checksums
126bca0cf0d554ec43bf1e0f9aa6a94b4d42fac1a38384019dbcffdd998f6c4d
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 2, 2026.

Transparency log

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

Download URL culvert-0.3.0-py3-none-any.whl
Size 200.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a9a4e622ca5a6e1146217d36f43eb72959bb1b98c1763281baf7cef58b25eff5
BLAKE2b-256 checksum
How to use checksums
c2dd6dd442543ae5d714776ca2d0d047b184fcbb08d73ca6e45add6b7c2c027f
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 2, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.0

2 release files

0.4.0

2 release files

This release

0.3.0 This release

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