Released · improving
Move data while you watch the values
An ETL tool that gathers scattered operational data in one place. Wire it on a canvas in the browser IDE, test against real values, then schedule, verify and get notified.
What it is for
TASTEETL packs a command-line tool (tasteetl) and a browser IDE into one folder. Name sources and targets as datasets, wire columns on the mapping canvas with lookups, filters and expressions, decide where and how a job loads, and order and schedule jobs in workflows. Check, trace and dry-run show real values without writing anything, so nothing is built blind. Runs leave a run log, lineage and rejected rows; post-load verification, quality rules and scores, schema drift detection, failure alerts and daily summaries follow.
Explorer, tabs, canvas and a drawer (properties, preview, expression evaluator, messages, output) on one screen, in light and dark themes.
Drag to wire columns, attach lookups, add filters and expressions, and decide outputs and rejects. Node positions are saved next to the file.
Check, trace and dry-run push a few source rows through and show the real value in every node, without writing anything.
Chain jobs, set a condition on each link (success · failure · done), and choose parallel runs, retries and locks.
Run daily, hourly or weekly, at intervals, when a file arrives, when a signal comes, or after upstream jobs. Spot overlaps on the calendar.
Pick full reads, incremental (watermark), snapshot comparison or the transaction log (PostgreSQL wal · MySQL binlog · Oracle redo · SQL Server CDC) per source.
Reads and writes PostgreSQL, MySQL, MariaDB, SQLite, Oracle, SQL Server, Db2, Altibase, CSV, Excel, Parquet and HTTP.
Reconciles source and target by key, then records and reports missing, extra and mismatched rows.
Put rules on a dataset and every run adds to its score; the run stops when the score falls below the threshold.
Product value
Focused work
Verified release
We only show the version, platform, file size, signature status, and SHA-256 verified in the current manifest.
We don't promise unverified files or dates. You can check the current product scope in the docs.
View TASTEETL docsContinue
Other tools
When a source table's columns change, it stops, or warns and carries on.
Failed, filtered, not-found and blocked rows are kept in a file per kind; fix the values on screen and load them again.
Each run records rows read, written and failed, plus per-step counts, and two runs can be compared. Lineage shows where data came from and where it went.
Failures are reported by email, webhook or command, and a summary goes out every day.
Pin a version, open it run-only on the operations machine, and roll it back. Diagnostic bundles carry only definitions and history.
Developer, operator and remote-support roles. Once people are registered, screens appear only after sign-in, and tokens let outside systems call the API.
Discussion
Share feedback, questions, or your experience with the product. For bug reports, please use support.
Log in to leave feedback.
No feedback yet. Be the first to leave a review.