Free Factsheet

Abstraction-Layer vs. Cloud-native Access

At the beginning of every cloud journey is the strategic decision to position the enterprise between the security of an abstraction layer and the flexibility of cloud-native access.
Get the lowdown on the pros and cons of setting up cloud-native access or an abstraction layer. This factsheet will help you figure out your cloud governance strategy with essential guiding questions to get you thinking.

Language: English
Target Group: Platform Engineers & Enterprise Architects

Download Now!

Abstraction layer vs. cloud-native access factsheet cover. Guide to making the strategic cloud governance decision between control and flexibility.

Guiding questions for your cloud strategy

Cloud-native freedom or full control?

Decision-making assistance at a glance

How to use Landing Zones in Azure?


Our guide will help you get your head around which cloud governance strategy is the right fit for you and how to dial in your cloud management abstraction.

When you’re setting up a cloud governance solution, you’ve got two main options: total control with a platform abstraction layer, or full-on flexibility and agility by going cloud-native.

This becomes even more important in highly regulated industries where you need to keep a tight rein on things, but also need to stay flexible to keep up with the business requirements. Our guide will help you get the balance right.

  • Are you looking to make your move to the cloud at warp speed?
  • Constantly rolling out cloud-native apps?
  • Trying to attract top IT talent for your department and company?
  • Thinking about a multi-cloud strategy to avoid being tied down to one vendor?
  • Need to keep a bird’s eye view on all cloud activities to stay compliant?

Our guide questions will help you suss out which cloud governance strategy is your perfect match.


  • Clouds provide a ton of services. If you go with an abstraction layer, you'll need to add new services one by one before your developers can start playing around with them.
  • Keep in mind, automation is king. If you've got cloud-native deployments running on autopilot, you won't be able to transfer them over to your abstraction layer solution.
  • Developers are like artists, they like to choose their tools. Cloud-native access gives them the room to experiment and can help you attract more talent for multi-cloud operations.
  • Abstraction layers might take away some of the benefits of a multi-cloud strategy. They can create a new single dependency and unify the variety of services on offer.
  • Control is always important, not only in highly regulated industries. An abstraction layer gives you more control but traditionally, there's a bit of a trade-off between having control and staying agile.