Why CloudManager

Why CloudManager

Why CloudManager? That’s a great question. The Cloud is an ever evolving landscape, in the case of AWS, new services and features are added daily. Couple this with a multitude of choices for how to build your Cloud based systems, Microservices, Monoliths, Serverless and programming languages, JavaScript, Python, Java or GoLang to name just a few.

Where should you start and how do you keep on top of all these changes? This is where CloudManager comes in. We’ve taken more than 25 years of production, high volume, internet scale experience and created a platform for developers to excel in the Cloud.

CloudManager brings more than 25 years of production, high volume, internet scale experience and created a platform for developers to build applications in minutes.

CoudManager is a combination of multiple tools working together so you can focus on your customers and creating the most compelling user experience possible. Here is what makes up CloudManager:

Cloudprints

One of the core building blocks of CloudManager, a Cloudprint is a combination of software and infrastructure. A Cloudprint is an opinionated way to build software, it includes the following:

  • git repository creation, with branch protection enable.

  • CICD pipeline definition, configured and running upon project creation.

  • Source code, creates a fully functioning application or web service, designed and built to support high volume workloads. We embrace a minimalist approach to application development, there’s no code bloat or unnecessary boilerplate.

  • Infrastructure as code (IaC), you know your application requirements best, you should define the infrastructure needed for your application. All the infrastructure needed for your application or web service is also included and will be deployed as part of your CICD pipeline.

CloudPolicies

While we believe in empowering dev teams to create the infrastructure they need, organizations also need to ensure corporate governance and security policies are followed. Enter CloudPolicies, defined by CloudManager, extensible by you and your IT Security/Ops teams. CloudPolicies define how infrastructure should be used. If an application doesn’t conform to a CloudPolicy, a CloudResolution process can be kicked off for rapid resolution.

CloudPolicies define how infrastructure should be used.
CloudTeams

Imagine all of your team permissions are easily and effortlessly transferred as you move from team to team. Welcome to CloudTeams. When you are added to a team, you have permission to all of your teams applications, monitoring and resources. When you change teams, CloudManager will automatically add you to the new team and remove you from the old team. No more dangling permissions or the need to "clean up" your directory service.

CloudManager will automatically add you to the new team and remove you from the old team
CloudResolution

Remember the last time your container was scanned for vulnerabilities and it took weeks to resolve all the issues found? Welcome to CloudResolution, the first service of it’s kind. CloudResolution will enable you to quickly resolve issues found due to container/application scanning and/or CloudPolicy violations. Tied into the Continuous Integration portion of your CICD pipeline, CloudResolution will enable your Security and Operations teams to quickly and accurately respond to your requests. There are a varitety of ways to resolve your exception request and CloudResolution will catalog and manage all requests for you and your organization, streamling the process so you can focus on your customers.

Welcome to CloudResolution, the first service of it’s kind. CloudResolution will enable you to quickly resolve issues found due to container/application scanning and/or CloudPolicy violations.