The Patchbay_

VCV Rack vs Cardinal

Cardinal is a fork of VCV Rack built to be completely free and to run as a plugin. Same modular concept, different licensing philosophy and a different deployment story.

Short answer. Want the biggest module library and commercial modules → VCV Rack. Want it as a DAW plugin, fully open, or on Linux with no proprietary parts → Cardinal.

Side by side

VCV Rack Cardinal
Runs as a pluginRack Pro (paid)Yes — free
LicenceGPL core, proprietary modules existFully open
Module libraryLargest, incl. commercialBundled open modules only
CostFree standalone; Pro is paidFree
Module installationPlugin managerBundled — no separate installs
Self-containedNoYes — everything included
LanguageC++C++
LicenseGPL-3.0-onlyGPL-3.0-or-later
PlatformsmacOS Windows LinuxmacOS Windows Linux Web
First released20172022
MaintainedYesYes

Where they actually differ

Plugin use is free in Cardinal

Running VCV Rack inside a DAW requires Rack Pro, which is paid. Cardinal ships as a VST/CLAP/LV2 plugin for free. If your workflow is DAW-centred, that alone may decide it.

Cardinal bundles, VCV installs

Cardinal ships with a large collection of open modules built in, so a patch you make works anywhere Cardinal is installed. VCV downloads modules individually through its manager, which gives you far more choice and makes patches dependent on what the other machine has.

The commercial module ecosystem is VCV only

Many well-regarded modules are commercial and VCV-only, and Cardinal cannot include them because it is strictly open. If a specific paid module is the reason you are here, Cardinal cannot help.

Licensing purity is the point of Cardinal

Everything in it is open source, which matters for Linux distributions, for redistribution, and for anyone who wants no proprietary components. VCV mixes an open core with a proprietary ecosystem.

Which should you choose?

Choose VCV Rack when…

Choose Cardinal when…

VCV Rack detailsCardinal detailsAll ML & generative

← All comparisons