Bring Your Own Cloud: Running Software in Customer Environments

Your enterprise customer just asked: "Can you run this in our environment?" Join us for an evening of deep dives into that question – the engineering tradeoffs behind BYOC, the deployment model reshaping how software is sold and operated, accelerated by AI and rising data-sovereignty demands. More buyers now require vendors to deploy into their cloud, forcing product and engineering leaders into a hard tradeoff: keep shipping the roadmap, or invest in a new deployment model. Rootly hit this directly, and built their Edge Connector to run inside customer networks without opening inbound access – they'll share what that took. This panel covers the full journey: launching a self-hosted deployment option, adding the access and infrastructure layer that turns it into true BYOC, and navigating the challenges that emerge once you're operating software across dozens – or hundreds – of customer environments. We'll bring together the three pillars of a BYOC motion – deployment, secure access, and day-2 operations – and explore how to orchestrate them to launch, secure, and maintain software in customer environments without the traditional overhead. ​Agenda: ​Speakers Quentin Rousseau | CTO & Co-founder, Rootly AI Michael Ten-Pow | Founder & CEO, Tensor9 Eran Kampf | VP of Engineering, Twingate Who Should Attend? About Rootly AI is the AI-native on-call and incident response platform that provides proactive support to help Site Reliability Engineers resolve incidents faster, improve system resilience, and streamline on-call operations. It’s your always-on SRE copilot that automates root cause analysis and identifies patterns that drive continuous improvement—trusted by hundreds of companies like LinkedIn, NVIDIA, Replit, Elastic, Canva, Clay, Tripadvisor, and Shell. Tensor9 lets software vendors deploy their product inside customer environments – cloud, on-prem, or air-gapped – without rewriting any code or maintaining a second product. It takes the deployment setup you already have and automatically adapts it to each customer's environment, so every customer runs the same product on the same release schedule. It's the fastest way to launch a self-hosted option – from one dashboard, your team can monitor and update every deployment – trusted by leading startups like Serval and Cerby. Twingate solves the other half of the problem: once your software runs in a customer's environment, your engineers still need to reach it – to debug, patch, and respond to incidents. With Vendor Private Access, an egress-only connector ships inside your deployment package, giving your team least-privilege, fully audited access to every customer deployment – no inbound ports, VPNs, or bastion hosts – while customers keep complete visibility and control. It's the access layer that turns a self-hosted deployment into an operable BYOC offering — trusted by companies like Notion, Confluent, Wiz, Cyera and Red Hat.