Answer in Collibra before the question.
Your auditor asks where a regulatory number came from. With the agent, the answer is in Collibra before the question gets to your team. Audit cycle becomes a review.
All agents
Lineage Documentation · Compliance & Orchestration
Lineage your auditors accept on the first pass.
Your regulatory analysts spend three weeks of every audit cycle tracing data lineage from Pentaho ETL to Collibra by hand. Multiply by every reporting cycle, every model retrain, every regulator inquiry. The agent scans your Pentaho ETL, resolves properties files, queries Collibra for existing metadata, and generates field-level lineage at app, table, and column resolution. Continuously updated.
SOC 2 Type IIOperates on ETL source files onlyNo production data access requiredField-level lineage
Watch a real lineage run, end to end.
Scan Pentaho ETL
Source.kjb / .ktr files
Resolve & query
Properties resolved · metadata queried
Environment configresolved
Collibra metadata
Generate lineage
ResolutionAppTableColumn
Upload & visualize
Upload CSV→Collibra
Visual lineage→Auto-generated
Field-level lineage
Pentaho ETL
Lineage generated
App level
Table level
Column level
Citations
Properties resolved● Complete
Production access● None required
Uploaded to Collibra, visual lineage live
continuously updated · regulator-ready
Per-run log · timestamped, reproducible
01Scanned your Pentaho .kjb / .ktr source files
02Resolved properties placeholders against your config
03Queried Collibra for existing metadata
04Generated field-level lineage at app, table, column
05Uploaded the CSV to Collibra
06Visualized lineage, continuously updated on change
DataworkzNo production data access required
60 seconds. It scans a folder of Pentaho .kjb / .ktr files. Properties placeholders resolved. Collibra queried for existing metadata. Field-level lineage CSV generated. Uploaded to Collibra. Visual lineage auto-generates at app, table, and column level. Three weeks of analyst work, completed in minutes.
Try it now
How it works
Three steps from Pentaho ETL to populated Collibra.
01
Scan and resolve.
It parses your Pentaho .kjb / .ktr files. Properties file placeholders resolved against your environment configuration. Existing metadata queried from Collibra.
02
Generate field-level lineage.
Structured lineage mappings synthesized at app, table, and column resolution. CSV output formatted for direct Collibra upload.
03
Upload and visualize.
CSV uploaded to Collibra. Visual lineage auto-generates. Continuously updated as your ETL changes.
Capabilities that earn their place.
Pentaho ETL parsing
.kjb and .ktr files parsed natively, including the transformation steps inside each job.
Properties file resolution
Environment placeholders resolved automatically. No analyst rework.
Extensible to other ETL toolchains
Pattern works with Informatica, Talend, Alteryx and other catalogs on a per-deployment basis.
Field-level lineage
App, table, column resolution. Granularity your regulators expect.
Collibra-native CSV output
Direct upload format. No middleware required.
Continuously updated
New Pentaho jobs trigger lineage updates automatically. Audit-readiness stops being quarterly.
Regulator-ready output
Lineage structured at the granularity audit and compliance reviews expect.
No production system access
Operates on ETL source files only. Safe for regulated environments.
vs. the alternative
Three ways teams handle regulatory lineage.
| Dimension | Regulatory analyst tracing by hand | Collibra native cataloging | Lineage Documentation |
|---|---|---|---|
| Time per cycle | 2–4 weeks of analyst time. | Manual entry per asset. | Minutes per run. Continuously updated. |
| Field-level resolution | Yes, where the analyst gets to. | Manual, where someone catalogs. | App, table, column. |
| Pentaho ETL parsing | Manual. | Not native. | Native. |
| Properties resolution | Manual. Source of error. | Not handled. | Automatic. |
| Regulator-granularity lineage | Depends on analyst diligence. | Depends on cataloging discipline. | Complete by design. |
| Audit-cycle effort | Quarterly fire drill. | Quarterly cataloging review. | Continuous. Audit cycle becomes a review, not a build. |
Four ways D&A and compliance leaders hire Lineage Documentation.
Field-level lineage at regulator granularity.
Regulatory reporting requires field-level lineage. The agent produces it at the granularity regulators expect, continuously updated.
Structured lineage as a side effect.
Your Pentaho codebase has hundreds of jobs and limited documentation. The agent produces structured lineage as a side effect of running.
Trace training data to source.
When your AI governance committee asks where the model's training data came from, the agent produces the answer back to source ETL.
Built for your security review.
Three deployment optionsSOC 2 Type IINo production data accessField-level lineageAudit-safe by defaultBYO LLM
It operates on ETL source files only, not production data. Lineage stays where you specify. Output is structured for direct regulator review. Every run is logged. Your CISO and your compliance team read the same posture.
Questions D&A and compliance leaders ask us.
It scans your Pentaho ETL source files, resolves properties placeholders, queries Collibra for existing metadata, and generates field-level lineage at app, table, and column resolution. Output uploads directly to Collibra and auto-visualizes.
The current native integration is Pentaho. The pattern extends to Informatica, Talend, and Alteryx on a per-deployment basis. Confirm your ETL stack during evaluation.
The current native integration is Collibra. The output format is configurable for other catalogs (Alation, IBM, etc.) on a per-deployment basis.
First-run timing depends on the size of your ETL codebase. Most enterprises see initial lineage in Collibra within two weeks of deployment. Continuous updates run on every change.
Yes. Output is structured at app, table, and column resolution for direct regulator review.
Collibra's lineage tools rely on metadata you've already cataloged. The agent automates the upstream extraction from your Pentaho ETL: the work that populates Collibra in the first place.
Yes. It parses Pentaho .kjb and .ktr files natively. Custom transformations are handled by the agent's reasoning over the source. Edge cases flag for analyst review rather than guess.
Lineage your auditors accept on the first pass.
The audit cycle that consumes three weeks of analyst time. The Pentaho ETL nobody wants to read. The Collibra catalog that's perpetually behind. It closes the loop. Continuously updated, ready for the regulator's next inquiry.
30 minutes. Bring a Pentaho job from your environment. We'll walk through the lineage the agent produces.