Run Python scripts from your TypeScript background tasks using our Python build extension. No separate Python server. No complex orchestration. Just add your .py files and go. 🧵

The problem: Python has the best ML/data libs. But orchestrating Python workers (Celery, RQ) means managing Redis, separate deployments, different observability.

Dependencies installed at build time. Scripts bundled automatically.

There are two execution modes: - Inline - Or run a script file with args Returns stdout, stderr, exit code. Streaming output also supported.

The value: mix ecosystems in one task. No IPC. No message queues. Just sequential code.

→ vs traditional task queues: No Redis or message broker to configure. No separate worker pool to deploy and scale. Works natively with your TypeScript codebase. → vs serverless functions: Not a separate deployment target. Tasks run with full access to your application context, types, and shared code. → vs running scripts in production: We handle container orchestration, dependency management, and dev/prod parity automatically.

Check out our practical guides in our docs: - Web scraping with Crawl4AI + Playwright - Image processing with Pillow → S3 - PDF form extraction with PyMuPDF - Doc conversion with Microsoft's MarkItDown All TypeScript orchestration with Python execution. trigger.dev/docs/guides/