What is Fugue Platform?

Fugue Basics

What’s Fugue Platform?

Fugue is the name of the company responsible for creating two tools, Fugue Platform and Risk Manager. Fugue Platform (or just ‘Fugue’ for the purposes of the docs) is a cloud-native system that governs the provisioning, operation, and management of cloud infrastructure and services at the API layer. Fugue Platform completes the DevOps workflow via enforced and versionable infrastructure as code. It ensures cloud resources are always provisioned according to internal and external policies and standards, enabling governance by automating cloud lifecycle management with continuous enforcement of declared configurations.

What are the Fugue Platform standard features?

Declaration

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:

Automation

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:

Enforcement

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:

What’s Ludwig?

Ludwig is a simple language designed specifically for coding cloud infrastructure. Fugue uses Ludwig compositions to automatically build, update, and continuously maintain declared infrastructure. Ludwig features a type system for fast feedback, code and compliance validation, and meaningful errors. It also supports commenting for collaboration and documentation generation. Shareable modules allow you to break up and collapse complexity into simple abstractions to provide consistency across DevOps teams.

What does “Infrastructure Governance” mean?

With the cloud, everything is software, and anyone in the organization with a cloud account can create or change any resources they want, often with little supervision or controls. This introduces significant risk. Infrastructure governance is a system whereby only resources that adhere to established policies and controls can ever be changed and compliance is assured for the entire lifecycle of a given resource, with checkpoints for policy compliance at each lifecycle stage. Fugue provides infrastructure governance through: compliance and policy automation, DevSecOps collaboration, and continuous runtime protection.

Is cloud computing experience a prerequisite to using Fugue?

Technically no, you do not need cloud computing experience to use Fugue; however, it may be helpful. Specifically, you should understand your application’s architecture and how your application works. In addition, you should know which cloud infrastructure services your application may need, such as computing or storage. You declare your cloud infrastructure using simple syntax, and Fugue assumes the complexity of building, operating, and maintaining it.

Why Do I Need Fugue?

Why do I need Fugue?

Fugue removes the complexity and undifferentiated burden of configuring and maintaining cloud infrastructure, allowing you and your team to focus on creating value with your applications. If you want to stop wasting time managing configuration details, maintaining infrastructure, ensuring compliance, and chasing bugs in production, consider using Fugue to run your cloud workloads.

Who can benefit from using Fugue?

Because Fugue is an infrastructure-level system for the cloud, anyone deploying workloads in the cloud can benefit from it. Large enterprises face complex challenges managing workloads at scale in the cloud, and they can benefit from the operational efficiency, compliance and policy enforcement, and business agility that Fugue provides. Those running smaller workloads in the cloud can benefit from the “set it and forget it” benefits of Fugue, allowing scarce resources to be devoted to value-creating applications rather than costly infrastructure maintenance.

What are some high-level use cases for Fugue?

Fugue fully automates the creation, operations, and maintenance of cloud infrastructure for a wide variety of workloads and centralizes control and collaboration for cloud operations at scale. Some of the operational use cases for Fugue include:

  • Regulating the creation, modification, and access to cloud resources with role-based access controls
  • Providing fast access to reliable cloud infrastructure environments for internal teams or external customers
  • Managing multiple, dynamic cloud environments that span AWS accounts
  • Completing your CI/CD workflow by automating the lifecycle management of cloud infrastructure
  • Simplifying the creation and management of container clusters, networks, and related infrastructure services
  • Ensuring policy validation at design time and continuous enforcement of infrastructure configurations in production
  • Showing the impact of infrastructure changes before they’re applied so you can include plans in approval processes

Take a look at our Product Page to see details about Fugue’s capabilities or Fugue by Example to walk through a specific scenario.

How does Fugue save me money in the long run?

Fugue greatly reduces the need for deep cloud expertise in adopting and scaling cloud use. Fugue radically reduces costly infrastructure operations and maintenance burdens, allowing you and your team to focus on creating value with your applications, not managing infrastructure configuration details and debugging in production.

Click here to visit the FAQ page for “Fugue and Ludwig Internals”, or go back to the main FAQ page.