 Okay, so I'm very happy to be here today and on stage for the next five minutes and Because I don't have a lot of time. I'm going to jump directly into the answer and the answer is yes yes, and the question to that answer is can backstage deliver value beyond engineering teams across the organization to other people My name is Olivier Lycheti. I'm founder and CTO of Avalya Systems and one problem space that we explore with our clients is How can we better understand and explain what is happening in the black box of software development? And can we communicate the business value the business impact of technology There are two reasons why we decided to use backstage to work on this problem and This is because in the solution space backstage gives us two important capabilities The first one is the generic Data model that we can use to create a model of the entire software ecosystem The second capability is this very generic application development framework that we can use and so with these two capabilities We are equipped to implement a very different use cases for different people in the organization Instead of talking about developer portals We tend to speak about digital portals and in the projects that we do we focus a lot on content insights and stories and We create personalized experiences By selecting the type of information and the way the information is presented to the users Doing these projects. We have identified three teams that we find important and that we keep revisiting These teams are revisit the UX Embrace model extensions and be smart about content Revisit the UX I Think we can all agree that even if the UI of backstage is very logical is well structured It drives us to the design of portals that really feel like developer tools And if you consider non-technical people this can be Overwhelming if not scary I think we can also agree that the table view in the catalog is very effective to search for information But it's not very good to understand the overall structure of the ecosystem It's state and the relationships between the entities The good news is that in the end a backstage instance is a react application So with some work, it's possible to turn the UI inside out Instead of adding custom panels custom tabs into backstage We prefer to look at it the other way we look at a broader collaborative web application and We inject backstage user interface elements into that broader application This is a technique that we use to create a first experience with the portal that is more appealing for non-technical people Embrace model extensions I mentioned before that the system model is really one of the features that drew us to the backstage in the first place and At the same time if we read the documentation the documentation makes us cautious about Modifications extensions of the system model. Is it a good idea to change? entity kinds is it's a Good idea to define new relations. So we are aware of the trade-offs But because for us the modeling part is so important. We tend to favor them in addition to the taxonomies an important part is the Metadata that you can associate that you can lean to entities in the catalog and here I would like to make an analogy to a GIS The GIS gives you different perspectives on the world By allowing you to use different layers on the map and the idea is that Backstage can become the GIS of your software ecosystem Because the user interface of backstage is fully customizable It's possible to create these interactive data visualizations these interactive maps in This example we are looking at the organizational structure Where squads are groups? in tribes and When you have these interactive visualizations rendered into backstage You can annotate them to represent the state of the acquisition of the Ecosystem here. It's the happiness of the teams But you can do similar things with the quality of the systems or the business value generated in the domains Last but not least be smart about content Creating a digital portal is not trivial But we have really when you have released the first version of your portal you have only done one part of the job If the goal is to generate a stream of insights content and stories How are you going to keep this stream lively and relevant for the people who is going to do that work? And how much time is it going to take? There are of course different strategies that you need to to combine But one very interesting use case that we see is to combine software analytics with generative AI and One thing that we have done is to implement data pipelines where we combine these tools. I Don't have the time to go into a lot of details, but just to give you an idea It's possible to extract data from systems. For example issues captured in GitHub To give this data structure to charge EPT and to ask What are interesting questions that you could ask about this data set? To then ask charge EPT to write to the code That once executed can answer the question proposed by charge EPT and In the end to ask the charge EPT to write a story About the answers in a way that makes sense to an engineer a CTO or a CFO and Therefore creating this content that will be Understandable and make sense for the different personas. I Hope that this has Triggered your curiosity. I will be at the conference for the whole week And I would love to chat and show you a demo of these Portals. Thank you