GOTO - The Brightest Minds in Tech

The episode has a few genuinely useful data points (bare-metal cost savings, eventual-consistency resilience of the control plane) but is padded with repetitive product explanation, conversational affirmation, and obvious observations about Kubernetes complexity. The ratio of novel ideas to filler is low for a 33-minute runtime.

“if our control plane were to go down, your servers will continue to maintain a manifest. So if one of your containers crashes, but that manifest says, hey, like this container should be running, your server will still restart that container even though it can't talk back to cycle”

“since November of last year, I would say, I don't have an exact number, but I would say 70% plus of the companies of Adopt and Cycle have had a bare metal component”

The sovereign-cloud and cloud-repatriation themes are well-trodden in 2024-2025 industry coverage, and the Kubernetes-complexity narrative is essentially a cliché. The 'waves' framing for geopolitical reaction and the AWS-holding-your-keys metaphor are mildly fresh but not counterintuitive or first-principles.

“I think we're going to see it in waves. Right. So I think we just saw a short term very intense wave and then it kind of died down as the conversation around Greenland kind of paused”

“too many people kind of handed over the keys to AWS and said, great, solve it all. And now AWS is sitting there holding your keys, saying, now you need to pay me more if you want these keys back”

Jake is a genuine practitioner with real infrastructure credentials - early OpenStack contributor, bare-metal IaaS builder, and a functioning commercial product since 2019 - which is meaningfully above the 'thought leader' baseline. However, Cycle is a niche, mid-market product and the conversation never reaches the scale or depth of experience that would justify a higher score.

“Jake has nearly two decades working in data centers, infrastructure automation and DevOps. From contributing to early OpenStack projects to leading development and one of the first bare metal infrastructure as a service providers”

“since Cycle started bringing in customers back in 2019, our control plan has been just a North America control plan”

There are a handful of concrete data points - the $45K-to-$12K AWS-to-bare-metal cost example, the 70% bare-metal adoption figure, and the March 2021 uptime claim - that add genuine evidential weight. But the guest frequently hedges ('I don't have an exact number,' 'I'm not sure if I'm allowed to mention their name') and the broader geopolitical and industry claims are entirely unsubstantiated.

“I believe their compute spend at AWS was somewhere around $45,000 a month. And by moving over to bare metal, their spend now is, uh, hovering around 12 grand a month”

“70% plus of the companies of Adopt and Cycle have had a bare metal component”

Charles Humble brings genuine domain experience and does land a few productive challenges - pushing on trade-offs of abandoning hyperscalers and asking about trust in a US-headquartered company. However, he frequently affirms rather than probes, lets the Cloud Act legal risk angle drop too quickly, and several questions are open-ended softballs that allow the guest to pivot back to product marketing.

“What are the trade offs that you're making? So if you decide to move away from aws, uh, or GCP or Azure or something, what would you say are the uh, trade offs that you're making there? What do you lose if you abandon the cloud effectively?”

“I'm wondering if you think that that's a layer that has been underappreciated in risk terms maybe up till now potentially”