KRATEO PLATFORMOPS

The Platform Team must provide services for which:

• Automation is a key element on which build your platform;
• You need a self-service portal that exposes internal services through a user-friendly catalog;
• The services in the catalog can be heterogeneous: infrastructure components, software templates, pipelines for Machine Learning models, etc..
• Services can be deployed anywhere: on premise, public cloud, hybrid cloud, multi-cloud.

However, it is important to pay attention to some aspects when implementing the PlatformOps strategy: the automation for each service does not have to be specialized for that specific service. Modern application development is based on the microservices paradigm as they bring various advantages such as scalability, atomicity, reusability, ease of maintenance: automation must also follow the same principles.

If these guidelines for implementing the PlatformOps strategy are not established from the outset, the following issues will emerge on the critical path:

• diverging automation flows, complex to maintain, not very reusable;
• an increase in the number of tools to use – when in reality you want to simplify the toolchain _ and the related need to have skills on them;
• increase in costs and risks for the Platform Team of failing to implement the PlatformOps strategy and therefore not enabling the business of one's company to scale.

With Krateo you can solve these problems through a single platform!

The common onboarding experience of a developer is increasingly complex as the complexity of the toolchain grows: the user must not get lost in documentation to read, tickets to open, meetings to organize. He must be able to access internal services as quickly, securely and independently as possible. To do this, you need a self-service, reliable and user friendly portal that requires a minimum number of information necessary to use it.

The portal must also request business information that the user knows and not detailed information that can be determined by the automation of the Platform Team.

All information related to the service or the lifecycle of that product needs to be centralized: this allows to abstract the toolchain and to focus the user on the important data related to the service.

Within the portal itself it must then be possible to search for all the services already implemented, access the relative documentation, identify the exposed interfaces, access the source code with a view to providing governance and building a real community within the company.

Krateo delivers this kind of experience by streamlining service onboarding and ownership processes.

FinOps is for "Cloud Financial Operations" or "Cloud Financial Management" or "Cloud Cost Management".

The task of the FinOps is to help the C-level managers both in the budgeting phase (i.e. estimating the budget that the service requested by the portal needs), in the cost allocation phase (i.e. verifying that all the cost items are effectively in line with expectations and that they are assigned to the teams correctly) and in the cost optimization phase (i.e. analysis of a possible lower use of resources also aimed at reducing consumption, environmental impact and carbon footprint without compromising the performance of the service).

With Krateo it is now possible to do FinOps and optimize platform costs across multiple suppliers.