Posts

Showing posts from May, 2023

Top 5 Questions About Maestro: Automation and Multi-Partners Finance

Image
In our previous post , we started the topic of top questions related to Maestro , which included those about Maestro as a SIAM platform and Maestro resource management approaches. In this article, we are facing another popular questions - focusing on finance and automation. 1. How would you organize the multi partner billing process? Using a SIAM framework which supports multi-layered organizational structure allows organizing billing process for multiple cost objects, that can be assigned to different partners. This can be organized wither via using multi-tenant approach, where cloud accounts are matched to different tenants, thus the whole billing for a specific tenant goes to a specific partner. Alternatively, in case a single account is used by several partners, infrastructure can be split within a tenant, with tags, or based on the resource ownership concept. 2. What are the relevant price items which would build up the structure of your cost estimation? For public cloud providers

Top 5 Questions About Maestro: Service Integration and Management

Image
New trends keep on hitting the Cloud Market, caused by both changes in infrastructure creation approaches, and enterprises' aim to make the infrastructures more effective - in performance, and from the financial point of view. While communicating to project teams and customers, Maestro team has collected a set of typical questions, and we decided to aggregate the answers in a series of two blog posts. And we would like to start with the questions, related to one of the hottest topics now - Maestro as a Service integration and Management Platform.  1. How should a SIAM model from your point of view look like? SIAM is a framework needed to manage multiple service providers and their services effectively, in a unified manner, by incorporating them into a single platform.  Maestro as a SIAM framework allows arranging effective operation and infrastructure services for an enterprise.  It has an API-first approach which allows both effective adding new own components, as well as integra