--- date: "2020-04-21" title: "Announcing Pulumi 2.0, Now with Superpowers" authors: ["joe-duffy"] tags: ["pulumi-news"] meta_desc: "Today we are announcing Pulumi 2.0, a modern infrastructure as code platform with advanced capabilities including new languages, testing, and policy as code." meta_image: "pulumi-2-0.png" --- Today we are excited to announce Pulumi 2.0, the next major stage in our journey as an open source project, company, and community. This release expands on our original vision of using your favorite languages and tools to do all things infrastructure as code, now with new cloud engineering superpowers that will help you and your team adopt modern cloud architectures.
## What is Pulumi? We call Pulumi's unique approach _Modern Infrastructure as Code_: * **Familiar Languages**. Use the best languages and tools to declare infrastructure and gain best-in-class productivity and engineering capabilities. Connect to existing communities and ecosystems and leverage world-class language and tooling innovation. * **Multi-Cloud**. Adopt consistent workflows across any cloud(s) — public, private, or hybrid — while still using the full breadth and depth of your target cloud's services. * **Modern Architectures**. Although Pulumi works great for legacy workloads, it was born in a world of modern container, serverless, and cloud-native architectures. Feel free to mix and match these approaches as you modernize over time. * **Cloud Engineering Teams**. By choosing Pulumi, you're betting on your team. The whole team, in fact: developers, infrastructure and operations teams, and security engineers alike. Tackle cloud solutions together without technology or team silos. ## Introducing Superpowers! The main theme of 2.0 is something we've taken to calling "superpowers." This isn't just a buzzword we came up with — it's something we keep hearing from happy end users. ## What is Pulumi 2.0? After [shipping 1.0 last year](/blog/pulumi-1-0/), we've been hard at work helping customers to succeed at their modern cloud projects. This has taken us beyond the basics to include: * **Provisioning**. All core language SDKs are now at parity, including all existing languages — [Node.js (JavaScript, TypeScript)](/docs/languages-sdks/javascript) and [Python](/docs/languages-sdks/python/) — as well as the new additions to the family — [.NET (C#, F#, etc)](/docs/languages-sdks/dotnet) and [Go](/docs/languages-sdks/go/). We've also significantly expanded upon the supported cloud resource providers in the [Registry](/registry/), totalling above three dozen, and rolled out [entirely new API documentation](/registry/). * **Delivery**. As we've worked with customers to go from development to production, we've added [more CI/CD integrations](/docs/using-pulumi/continuous-delivery/) as well as [environment management capabilities to help at scale](/blog/pulumi-service-improvements_02-2020/), such as [project and stack tagging and filtering](/docs/concepts/stack#stack-tags). * **Architecture**. Customers are [building their own platforms](/resources/building-self-service-clouds/) that use abstraction and packaging mechanisms, including our component model, to codify their own best practices. [New coexistence and migration options](/docs/using-pulumi/adopting-pulumi/migrating-to-pulumi/) help to build larger systems out of many component parts, including those you haven't been able to port to Pulumi yet. * **Policy**. [Our new policy as code framework, CrossGuard](/docs/using-pulumi/crossguard/), lets you define policies using familiar languages and then apply those policies at deployment-time. This prevents mistakes from ever getting out the door, including cost, security, and compliance. [Configurable policy packs](/docs/using-pulumi/crossguard/configuration/) let you write a single policy and apply it flexibly across your projects. * **Testing**. Many customers are using a spectrum of techniques to [validate their infrastructure in new ways](/docs/using-pulumi/testing/). This includes [unit testing using familiar frameworks and new mocking capabilities](/docs/using-pulumi/testing/unit/) through [integration testing for short- and long-lived environments](/docs/using-pulumi/testing/integration/). ## Welcome to the Team, Pulumipus!