Downloads

Use this page to select an explicitly published LyftData channel and version approved for your deployment. Match the archive to your operating system and architecture before starting the First pipeline guide. For a single-machine evaluation, download matching Product and Worker archives from one version folder, then follow the Evaluation Quickstart. LyftData 3.0 builds include archives for Linux (x86_64 and ARM64 GNU, plus x86_64 musl), macOS on Apple Silicon and Windows x86_64, and server Docker images for Linux amd64 and arm64. Use only the files listed for the version you choose.

Try now

Prefer the guided flow? Try now

Verify each download against the matching SHA256 checksum before you extract it.

For version-bound Linux setup and MCP recipes, use Set up with an assistant.

Which download do I need?

• Linux/macOS server + UI + CLI: download the Product (lyftdata-<target>) and Worker (lyftdata-worker-<target>) archives for one exact published version. Copy each full filename, including its published suffix (.tar.xz or .tar.gz); do not infer the suffix from another release. Install lyftdata from the Product archive and lyftdata-worker-job from the Worker archive in the same directory. The helper is required for Job execution with the built-in worker too; running the separate Worker daemon is optional.
• External worker host: download the matching Worker archive and keep lyftdata-worker and lyftdata-worker-job together.
• Windows: first confirm that the selected channel and version list matching Product and Worker ZIPs and their checksums, then follow the Windows installation instructions. An absent Windows asset is not a reason to switch channels silently.
• Docker: download lyftdata-server-docker-linux-<arch>.tar.xz and follow Docker and Docker Compose.

Find the exact version

Choose the channel approved for your deployment before downloading. A “latest” link can change; use a fixed version folder so that every file comes from the same published version:

1. Open RELEASE.json in the approved channel’s section. If it is unavailable, stop and confirm publication with the LyftData team.
2. Record its tag field (the exact version) and its source_path field (that version’s folder). Confirm that this is the version approved for your deployment.
3. Use the downloads site address followed by / and source_path as the version folder URL (release_url) in the install examples. Download every archive and its matching .sha256 file from that folder.
4. Check lyftdata --version against the recorded tag. Keep Product, Worker, and the Job helper on that same version and target.

Do not combine files from different versions or targets. Follow Prepare the binary for the exact extraction/copy steps; preserve both required executables when moving an installation.

Downloads portal

Use the downloads portal for published archives and SHA256 checksums in your approved channel. A Release heading does not establish that a 3.0 GA artifact has been published. If the selected channel or artifact is unavailable, stop and contact the LyftData team; do not substitute Beta for Release. Beta builds require an explicit decision to evaluate that channel.

Open downloads

Product documentation PDFs

Downloadable product documentation is available from the Downloadable Docs page, including the archived 2.1.0 PDF set. Those PDFs are historical documentation, not LyftData 3.0 GA documentation.