pentaho/pentaho-kettle

Pentaho Data Integration ( ETL ) a.k.a Kettle

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 45 minutes ago
Added to GitGenius on September 7th, 2026
Created on October 8th, 2013
Open Issues & Pull Requests: 81 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 3,576
Total Stargazers: 8,387 (+0)
Total Subscribers: 452 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Pentaho Data Integration is an ETL tool that extracts, transforms, and loads data across diverse sources and destinations.

The tool addresses the need to move and process data between systems by providing a visual design environment where users build data pipelines through graphical composition. The engine executes these pipelines, with core plugins handling standard operations and extensibility mechanisms allowing custom transformations. The architecture separates concerns across a database dialog layer, user interface, core implementation, and pluggable engine extensions.

Organizations managing data warehousing, migration projects, or regular data synchronization tasks benefit from the tool's visual workflow design. It suits teams that need to orchestrate complex multi-step data operations without writing code for each transformation. The project includes both a desktop client and server deployment options, making it applicable to standalone analytics work and enterprise integration scenarios.

The project maintains a structured Maven-based build system with comprehensive testing infrastructure including unit tests, integration tests, and remote debugging capabilities. Contributions flow through pull requests linked to Jira cases, with checkstyle enforcement and test coverage expectations applied to incoming changes. The community directs support questions to a dedicated forum rather than handling them through issue channels.