Skip to main content

ETL with LLM operations.

Project description

📜 DocETL: Powering Complex Document Processing Pipelines

Website Documentation Discord Paper

DocETL Figure

DocETL is a tool for creating and executing data processing pipelines, especially suited for complex document processing tasks. It offers:

  1. An interactive UI playground for iterative prompt engineering and pipeline development
  2. A Python package for running production pipelines from the command line or Python code

💡 Need Help Writing Your Pipeline?
Want to use an LLM like ChatGPT or Claude to help you write your pipeline? See docetl.org/llms.txt for a big prompt you can copy paste into ChatGPT or Claude, before describing your task.

🌟 Community Projects

📚 Educational Resources

🚀 Getting Started

There are two main ways to use DocETL:

1. 🎮 DocWrangler, the Interactive UI Playground (Recommended for Development)

DocWrangler helps you iteratively develop your pipeline:

  • Experiment with different prompts and see results in real-time
  • Build your pipeline step by step
  • Export your finalized pipeline configuration for production use

DocWrangler

DocWrangler is hosted at docetl.org/playground. But to run the playground locally, you can either:

  • Use Docker (recommended for quick start): make docker
  • Set up the development environment manually

See the Playground Setup Guide for detailed instructions.

2. 📦 Python Package (For Production Use)

If you want to use DocETL as a Python package:

Prerequisites

  • Python 3.10 or later
  • OpenAI API key
pip install docetl

Create a .env file in your project directory:

OPENAI_API_KEY=your_api_key_here  # Required for LLM operations (or the key for the LLM of your choice)

⚠️ Important: Two Different .env Files

  • Root .env: Used by the backend Python server that executes DocETL pipelines
  • website/.env.local: Used by the frontend TypeScript code in DocWrangler (UI features like improve prompt and chatbot)

To see examples of how to use DocETL, check out the tutorial.

2. 🎮 DocWrangler Setup

To run DocWrangler locally, you have two options:

Option A: Using Docker (Recommended for Quick Start)

The easiest way to get the DocWrangler playground running:

  1. Create the required environment files:

Create .env in the root directory (for the backend Python server that executes pipelines):

OPENAI_API_KEY=your_api_key_here  # Used by DocETL pipeline execution engine
# BACKEND configuration
BACKEND_ALLOW_ORIGINS=http://localhost:3000,http://127.0.0.1:3000
BACKEND_HOST=localhost
BACKEND_PORT=8000
BACKEND_RELOAD=True

# FRONTEND configuration
FRONTEND_HOST=0.0.0.0
FRONTEND_PORT=3000

# Host port mapping for docker-compose (if not set, defaults are used in docker-compose.yml)
FRONTEND_DOCKER_COMPOSE_PORT=3031
BACKEND_DOCKER_COMPOSE_PORT=8081

# Supported text file encodings
TEXT_FILE_ENCODINGS=utf-8,latin1,cp1252,iso-8859-1

Create .env.local in the website directory (for DocWrangler UI features like improve prompt and chatbot):

OPENAI_API_KEY=sk-xxx  # Used by TypeScript features: improve prompt, chatbot, etc.
OPENAI_API_BASE=https://api.openai.com/v1
MODEL_NAME=gpt-4o-mini  # Model used by the UI assistant

NEXT_PUBLIC_BACKEND_HOST=localhost
NEXT_PUBLIC_BACKEND_PORT=8000
NEXT_PUBLIC_HOSTED_DOCWRANGLER=false
  1. Run Docker:
make docker

This will:

  • Create a Docker volume for persistent data
  • Build the DocETL image
  • Run the container with the UI accessible at http://localhost:3000

To clean up Docker resources (note that this will delete the Docker volume):

make docker-clean
AWS Bedrock

This framework supports integration with AWS Bedrock. To enable:

  1. Configure AWS credentials:
aws configure
  1. Test your AWS credentials:
make test-aws
  1. Run with AWS support:
AWS_PROFILE=your-profile AWS_REGION=your-region make docker

Or using Docker Compose:

AWS_PROFILE=your-profile AWS_REGION=your-region docker compose --profile aws up

Environment variables:

  • AWS_PROFILE: Your AWS CLI profile (default: 'default')
  • AWS_REGION: AWS region (default: 'us-west-2')

Bedrock models are pefixed with bedrock. See liteLLM docs for more details.

Option B: Manual Setup (Development)

For development or if you prefer not to use Docker:

  1. Clone the repository:
git clone https://github.com/ucbepic/docetl.git
cd docetl
  1. Set up environment variables in .env in the root/top-level directory (for the backend Python server):
OPENAI_API_KEY=your_api_key_here  # Used by DocETL pipeline execution engine
# BACKEND configuration
BACKEND_ALLOW_ORIGINS=http://localhost:3000,http://127.0.0.1:3000
BACKEND_HOST=localhost
BACKEND_PORT=8000
BACKEND_RELOAD=True

# FRONTEND configuration
FRONTEND_HOST=0.0.0.0
FRONTEND_PORT=3000

# Host port mapping for docker-compose (if not set, defaults are used in docker-compose.yml)
FRONTEND_DOCKER_COMPOSE_PORT=3031
BACKEND_DOCKER_COMPOSE_PORT=8081

# Supported text file encodings
TEXT_FILE_ENCODINGS=utf-8,latin1,cp1252,iso-8859-1

And create an .env.local file in the website directory (for DocWrangler UI features):

OPENAI_API_KEY=sk-xxx  # Used by TypeScript features: improve prompt, chatbot, etc.
OPENAI_API_BASE=https://api.openai.com/v1
MODEL_NAME=gpt-4o-mini  # Model used by the UI assistant

NEXT_PUBLIC_BACKEND_HOST=localhost
NEXT_PUBLIC_BACKEND_PORT=8000
NEXT_PUBLIC_HOSTED_DOCWRANGLER=false
  1. Install dependencies:
make install      # Install Python deps with uv and set up pre-commit
make install-ui   # Install UI dependencies

If you prefer using uv directly instead of Make:

curl -LsSf https://astral.sh/uv/install.sh | sh
uv sync --all-groups --all-extras
  1. Start the development server:
make run-ui-dev
  1. Visit http://localhost:3000/playground to access the interactive UI.

🛠️ Development Setup

If you're planning to contribute or modify DocETL, you can verify your setup by running the test suite:

make tests-basic  # Runs basic test suite (costs < $0.01 with OpenAI)

For detailed documentation and tutorials, visit our documentation.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

docetl-0.2.6.tar.gz (332.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

docetl-0.2.6-py3-none-any.whl (414.6 kB view details)

Uploaded Python 3

File details

Details for the file docetl-0.2.6.tar.gz.

File metadata

  • Download URL: docetl-0.2.6.tar.gz
  • Upload date:
  • Size: 332.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for docetl-0.2.6.tar.gz
Algorithm Hash digest
SHA256 e9180cd44a19401312d97a17026a26b10680b9762a303fe99df3e18569915623
MD5 ff9eaa96dfd47902f3fea41c798a8632
BLAKE2b-256 eecf0d01c6b3ebf785c6dda9bd97412befd3cc21aecc89a8c8dc9aa488a51848

See more details on using hashes here.

Provenance

The following attestation bundles were made for docetl-0.2.6.tar.gz:

Publisher: release.yml on ucbepic/docetl

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file docetl-0.2.6-py3-none-any.whl.

File metadata

  • Download URL: docetl-0.2.6-py3-none-any.whl
  • Upload date:
  • Size: 414.6 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for docetl-0.2.6-py3-none-any.whl
Algorithm Hash digest
SHA256 d3724c2dca935e1dad23ea221e5bef25224c443b65d194f44dc0e92ee0bb345e
MD5 4ace1c93b77e2bd902011272749bdc4e
BLAKE2b-256 f5abb55bc6220602918c039451544d830ad2f8299386b0a2831339bed653b7e0

See more details on using hashes here.

Provenance

The following attestation bundles were made for docetl-0.2.6-py3-none-any.whl:

Publisher: release.yml on ucbepic/docetl

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page