This message was deleted.

My previous team stood up and developed the Backstage for my company. I've never looked at clutch. What questions do you have?

@Asaf Erlich We are building platform engineering capability and I am currently scanning the space for all resources that can help kickstart. At this point I am all open to learn how teams are doing this, what tools, what principles etc. Any pointers to blogs/notes on how not to do will help us. How hard is Backstage to manage and operate? Is the current documentation sufficient to instantiate something internally?

The documentation is decent but doesn't provide in my opinion enough to productionalize it. Things like proper security and operational rigor are up to you to decide.

Also adding onto the Backstage experience! We have a medium article written up about our use case around measuring operational excellence and some of our principals when setting up our system models. Just another data point for backstage 😄

How hard is Backstage to manage and operate?

I think this will really come down to how much you want to customize backstage out of the box, and what you aim to do with it.

Is the current documentation sufficient to instantiate something internally?

For sure more than enough to get something going internally to check it out! The software templating capability is probably going to be the major point of contact point for building a IDP. It not only lets you scaffold software but also lets you write/use actions like using git, making http requests to other services, or run a cloud pipeline. There is also https://github.com/kubevela-contrib/backstage-plugin-kubevela and https://www.syntasso.io/post/kratix-and-backstage-a-perfect-pair for a some other approaches on using backstage. I’d be remise to not throw out the backstage demo site as well to kinda get an experience of what backstage might be like out of the box with some demo data without templating.