SourceForge Podcast
The SourceForge Podcast is the world's largest B2B software podcast published to over 1.5 million subscribers across all major social media and podcast platforms, and to over 667,000 subscribers on YouTube. Interviews with tech and software CEOs, leaders, and changemakers. The SourceForge Podcast by Slashdot Media gives you insight into the cutting edge of software, B2B SaaS, and trailblazing technology.
SourceForge Podcast
Hybrid Bare Metal Cloud Infrastructure: Servers.com by Nexcess
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Servers.com delivers hybrid bare metal cloud infrastructure that combines scalable servers, customizable enterprise hosting, GPU-powered AI compute, and managed Kubernetes under one global network. Built for demanding workloads across industries like SaaS, fintech, gaming, streaming, and Web3, it helps businesses scale quickly, reduce latency, and maintain reliable performance without sacrificing control.
In this episode, we speak with Isaac Douglas, General Manager at Servers.com by Nexcess, about why many engineering and IT teams are rethinking the public cloud and moving toward a more mixed infrastructure strategy. The conversation covers how hyperscale cloud promised simplicity and lower costs but has often become more complex and expensive in practice, why no single provider should be treated as the answer for every workload, and how companies are increasingly choosing the right environment based on the specific needs of each application.
Isaac explains that bare metal cloud can offer the control, performance, and security of dedicated hardware while still preserving scalability and operational flexibility. He also discusses how managed Kubernetes on bare metal helps teams offload infrastructure complexity, letting them focus more on application scaling than on day-to-day operations. The episode further explores how AI workloads are accelerating demand for raw compute, low-latency infrastructure, and faster capacity access, making multi-vendor and hybrid approaches even more important.
The conversation also digs into migration pain points, including outages, support issues, and rising cloud bills, and why businesses should evaluate the true cost and ROI before moving. Isaac shares a real-world example of an ad tech company that improved growth, performance, and cost control by moving only the parts of its stack that made sense, while keeping other services where they already worked well. Overall, the episode argues that the future of infrastructure is not cloud versus not cloud—it’s deciding which workload belongs where and partnering with a provider that gives honest guidance.
Follow SourceForge:
SourceForge.net - https://sourceforge.net
SourceForge LinkedIn
SourceForge X (Twitter)
SourceForge Facebook
Interested in appearing on the SourceForge Podcast? Contact us here.
The SourceForge Podcast is the world's largest B2B software podcast.
Hello everyone and welcome back to the SourceForge podcast. I'm your host, Bo Hamilton. Now, today's episode, we're getting into something that I think a lot of engineering and IT leaders are quietly wrestling with right now, and that's where should your infrastructure actually live? Uh for a decade, the default answer was the public cloud, obviously, but that default is getting challenged. Barclay's CIO survey found that 86% of CIOs planned to move at least some workloads off of the public cloud, which is the highest that number has ever been. So something's obviously shifting in how companies think about performance, cost, and of course control. My guest today is uh he he has a front row seat to that shift. Isaac Douglas is the general manager of servers.com by Nexus, a global infrastructure platform that's built its reputation on bare metal and recently joined forces with the Nexus and Liquid Web family. So I'm really excited to have Isaac here. Isaac has spent well over a decade in the hosting industry, several of those years in video game hosting, which is basically the ultimate stress test for infrastructure. You think about the hundreds of thousands of players, you know, hammering your servers at the exact same second, you know, all of them sort of allergic to lag. That's that's definitely a one way to test the limits of one's infrastructure. So um we're gonna get into that. We're gonna dig into where the public cloud model breaks down, what the alternative actually looks like, and how companies are making the move without lighting things on fire. So with that said, um, Isaac, welcome to the podcast. Glad you could join us.
SPEAKER_01Yeah, thanks for having me.
SPEAKER_00So um I want to sort of set the stage here. Um, there are a lot of names in the hosting world, and servers.com by Nexus is actually a sort of a newer combination. Servers.com has been around since 2014 and it recently became part of the Nexus family alongside Liquid Web. Uh, for listeners, hearing about servers.com by Nexus for the first time, how would you describe what the company does?
SPEAKER_01Yeah, I think what we're best known for is being bare metal. So uh a true infrastructure as a service platform. But I think we were probably one of the ones that led the charges, a bare metal cloud, right? So this idea that back in the day bare metal was slow and long contracts and slow to provision and very manual. And we kind of came along and went, well, bare metal doesn't need to be that way. Hyperscale cloud and virtualization doesn't need to be the only answer to automation and scalability. Like, let's create a bare metal cloud platform where you can get all the benefits of bare metal, so cost, control, security, but let's make it scalable. So give our customers that ability to kind of scale up and down as they need, but get all those benefits of bare metal as well.
SPEAKER_00Gotcha. Okay, so the scalability is a really big component there. Now, as I alluded to sort of in the introduction, I know a lot of companies, you know, they didn't just sit down and carefully sort of choose their infrastructure. They just sort of defaulted maybe to the public cloud because that was kind of the standard practice. It's maybe the path of least resistance. Maybe you could talk about where that model start to break down.
SPEAKER_01Yeah, I think, you know, in the old days you would say no one got fired for buying IBM, right? Uh, I think everyone in tech has heard that saying. And I think for the last 10 years, you could probably say no one got fired for buying AWS. It's become the safe bet. And I think where it's really broken down is the promise of hyperscale was simplicity and cost savings and lower total cost of ownership. And as those platforms have grown and grown, the complexity's massively gone through the roof. You've got over 200 different services that you need to navigate how to buy, generally by yourself. Support is probably not as good as it could be in terms of they're just doing it at such a scale that it's hard to give everyone a white glove experience. And the costs, you know, have crept up over the years. And I think what our customer bases that are coming to us and saying is this isn't as simple as we were sold. This is way more complex, it's way more costly, but it you know, it does scale, and we will we want to still be able to have that scalability, but we want to also gain back that control. So that's where it's really breaking down for a lot of our customers that are coming to us.
SPEAKER_00Yeah, you mentioned AWS, and it's like I, you know, you're not saying like burn down your AWS account, you know, um, but thinking about like stop treating one tool as sort of the answer to every workload. I think there's a lot of things to consider, of course, but yeah, it's it's neat to hear your thoughts. And I actually just want to plug your, you have a blog post uh you posted a while back uh titled Why the Hyperscale Cloud Bubble is Bursting. So for listeners, viewers um who want to learn more and hear more of your thoughts and um in-depth opinions on this topic, that's a good place to go. But maybe you could walk us through some of the problems that arise for teams running, like let's say, high traffic apps, gaming platforms, media servers, you think uh fintech systems, and of course AI, uh AI workloads, what infrastructure problems tend to show up first?
SPEAKER_01For those kind of applications where they're you know high performance cloud applications, we tend to find that customers are hitting the edges of what's capable within their given platform, right? And so very much what you just said, which was one company, one platform shouldn't really be the answer for anyone. And I talk about that quite a lot in that actually when people come to us, I don't think they should be all on service.com. I think they should probably have service.com and another bare metal provider and probably multiple hyperscalers within their infrastructure mix. So it's when you get to a hard edge of any individual platform, or you find a part of your application stack that doesn't quite fit that particular platform or the way you want to solve a problem, you need to have that supplier mix to be able to go, okay, I'm gonna go solve this particular problem different, but it all needs to work together. And I think that's one of the things that kind of a hyperscale bubble is the same that blog post is it's like people have gone all in on one particular thing, and I think people are becoming wise now of actually what we need to do is we need to have a multi multi-vendor approach, we need to have different solutions to different kinds of problems, and one way of doing things isn't always the best answer. Now, when it comes to AI, that's what everyone wants to talk about right now, right? And it's a very different problem. Everyone is scrambling for capacity right now. Backlogs in these hyperscalers as well as the neo clouds are becoming really, really high. And really, it's about finding a vendor that can hit not just your technical requirements, but also hit your timelines. And the hyperscalers and the very large neo clouds, they're gonna go and chase those huge deals because you know that's what makes headlines. And I think there's other providers out there, including ourselves, where we still have quite a lot of scale available to us, but maybe we're not quite chasing those bigger deals. So if you are not an open AI or an anthropic and you're going and doing multi-gigawatt deals with data centers, you know, looking at further afield into different suppliers is probably going to be really beneficial.
SPEAKER_00As we talked about the problems, I want to talk about some of the answers to them because I know servers.com isn't just a pile of their metal. There's there's like a whole stack around it. It offers cloud servers, storage, firewalls, load balancing, private networking. There's a bunch of features. How did those all those pieces actually come together for customers? Like what does a typical architecture stack look like?
SPEAKER_01Yeah, so we we definitely did start out as just bare metal. And as we've we've grown as a business and as we've matured as a company, what we've really tried to focus on is two things. One is to listen to our customers, take feedback from them and build what they want. And then the other one is to try and close the gap with the hyperscalers to make it as easy for people to get the benefits of scalability and the hyperscalers with all the benefits of bare metal cloud. So it really comes down to your unique use case with us. We're not trying to build solutions where we're like, you come to us with a problem, and we're like, hey, this is the solution that we're going to sell you because we sell it to everyone. We're trying to tailor that for each customer. But typically a customer can come to us. It all starts with a server, right? It all starts with a server and how we make that enterprise grade, how we keep that server online in enterprise grade data centers and build an enterprise grade networking stack. And then it's about working with our team of experts on designing a solution around networking elements, say load balances, firewalls, storage. Do you need some cloud servers with that? Do you need some scalable bare metal along with your fixed bare metal? And they'll bring in those expertise of our product and help tailor a solution to each client's need. So there isn't really a typical stack for us. You know, there's always servers at the end of the day. There's always a data center at the end of the day, but really our where we've found value for our clients is being real consultants and listening to their problems and then coming up with a solution rather than having a solution and trying to, you know, only sell that cookie colour approach.
SPEAKER_00There is one area that I do want to zoom in on because it sort of sits at that intersection of everything we sort of talked about, the flexibility people love around cloud and the performance of dedicated hardware. And that's Kubernetes, specifically manage Kubernetes on bare metal, which is offered by servers.com by Nexus. And for listeners who might not be super familiar with Kubernetes, basically it's like it's like the platform that automates the deployment, scaling and management of containerized applications. Maybe you can expand upon that uh for listeners. But I'm curious, like, how does manage Kubernetes on bare metal help teams get the benefits of the platform without taking on all of the operational overhead?
SPEAKER_01Yeah, actually, I think you did a really good job of explaining it. And, you know, I was I was working with some of our new team members last week. And yeah, I think as an industry, we've gone from bare metal to virtualization was the savior of utilization across bare metal. And I think Kubernetes, whilst different to obviously different to virtualization, really takes that management of infrastructure and obfuscates it to an application level. And we really wanted to bring a product to market that allowed our customers to think of infrastructure as more like how do we scale their applications rather than how do we scale this infrastructure. And so we brought to we brought to market a product, you know, we call it managed Kubernetes, where we're taking over that overhead of managing the control plane. And the customer is just buying and using compute within Kubernetes cluster or multiple clusters with us. And what we're working towards in the future is with our scalable bare metal product, which will allow customers to scale up new bare metal instances in under 10 minutes and pay by the hour, is we're gonna have Kubernetes running across that and we'll be able to enable auto-scaling just like you would on a hyperscaler with their Kubernetes products. We charge no overhead for the Kubernetes managed Kubernetes service. It's just the cost of the compute. And I think that what that's really gonna do for our customers is allow them to seamlessly migrate workloads across hyperscalers and bare metal as if it's exactly the same thing. And that's why we really wanted to be one of the first to bring that to market.
SPEAKER_00Wow, very cool. Yeah, so it sounds like Kubernetes was supposed to sort of abstract away from infrastructure, but instead it's sort of a lot of teams sort of ended up managing more infrastructure than before because of it.
SPEAKER_01Yeah, I think uh, you know, there's like with any new technology, you've got people in your team that are specialists in one thing and a new technology comes out, and it doesn't mean they're instantly gonna be specialists in the next thing. And I think a lot of teams around the world had experience in system administrator or they were experts in VMware or other virtualization technologies, and that doesn't instantly mean anyone's gonna be an expert in Kubernetes. So we wanted to build that tooling and expertise in-house, and we'll take care of that complexity of running Kubernetes on bare metal. And for our customers, they just get a buy computer and they get to worry about their applications and how that's gonna scale. And again, our consultants will work with them and uh work on finding the right solutions. But um, we wanted to take a lot of that headache of working some of this stuff out away from the customers and uh do that in a way that made sense uh commercially for them.
SPEAKER_00So let's say uh, you know, someone listening right now is is is nodding along, they're looking at their latency, and that's not a pretty picture. But all this sounds great in theory, everything you've mentioned up to this point. There's a reason people stay put with, let's say, like the public cloud. The moving infrastructure is a daunting process. It's it's sort of like the open heart surgery of a business. What are companies usually worried about when they're moving infrastructure providers or redesigning their hosting environment?
SPEAKER_01Particularly for our customer base, and we're dealing with businesses that are the vast majority of their businesses online. They were maybe born online as a as a business, right? They never had bricks and mortar presence, you know, they were born online companies, and it's the lifeblood of their business. And if they make the wrong decision in their infrastructure, you know, it can cost a lot of money to people's lives and businesses and profits and staying alive as a business. So it does take a lot of trust to move your infrastructure, and generally you need to be in some kind of pain. And whether that's you're having outages or the support's terrible or your prices are scaling at such a rate that you can't actually take on more customers because it's becoming unprofitable to do that. And we've had several instances of that. I think you've got to be prepared to go through a process. I've written a blog on this as well, that it's going to be painful. And anybody thinking about going through it needs to go in with their eyes wide open, that there is going to be some pain. We actually have a calculator which we built internally for internal use of helping people understand what their cost of migration is going to be, and then calculating what their ROI is going to be of that migration over five years, looking at their costs with the hyperscaler, um, what their actual cost of migration is going to be, because there is a real dollar figure that you can apply to that. And then working out like, is this even going to save me money on my infrastructure or is it or is it going to free up enough resources to allow me to go make more money to make this migration valuable to the business in the long term? But yeah, I always come back to there are is going to be short-term pain, but generally it makes sense in the long term. And anytime where we take a customer through that and we go, let's fill in this calculator together and work out if this is valuable. Anytime it comes back into negative, we go, cool, then you probably shouldn't do this, by the way. And thanks for coming and talking to us. But you know, this isn't the right time for your business and this doesn't make sense. But you know, let's keep talking, and maybe maybe it does in a in a year or two years down the line.
SPEAKER_00Yeah, that that's great to be to have that honesty there and be like, this is just isn't the right time. Maybe save this for a couple years from now, um, like you're saying. Yeah, because there's so many moving pieces. It can be expensive, um, it just uh a lot of headache-inducing moments. I imagine you've you've obviously helped a number of clients make the pivot. Maybe you could share some real world experiences. I mean, I don't I don't want to put you too much on the spot here, but do you have maybe an example of how the right infrastructure setup helped a customer solve maybe a performance problem, a reliability problem, or a scaling challenge?
SPEAKER_01We're doing this all the time. And uh a few years ago, I worked on a on a very large project for an ad tech platform, and they were bleeding in a few ways. They were across a couple of the different hyperscaler platforms, and it really just the cost and the level of support that they were getting and the complexity in their infrastructure, it really stopped them from being able to continue to grow in the way that they in the speed that they wanted to be able to grow. So they had to make a change. We came in and we said to them, look, there are parts of your infrastructure stack that don't make sense to be on a hyperscaler. But by the way, there are certainly parts of your infrastructure stack that make complete and utter sense to remain where they are and let's work on a solution where we can move you over to service.com for some aspects, and that was a Kubernetes-based solution where we did a multi-site solution for them so they have an amount of disaster recovery built in. But then let's also uh make sure we have some private connections to your GCP account where some of your storage and databases can stay because that's a technology platform that you've got some vendor lock-in, and it doesn't make sense for you to move it right now because it's just not the part of your stack that's crippling you. And we, over the course of about six months, we managed that migration with them, and they've been you know back to growth and got their costs under control, and you know, performances the same, if not better, from what they were doing previously. And I think what was really refreshing for them is I think everybody else that they were speaking to at the time was going, bring everything. We want everything, we want the whole pie, right? And we went to them and we went, hey, like we we only want the bit of the pie that makes sense for your business. And I I do say something all the time to customers, which is look, I I tell you to do that quite selfishly, because if you make the right business decisions for you, you're probably gonna grow as a business and you're gonna need more stuff from me. So I I want to help you be successful quite selfishly, and I think that's quite an honest reflection that catches most people off guard a little bit.
SPEAKER_00Everyone can appreciate the honesty. I was gonna ask, yeah, is there enough, has there been enough kind of time and data collected to follow up and see how they're doing post-pivot, post-shift? It sounds like the long-term decision is paying off.
SPEAKER_01Yeah, I mean, they just renewed and added capacity with us. So you're very happy and very close with their CEO now. So uh we're we're good friends.
SPEAKER_00So I think a lot of the tension as I see it is companies sort of want a few things at once. They want more performance, they want more control, they want the flexibility. And the standard public cloud model keeps asking them sort of to trade one for the other, right? And then when you factor in AI, AI is like throwing gasoline on all of it with all the massive compute demands. So I'm curious, like looking ahead, how do you see infrastructure evolving as companies need more of these things, more of the performance, the control, the flexibility than some of the standard cloud models and what they provide?
SPEAKER_01We're already seeing this migration from 15 years ago, everyone was doing co-location or had on-prem capacity, very capex heavy. And over the last 15 years, we've seen this massive shift to the other end of the spectrum of opex everything, put it up at everything in the cloud, lose that level of control. But you know, we were supposed to gain all this simplicity and all this scalability. And I think people have realized that there you probably need a kind of uh a mixture of these different ways of doing things. And there is a middle ground, so you don't have to go all the way from colo to hyperscale. There are these middle options where you get more of that control, but you're still in an opex model, you get more of that performance, but you're still in an opex model with bare metal clouds like service.com. The hyperscale isn't going away, and neither's co-location, right? Co-location is seeing one of the biggest spikes in demand that it has, you know, since AWS launched, you know, almost 20 years ago now. And that's all down to AI. So AI is really changing the game for those particular workloads, and we've seen a bit of a return to the olden days where people are just going back and doing infrastructure again and servers, and people want to buy by the whole server, they don't want to buy by a VM because the virtualization of GPUs is not something that's effective. People want that raw access to the raw GPU power, and they don't want to be spending on anything that diminishes that access to that power because it's quite expensive. So we're going through a real flux in time at the moment, and I think there's going to be a real mixture. I think in traditional workloads, and when I say traditional workloads, I mean non-GPU workloads. I think we're still going through this awakening that, okay, we can't just be on AWS, GCP, Microsoft Azure. Like we need to have a mixture. And then I think in AI right now, it's who can get the capacity on fastest wins, and there's going to be some winners and losers in that space, and there's probably going to be some new companies springing up that maybe don't have that maturity of knowing how to do this long term. So I see this, particularly the AI business, is we're going to have a lot of new startups, these neo clouds coming out, and then there's probably going to be a reconsolidation of that market over the next five years as the true winners and the players that have the true maturity on how to do this and do it profitably and do it for the long term are probably going to win out.
SPEAKER_00Yeah. Yeah. Once the dust settles, there's going to be some there has to be consolidation. I mean, it's just too wide open right now, I feel like, with what's been going on. But a lot to think about. Um, I appreciate everything you shared with us. Um, the through line of this conversation I'm thinking of is just the question isn't like no longer the cloud or not cloud. It's which workload belongs where. You want the flexibility, and then you want a partner ultimately who's actually going to help you sort of answer that question and work with you and give you the honest kind of answers and feedback. And so I think that's a great way to wrap the conversation up. And for those listening who want to learn more about the company, where should they go?
SPEAKER_01Service.com, it's it's in the name. It's nice and simple. You can always contact me. I'm I'm on LinkedIn as well. But at servers.com, all the information, you can contact one of our consultants on there, and we'd love to jump on a call and get to know your problems and your challenges and work on a solution together.
SPEAKER_00Perfect. Servers.com, that's easy to remember. Isaac Douglas, go follow him over on LinkedIn. Isaac, thank you really uh so much for everything you share with us.
unknownThank you.
SPEAKER_00Thank you for listening to the SourceForge podcast. I am your host, Bo Hamilton. Make sure to subscribe to stay up to date with all of our upcoming B2B software related podcasts. I will talk to you in the next one.