Scan and Extract Your Cloud Assets and Get a Normalized View

With Cloudockit, you can obtain a complete extraction of your cloud assets as an Excel or JSON file for Azure, AWS and Google Cloud Platform.

Try it for free

Why normalize your cloud assets?

To help you develop software by providing you with a complete asset inventory of your cloud elements
To enable you to consolidate and have a standardized view of all your components across multiple providers
To help you develop a custom script which needs all of the resources from your cloud providers as input
To keep track of the evolution of your cloud landscape and build your own reports/apps

Normalization for Your Preferred Cloud Provider

Cloudockit’s Asset Normalization Output Formats

Excel Files

An Excel file is the best format to use when you want to extract all your plant components and customize the extracted data.

For example

- Creating a CMDB database with this Excel file
- Save snapshots of your environments
- Build charts and consolidated tables

The Excel file contains all of the information extracted from your cloud environments. This file is very useful as it contains 1 tab per type of component within your environment. The Excel file also contains a warning tab which consist of all of the issues automatically discovered by Cloudockit:

As an example, below is a simple warning stand in an automatically generated Excel file

Also, here is an example of a list of websites automatically extracted by Cloudockit

JSON Files

In order to accomplish more complex tasks like custom deployments, custom scripts or even embedding Cloudockit features inside your own product or your own SaaS solution, JSON files are what you need.

The JSON files automatically created by Cloudockit contain multiple interesting elements like:

- A list of all assets found during the inventory process
- For each of these assets, you obtain the following elements:
  - Complete diagrams of the asset architecture
  - Complete documentation of the asset architecture (HTML/MD Format)
  - All properties of the asset
  - Categories of each asset

- A list of categories to classify the assets. These categories are standardized between all cloud providers.
  - Example: an EC2 Instance in AWS and a Virtual Machine in Azure will be presented as the same category
- Cloudockit gives you a normalized view of all the cloud assets
  - Example: an EC2 instance in AWS, a VM in Azure and a GCP Compute engine all have a number of CPU and some amount of RAM. The JSON file would enable you to view the information in a standardized manner
- Cost information for all your cloud assets
- Compliance rules that are applied to all cloud providers
- All of the geographical properties
- And much more.

Please visit the following article for more information about the Cloudockit JSON Format: Cloudockit JSON File Format Description

Leverage Existing Diagramming Tools

No proprietary drawing

Cloudockit is available in three different hosting scenarios

We host everything for you.

You can install the product anywhere you want (for example on an EC2 instance in AWS, an Azure Virtual Machine, or your laptop).

You host the solution yourself in your preferred Container Hosting mechanism, whether it is AKS (Azure Kubernetes Service), EKS (Elastic Kubernetes Service), or GKE (Google Kubernetes Engine).

Data Security is Key

Your Data Stays Where it is

We built Cloudockit with a focus on security. All the documents are generated in memory in an isolated process and no sensitive information is stored on disk.