GHCup

GHCup is a free installer and version manager for Haskell’s core tools. It is best for developers who want to manage GHC, cabal-install, HLS and Stack across their development environments. Its narrow focus is a strength, but the lack of automatic project switching and the caveats around Windows and ARM make it a less complete fit for some setups.

Overview

GHCup brings several central parts of a Haskell toolchain under one manager, rather than asking developers to handle each tool’s versions separately. That focus makes it a practical choice for Haskell work; it is not a general project environment manager, and it does not pin tool versions to individual projects or switch them automatically.

Key features

GHCup installs and manages GHC, cabal-install, Haskell Language Server (HLS) and Stack. Stack can be configured to use GHC versions managed by GHCup, which helps keep those parts of a setup aligned. Shell integration and CI/CD use are supported, while the FAQ also identifies a text interface and GHC cross-compilation. Configuration can be stored in ~/.ghcup/config.yaml; command-line options override its settings.

The missing project pinning and automatic switching matter for developers who expect each repository to select its own compiler and tools. GHCup can manage versions, but that alone does not provide that per-project workflow. There is also an HLS caveat when Stack setup-info metadata is used: compatible HLS binaries are not guaranteed, and the latest and recommended shortcuts do not work.

Pricing

GHCup costs nothing. Its free plan covers Haskell toolchain installation and management, and the project is open source. There is no paid tier or trial to weigh; its cost advantage comes with a focused scope rather than a broader set of environment-management features.

Platforms

Installation instructions cover Linux, macOS, FreeBSD, WSL2 and Windows, but support is not uniform. WSL1 is unsupported, and macOS releases earlier than 10.13 are outside the supported range. On Unix-like systems, the installer should be run as a non-root user; on Windows, use a non-admin account. macOS may prompt for command line tools, and Windows installation should set up msys2.

Windows support is described as being in early stages, with a shim wrapper used because Windows does not handle symbolic links properly. GHCup relies on precompiled binaries, which can fail when a system lacks libtinfo or has other distribution compatibility problems. Linux support is for distributions compatible with upstream GHC binaries. HLS bindists on macOS aarch64 and Stack and HLS binaries on Linux ARM are experimental, so those environments carry extra uncertainty.

Who it's for

GHCup suits Haskell developers who want a free, dedicated way to install and manage the language’s main compiler and supporting tools, including in CI/CD workflows. It is a stronger fit for users whose systems match the supported binary environments and who are comfortable managing versions without automatic project-level selection. Those needing WSL1 support, older macOS compatibility, or mature Windows and ARM binary support should consider their environment carefully.

Pros and cons

• Pros: One manager handles GHC, cabal-install, HLS and Stack, reducing the need to manage these core Haskell tools separately.
• Pros: Free, open-source use includes shell integration and CI/CD support.
• Pros: Stack can use GHCup-managed GHC versions, and the tool also supports a text interface and GHC cross-compilation.
• Cons: No project version pinning or automatic switching means versions are not selected per project by GHCup.
• Cons: Experimental ARM and macOS aarch64 binaries, early-stage Windows support and binary compatibility issues can complicate installation on some systems.
• Cons: Stack setup-info metadata does not guarantee compatible HLS binaries, and disables the latest and recommended shortcuts.

Alternatives

For a broader development-environment manager, compare Development Environment Managers; for tools centered on managing runtime versions, see Runtime Version Managers.

ActiveState Platform has a free organization plan limited to public projects and a paid enterprise option with custom pricing; choose it if those organization-focused terms suit your work. devenv is a free, MIT-licensed option that requires Nix and works on Linux, macOS and WSL, making it relevant if you want a Nix-based setup. Flox offers a free Personal plan with its CLI, catalog access, unlimited public environments and three private environments; consider it if those environment features suit your needs.

frum is a free Ruby version manager, while FVM is a free open-source Flutter SDK version manager. Jabba is a free Java version management tool under Apache License 2.0, and vfox is free and Apache 2.0 licensed. DDEV is free and open source under Apache 2.0.

Verdict

Choose GHCup if you need a free, focused manager for Haskell’s core toolchain and your platform fits its binary support. The key reason to choose something else is the lack of automatic project-specific version selection; Windows and experimental ARM support are further reasons to check fit before committing.