Update the tooling, keep your license
No-license downloads for Linux and Windows, a Windows CLI to match the Linux one, and no form to fill in. For teams refreshing their tooling.
If you run Etlworks on-premise, you have hit this. A new CLI command shipped, or the installer picked up a fix. To get either you had to request a fresh installer bundle that arrived with a license you did not need, because you already have one.
That is fixed, along with a gap on the Windows side.
Two direct downloads, no form
The installer and command-line tools now download with no license bundled:
# Linux — returns etlworks-installer.tar.gz
https://etlworks.com/installers/download/no-license
# Windows — returns etlworks-installer.zip
https://etlworks.com/installers/download/no-license?os=windowsNo name, no company, no email. We ask for those on the trial flow because the backend uses them to generate a license. That is the entire reason the form exists. No license, nothing to collect.
Your existing license and configuration are untouched. These archives refresh the installer and the tooling around it, nothing else.
Both are on the site if you would rather click than curl: Installer & CLI tools.
A Windows CLI, finally
The Linux CLI became the way a lot of teams operate Etlworks on-premise: backups, log monitoring, routine maintenance, all driven from cron and shell scripts. Windows shops have been scripting around its absence.
The same tooling now ships for Windows as etlworks-cli.ps1 and etlworks-cli.bat, with parity across both platforms. It arrives with the Windows installer at 1.4.9 and later. A team running both no longer maintains two mental models or two sets of runbooks.
The Linux CLI gained capability in the same release, aimed at the same work: full backup and restore of PostgreSQL, Redis, and app.data, plus persistent suspend and resume of flow executions.
Why not re-download everything
Because the platform artifacts are large and you almost never need them.
The upgrade that matters to an operations team is usually the tooling. A CLI that performs the backup you have been scripting by hand, or an installer that handles a new OS version. Pulling several hundred megabytes of platform artifacts to get a better backup command is a bad trade, especially where every download goes through a change process.
Splitting these out means the operational surface updates on its own schedule, independent of platform upgrades.
Which download you actually want
There are three paths now. Pick by what you need:
| You are | Use |
|---|---|
| New to Etlworks, or want a trial | Request a trial installer. Ships with a 14-day license, emailed in seconds |
| Already running Etlworks, updating tooling | Installer & CLI tools. No form, no license |
| Just need a license for Docker or a renewal | Request a license-only download, or take it from your account in the app |
Notes for change control
A few things worth knowing before this goes through an approval process.
The no-license archives contain the installer and CLI tooling. They carry no license, so an install from these alone will not activate. Nothing about your existing configuration, flows, or license changes by downloading or unpacking them. And the endpoints are plain HTTPS with no authentication, so they work from a build agent or a locked-down jump host with no credentials in the pipeline.
Installation and upgrade steps have not changed. The on-premise guide still covers Linux, Windows, and Docker.