Fugue's new Composer maps your application’s cloud infrastructure with automated, interactive diagrams that show your whole system in real time and the relationships between system components. You can zoom and inspect. You can quickly discover configuration errors and compliance violations. It's introduced with Fugue’s Transcriber—your tool to scan existing AWS cloud services in an account and automate their translation for easy Composer mapping. It doesn’t matter how you stood those services up. You'll see everything with Fugue. The new features are in beta and they're free.

Fugue now supports the Amazon Web Services (AWS) GovCloud region, which means federal agencies, like enterprises, can automate operations in the cloud fast, while simultaneously meeting regulatory demands. Fugue deployments start with powerful, but easy-to-understand code declarations in a composition that governs a system’s infrastructure. By including select libraries in that composition with simple import statements, a particular agency’s compliance regime gets integrated from the start. This kind of fully realized policy-as-code provides a scalable protocol for agency cloud ops and increases speed to mission.

A CMDB for APIs is a crucial aspect of Fugue, and one area where running your operations with Fugue offers a lot of value to you. Fugue's CMDB is an effect of our declarative model for configuration, built around our typesafe, compiled Ludwig language. Once it is run as a process in Fugue, that declaration is made real and immutable with machine precision.

Fugue uses a new domain-specific language, Ludwig, to describe infrastructure configuration. Before we started building, we looked around for what we wanted, but didn't find it all in one place. We want typical things you do in cloud to be easy, and not feel like programming. We want users to get great error messages, fast. We want a program that compiles to almost always work in the cloud. We want sophisticated work to be possible, but safe, predictable, and shareable.

The elastic compute systems of any given enterprise are now distributed across tens, hundreds, thousands or more physical nodes running an ever-growing array of cloud services, but there is no central coordinating function to act as a nexus for control and trust. In the midst of this unwieldy reality is an even more compelling reality—that the cloud is not, in fact, merely a collection of infrastructure. It’s the world’s first global computer. And, just as we abstracted the hardware of individual computers decades ago, we can abstract the distributed hardware of the cloud and radically simplify operations complexity.