Does your org’s stack offer low-code/no-code options for non-technical employees to build applications from, or does the tech side of the business have full control over what’s built?

I am curious about the management overheads of the "development" and "promote to production" efforts in PowerApps - like how much effort is that for in general, who takes up that effort and what scans and validations performed on the apps etc. Do you allow your team requests for free / unlimited play in dev / sandbox environment at all or their requests are totally gated and vetted before letting them touch anything? How complex are these apps built so far? Have they helped giving any significant return or only small tactical gaps in the ecosystem? 

Great questions, I don't have all the answers, but will give it a shot.  Our company is a collection of businesses, however we leverage an enterprise Power Platform environment.  Our different businesses contribute/build into that environment, so there is visibility of the catalog and owner(s).  The IT capability doesn't dictate time, that is the decision of that employee and supervisor how to handle what their responsibilites are within their role.  Your later questions are more challenging in that we don't have a true framework defined as what is "too complex" for this environment.  Most that we see serve a few people/department in efficiency gains.  Others have served into building functionality into a platform or deciding to change a buisness process, then that PowerApp can be deconstructed as it served it's purpose.  I do agree there needs to be some small group with observability, otherwise it can grow out of control.  Then back to the patnership/engagement portion with your users.