{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/2e622b586a5c43dea4372bb5072b27f5\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/2e622b586a5c43dea4372bb5072b27f5-59ccf092e5c8ae80.gif","duration":110.442667,"title":"AutoOps Upgrade for Smarter Game DevOps","description":"This Loom explains why Onglings built AutoOps Upgrade to help teams make better DevOps decisions without deep engineering backgrounds. It uses the example of Sansa, a virtual temple that drew 12,000 people on launch day before the server crashed due to cheaters and bugs, and where the creators could not keep up with everything needed to keep it running. The speaker notes that while tools can build and fix changes, the challenge is knowing what to ask for, such as adding server capacity or changing system architecture without causing downtime or new bugs. AutoOps brings those choices to users and then helps implement the selected changes after connecting their GitHub and related accounts, with no separate account to create or installation."}