When your platform generates your customers' applications, every incident in their production is your incident. This talk is a field report from running a no-code platform's runtime plane at a peak of 250,000 concurrently hosted containers: one container and one PostgreSQL database per tenant app across multiple regions, with a control plane and a build plane feeding it. The applications themselves are produced by an AI-driven generator from customers' blueprints, which adds a failure class most fleets never see — code that nobody reviewed, regenerated on demand. I'll cover the reliability model we settled on and why: blast-radius isolation vs. density, per-tenant observability, fleet-wide regeneration and redeploy when the generator itself changes, noisy-neighbor handling on shared hosts, and the failure modes that only exist when the code in production was compiled from a customer's blueprint 10 minutes ago. Practical patterns for anyone operating a fleet of workloads you don't control.
Oleg has 25+ years in software development and shipped his first commercial app in 2003. He holds 50+ professional certifications from Microsoft, Cisco, IBM, Dell, EC-Council and others, and has built 9 startups over the past 17 years, with 2 exits. Since 2020 he has been CTO and Co-Founder of AppMaster, an AI code-generation platform launched before ChatGPT became a thing. Since 2025 he works as a Fractional CTO with 20+ companies across 12 countries, helping them transition to AI-native software engineering and SRE.
