Free Fugue Features

Free Fugue offers several standard features:

Note: If you exceed the number of users for your Conductor you will receive the following:

[ ERROR ] max user limit of 2 exceeded, policy requested 3. Please visit for information about upgrading your conductor.

The default Conductor instance size is m4.large and supports up to 5 AWS accounts* and 200 simultaneous FIDs. If these numbers are exceeded, the CLI displays a message with instructions for upgrading the Conductor instance size to m4.4xlarge. The larger instance supports up to 15 AWS accounts (2 for Free Fugue) and 1,000 FIDs. For customers using the paid version of Fugue, each Conductor can support up to 15 AWS accounts, and there are no restrictions on the number of Conductors that may be used.

  Free Fugue Fugue (paid version)
Small instance (m4.large) 2 accounts / 200 FIDs 5 accounts* / 200 FIDs
Large instance (m4.4xlarge) 2 accounts / 1,000 FIDs 15 accounts / 1,000 FIDs

*The paid version of Fugue starts at 3 AWS accounts but more may be purchased (e.g. up to 5 on the m4.large instance and 15 on the m4.4xlarge instance). Reach out to for details on your upgrade options.

AWS typically charges more for larger instances. See the FAQ for details on how Fugue affects your AWS bill.


With Fugue, you declare your cloud architecture, and Fugue makes it so. It’s infrastructure as code. Using the domain-specific language Ludwig, you describe the configuration of your cloud infrastructure. You run the compositions with the Fugue CLI, and the Conductor creates, modifies, or destroys your infrastructure accordingly.

Ludwig is simple, concise, and strongly typed. For more information about writing Ludwig to declare your infrastructure, see the following documents:


Fugue automatically builds, updates, and maintains your cloud infrastructure. It’s your single source of truth and trust for the cloud. When you run a composition, the Conductor deploys your infrastructure for you. To make a change to your infrastructure, simply edit your composition and update the process. Fugue handles the modifications for you automatically, making sure that your infrastructure is always just as it was declared. And if you need to tear down your infrastructure when you’re all done, Fugue handles that automatically, too – just use the kill command.

For more information about how Fugue uses automation, see the following documents:


Fugue enforces your infrastructure by continuously and automatically comparing it to the declarations in your Ludwig code. If there’s an untracked difference between the Ludwig and the state of your infrastructure, Fugue reverts the changes, restoring your infrastructure to the declared state. If you need to make a change to your configuration, simply declare it in your Ludwig composition and update the running process. Fugue makes your infrastructure so, and makes sure it remains so.

For more information about how Fugue uses enforcement, see the following documents: