Osiris Pipeline
The deterministic compiler for AI-native data pipelines. You describe outcomes in plain English; Osiris compiles them into reproducible, production-ready manifests that run with the same behavior everywhere (local or cloud).
🚀 Quick Start
# Setup
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
# Initialize configuration
osiris init
# Start MCP server for AI integration (Claude Desktop, etc.)
osiris mcp
🎯 What Makes Osiris Different
- Compiler, not orchestrator - Others schedule what you hand-craft. Osiris generates, validates, and compiles pipelines from plain English.
- Determinism as a contract - Fingerprinted manifests guarantee reproducibility across environments.
- Conversational → executable - Describe intent; Osiris interrogates real systems and proposes a feasible plan.
- Run anywhere, same results - Transparent adapters deliver execution parity (local and E2B today).
- Boring by design - Predictable, explainable, portable — industrial-grade AI, not magical fragility.
📊 Visual Overview
Pipeline Execution Dashboard
Interactive HTML dashboard showing pipeline execution metrics and performance
Run Overview with E2B Integration
Comprehensive run overview showing E2B cloud execution with <1% overhead
Step-by-Step Pipeline Execution
Detailed view of pipeline steps with row counts and execution times
Example Usage via MCP
# Start the MCP server
$ osiris mcp
# Use with Claude Desktop or any MCP-compatible client to:
# - Discover database schemas and sample data
# - Generate SQL queries and transformations
# - Validate and compile pipelines
# - Execute with deterministic, reproducible results
# Or run pipelines directly:
$ osiris run examples/inactive_customers.yaml
✨ Key Features
- AI-native pipeline generation from plain English descriptions
- Deterministic compilation with fingerprinted, reproducible manifests
- Run anywhere with identical behavior (local or E2B cloud)
- Interactive HTML reports with comprehensive observability
- AI Operation Package (AIOP) for LLM-friendly debugging and analysis
- LLM-friendly with machine-readable documentation for AI assistants
🤖 LLM-Friendly Documentation
Osiris provides machine-readable documentation for AI assistants:
- For Users: Share
docs/user-guide/llms.txtwith ChatGPT/Claude to generate pipelines - For Developers: Use
docs/developer-guide/llms.txtfor AI-assisted development - Pro Mode: Customize AI behavior with
osiris dump-prompts --export
🚀 E2B Cloud Execution
Run pipelines in isolated E2B sandboxes with <1% overhead:
# Run in cloud sandbox
osiris run pipeline.yaml --e2b
# With custom resources
osiris run pipeline.yaml --e2b --e2b-cpu 4 --e2b-mem 8
See the User Guide for complete E2B documentation.
🤖 AI Operation Package (AIOP)
Every pipeline run automatically generates a comprehensive AI Operation Package for LLM analysis:
# View AIOP export after any run
osiris logs aiop --last
# Generate human-readable summary
osiris logs aiop --last --format md
# Configure in osiris.yaml
aiop:
enabled: true # Auto-export after each run
policy: core # ≤300KB for LLM consumption
AIOP provides four semantic layers for AI understanding:
- Evidence Layer: Timestamped events, metrics, and artifacts
- Semantic Layer: DAG structure and component relationships
- Narrative Layer: Natural language descriptions with citations
- Metadata Layer: LLM primer and configuration
See AIOP Architecture for details.
📚 Documentation
For comprehensive documentation, visit the Documentation Hub:
- Quickstart - 10-minute setup guide
- User Guide - Complete usage documentation
- Architecture - Technical deep-dive with diagrams
- Developer Guide - Module patterns and LLM contracts
- Examples - Ready-to-use pipelines
🚦 Roadmap
- v0.2.0 ✅ - Conversational agent, deterministic compiler, E2B parity
- v0.3.0 ✅ - AI Operation Package (AIOP) for LLM-friendly debugging
- v0.3.1 ✅ - Fixed validation warnings for ADR-0020 compliant configs
- v0.3.5 ✅ - GraphQL extractor, DuckDB processor, test infrastructure improvements
- v0.5.4 (Current) ✅ - CLI version display hotfix
- v0.5.3 ✅ - Python version requirement fix + CSV extractor runtime bug fix
- M2 - Production workflows, approvals, orchestrator integration
- M3 - Streaming, parallelism, enterprise scale
- M4 - Iceberg tables, intelligent DWH agent
See docs/roadmap/ for details.
🛠️ Contributing
See CONTRIBUTING.md for development workflow, code quality standards, and commit guidelines.
License
Apache-2.0
Metadata
Release files for osiris-pipeline 0.5.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| osiris_pipeline-0.5.7.tar.gz | 467.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| osiris_pipeline-0.5.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 975.2 kB
Release files / osiris_pipeline-0.5.7.tar.gz
| Download URL | osiris_pipeline-0.5.7.tar.gz |
|---|---|
| Size | 467.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8176ad444bd9a878d70e231b15fc31a430cdf229f370497db1904376e6ba31fa
|
|
BLAKE2b-256 checksum How to use checksums |
c7824704f253d1ddbe61e5543aa7d749fa0cdf15389ef719bb1760ce7d77af6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / osiris_pipeline-0.5.7-py3-none-any.whl
| Download URL | osiris_pipeline-0.5.7-py3-none-any.whl |
|---|---|
| Size | 508.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82620bbabed2fbd4b49c322de79f8c39468d6e15fa309d7fae9c2d3100cfbc49
|
|
BLAKE2b-256 checksum How to use checksums |
80d0535357cb66cbc9d44cfe9e63e05f0b8a00bae383b0484b4af88ffbbd4298
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for osiris-pipeline 0.5.7
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.