Cloud development teams are increasingly required to validate workloads across AWS, Azure, and emerging sovereign cloud environments before anything touches live infrastructure. Testing against multiple providers in CI or on shared sandboxes introduces cost, latency, and compliance exposure that local emulation eliminates. For organizations operating in regulated industries or European jurisdictions, the question of where workloads run during development is no longer optional.
In this interview on TFiR, Waldemar Hummer, Co-founder and CTO at LocalStack, walks through how LocalStack functions as a digital twin of the cloud, enabling local multi-cloud testing across AWS, Azure, and Snowflake, and how the platform addresses sovereign cloud requirements for enterprise and regulated environments.
Guest: Waldemar Hummer, Co-founder and CTO at LocalStack
Show: TFiR
Here is what every platform engineer and cloud developer needs to know.
Technical Deep Dive
Q: What is the sovereign cloud trend and why is it relevant to cloud developers now?
Waldemar Hummer, Co-founder and CTO at LocalStack, describes a broader shift toward decentralization, moving away from the ultra-centralized model that major public clouds represent. Europe is at the forefront of this movement, with active initiatives to build cloud alternatives to US-based providers. The pressure is coming from both regulatory requirements and geopolitical factors, making local and sovereign execution a priority for many organizations regardless of whether they are formally regulated.
“We’re seeing a bit more trend towards decentralization, going away from this ultra centralized model of the clouds. Europe is kind of very much on the forefront here.” — Waldemar Hummer, Co-founder and CTO, LocalStack
Q: How does LocalStack support sovereign cloud and data residency requirements?
Hummer explains that LocalStack enables workloads to run entirely on a developer’s local machine, including a laptop, without any dependency on a remote cloud provider. This architecture directly addresses data residency and sovereignty concerns by ensuring that no data or workload leaves the local environment during development and testing. The platform is also expanding to support sovereign and European cloud initiatives as they mature.
“We give you the ability to run your workloads literally on your machine, on your laptop.” — Waldemar Hummer, Co-founder and CTO, LocalStack
Q: What cloud providers does LocalStack currently emulate and what is the multi-cloud roadmap?
Hummer describes AWS as the primary flagship product for LocalStack. Approximately a year before this interview, the team launched a Snowflake emulator as their second product. Azure is identified as the next cloud provider being added to the platform. The stated goal is to establish a multi-cloud platform that allows end-to-end application testing across providers, including sovereign cloud environments as they emerge.
“We’re looking to establish a multi-cloud platform that allows you to test end to end your applications and also from a sovereignty perspective dive into some of these sovereign clouds that are coming up now.” — Waldemar Hummer, Co-founder and CTO, LocalStack
Q: How does LocalStack partner with AWS rather than compete with it?
Hummer describes a co-launch model with AWS product teams, citing a same-day feature launch with the AWS Lambda team at AWS re:Invent. There is also a native integration between LocalStack and the AWS toolkit for Visual Studio Code, meaning developers using the official AWS IDE extension can work directly with LocalStack from within that toolchain. Hummer frames this partnership model as something he hopes to replicate with Azure and with emerging sovereign cloud providers.
“The AWS toolkit for Visual Studio Code now has a native integration for LocalStack.” — Waldemar Hummer, Co-founder and CTO, LocalStack
Q: What does the self-serve onboarding model look like for LocalStack?
Hummer describes a turnkey self-serve motion where a developer downloads the software, runs a container, and all application logic including infrastructure as code tooling such as Terraform works automatically by pointing configuration at LocalStack. The concept is framed as a digital twin of the cloud, meaning the local environment behaves like the real provider without requiring a live connection. No account setup or cloud credentials are required to get started.
“We call it a digital twin of the cloud. You just run your container and all your application, things like infrastructure as code, if you have something like Terraform, you just point it to LocalStack and it just works out of the box automatically.” — Waldemar Hummer, Co-founder and CTO, LocalStack
Q: How do enterprise platform engineering teams deploy and adopt LocalStack?
Hummer identifies platform engineering teams as the primary enterprise entry point for LocalStack, describing them as sparring partners who are building developer experience for the broader organization. These teams introduce LocalStack as a value driver across development workflows and work with the LocalStack team to customize and tailor the solution to specific enterprise environments. The engagement model combines the turnkey self-serve aspect with deeper customization for enterprise-scale deployments.
“We often have strong success when we work with platform engineering teams who are building the developer experience for the organization more broadly. Those are typically our main sparring partners.” — Waldemar Hummer, Co-founder and CTO, LocalStack
Q: How does LocalStack engage with open source and the broader cloud-native ecosystem?
Hummer states that open source is part of the company’s core DNA, with LocalStack contributing parts of its internal platform to open source projects and also contributing to upstream projects. He describes open source as one of the cornerstones of giving back to the community while also accepting external contributions. He notes that the rise of agentic AI is driving an interesting and ongoing shift in the open source landscape, though the platform continues to treat open source as a foundational pillar.
“The world really runs on open source. I think now with some of the agentic changes happening, open source in general is going through an interesting shift right now.” — Waldemar Hummer, Co-founder and CTO, LocalStack
Resources & Documentation
- LocalStack, cloud emulation platform providing a local digital twin of AWS, Azure, and Snowflake for development and testing
- LocalStack Documentation, official docs covering setup, supported services, and enterprise configuration
- LocalStack on GitHub, open source core repository for the LocalStack project
- AWS Toolkit for Visual Studio Code, official AWS IDE extension with native LocalStack integration
- Terraform Documentation, infrastructure as code tooling confirmed to work with LocalStack out of the box
***
👇 Click to Read Full Raw Transcript
Swapnil Bhartiya: So you’re already pivoting in that direction.
Waldemar Hummer: Exactly.
Swapnil Bhartiya: Now you also mentioned regulated industries. Nowadays, of course we are in Europe. Geopolitical crisis is going on, wars are going on, but there has been a growing movement towards sovereign cloud, sovereign AI. How does local stack kind of also enable that capability? Especially not only just high. I think it doesn’t really matter these days whether you’re regulated or not regulated you do want. And Europe is also building its own cloud alternatives to a lot of US based solutions. So how are, how do you feel that your positions in the right place, right time to also address this problem that we did not even envision?
Waldemar Hummer: Exactly. Yeah. We have a lot of conversations actually at Kubecon here about sovereign cloud and it’s a trend that’s coming up. So I think in general we’re seeing a bit more trend towards decentralization. Right. So maybe going away from this ultra centralized model of the clouds. And Europe is kind of very much on the forefront here. So with our solution we give you the ability to run your workloads literally, you know, on your machine, on your, on your laptop. So I think this very much in our, in our, in our favor here. At the same time we also as a platform, we’re going actually multi cloud. So we’ve been focusing on AWS as the primary flagship product. But more recently we put out a Snowflake emulator which is the second product we’ve launched a couple of about a year ago. And we’re also now venturing into Azure as the next cloud provider. So what we’re looking to establish is a multi cloud platform that allows you to test, end, to end your applications and then also of course from a sovereignty perspective also like diving into some of these sovereign clouds that are coming up now. It’s a very exciting development for us.
Swapnil Bhartiya: Actually from that perspective you mentioned, of course we talked about aws, Azure, Google Cloud is there, but Europe is also kind of building its own cloud. So how do you look at these hyperscalers? Is it like as a competitor, as something that you complement or something as Europe is working, I mean it’s hard to build hyperscaler and sometimes doesn’t mean, I mean there are a lot of effort going on in Europe as well to bring their build their own. So what is your sentiment about that? How do you look at these hyperscalers?
Waldemar Hummer: Yeah, great question. So we basically we are, especially more recently we’ve been starting to partner up very closely with aws. We have, we partner up with their product teams. We have sometimes co Launches like same day launches. Last year at AWS Re Invent, we launched some features with the AWS Lambda team, for example, because there’s a lot of pull from their customer base to enable a local developer environment. Last year we also pushed out a feature for Visual Studio code integration. So the AWS toolkit for this Visual Studio code now has a native integration for local stack. So I think at this point we’re much more closely partnering up with the cloud providers and I would anticipate or hope that this would also happen with some of the sovereign or European clouds initiatives that are coming up again on the AWS side. We’ve been very successful there and hope to replicate that also on the Azure side and other clouds now, since you.
Swapnil Bhartiya: Enable developers to work locally and how much open source do you consume or how much open source do you support? How much your toes are in the open source world?
Waldemar Hummer: Yes, we definitely have a strong DNA in the open source. We contribute part of our internal platform to open source projects. We also contribute a lot to upstream projects. So I think in the company DNA it’s pretty strong because the world really runs on open source. At the same time, I think now with some of the agentic changes happening, I think open source in general is going through an interesting shift right now as we speak, but we still see it as like one of the cornerstones of giving to the community and also accepting contributions.
Swapnil Bhartiya: How closely do you folks work with your customer client? It’s more or less like turn into solution. You come, sign up, pay and you’re done. Obviously work closely with them, the teams. What I’m trying to understand is that today what are some of the pain points that developers face despite all this maturity of whether we look at the whole cloud native ecosystem or intimidate AI ecosystem, What are some of the pain points that you see? They’re fixing it and that’s where local stock is helping them.
Waldemar Hummer: Yeah, great point. So we, there’s, I would say there’s two motions. One is our self serve motion where people can just literally download the software and just get started easily. We call it a digital twin of the cloud. Right. So you just run your container and all your application. Also things like infrastructure as code. Maybe if you have something like Terraform, you just point it to local stack and it just works out of the box automatically. Then there’s also a motion where we work a bit more closely with enterprises and for example talk to platform engineering teams. We often have strong success when we work with platform engineering teams who are building the developer experience for the organization more broadly, and those are typically our main sparring partners to introduce local stack as a main value driver across the broader organization. And then we can also play to the strengths of the solution. We can adjust it, tailor it to the effective environments. So it’s very much there is a turnkey aspect to it, but we also do a lot of customizations with the enterprise that we work with.





