Scheduled pipelines
Jobs that move data between systems on a timetable.
We have no published Airflow build. Airflow 2 reached end of life on 22 April 2026, and we show the nearest Python and reporting work and the move to Airflow 3.
Jobs that move data between systems on a timetable.
Pipelines moved off a version that no longer gets fixes.
Data prepared for reports, as on the Power BI builds.
Docker multi-stage builds, the pattern on TruckFleet.
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
Source: Apache Airflow documentation, Version life cycle, checked 3 November 2026.

Azure SQL data feeding PDF certificates and Power BI dashboards, the reporting half of a pipeline.
MQTT telematics normalised before storage, with Redis, PostgreSQL and a Python 3.13 back end.
Python
Docker
Kubernetes
AWS
Azure
PyTorchNo. The Airflow project lists Airflow 2 as end of life on 22 April 2026, after limited maintenance from 22 October 2025. End-of-life versions get no fixes or support.
No. We say so on the first call and show the nearest work, which is Python data builds and Power BI reporting.
Airflow 3, first released on 22 April 2025, with 3.3.2 current. The project advises installing the latest release.
You do, from the first commit. Repositories and cloud accounts stay in your name.
Thirty minutes on your jobs, your schedules and your Airflow version. No sales pitch.