LocalStack for Azure emulates Azure application behavior on your local infrastructure, so developers and AI agents can build and test Azure applications without the delays, costs, or complexity of deploying to the cloud.
LocalStack for Azure is a local Azure sandbox that lets developers and AI agents build, test, and validate Azure applications on their own machine, without shared cloud environments, slow feedback loops, or dev/test cloud spend. It emulates core Azure services locally so you can move faster before deploying to real Azure infrastructure.
Real Azure environments are slow to iterate against, costly to run for dev/test, and hard to share across a team. LocalStack for Azure gives you a local, isolated environment with fast feedback on every change. You catch issues earlier, avoid environment conflicts, and keep development work off your Azure bill.
It's built for enterprise software teams (developers, DevOps engineers, platform engineers, and the AI agents they work with) building Azure applications who want to move faster and test more reliably before deploying to production.
LocalStack for Azure (Public Preview) emulates core Azure services with a focus on reliability and high-fidelity behavior for typical enterprise architectures. Developer experience features, including App Inspector, snapshots, and chaos APIs, aren't included at preview launch. See the supported services page for the full list and known limitations, and browse working examples in the LocalStack for Azure samples and AKS samples repos.
Yes. The LocalStack for Azure samples repo has end-to-end examples across supported services and provisioning tools, and the AKS samples repo covers Kubernetes workloads and tutorials.
We support the services most commonly used in enterprise software architectures, including containers, serverless, databases, messaging and eventing, networking, and monitoring. See the supported services page for the full list. Each service page documents its supported behavior and is open about where any parity gaps exist.
LocalStack for Azure is built for teams. It delivers high-fidelity behavior across the services enterprise architectures use most and works with the provisioning tools teams already use: ARM and Bicep templates, Terraform modules, Pulumi programs, and the Azure CLI. Every supported service has documentation that is open about where any parity gaps exist. LocalStack for Azure runs on the same core technology enterprise teams already use with LocalStack for AWS, with SLA-backed support at GA.
No. LocalStack for Azure is a development and testing tool. It's designed to speed up your dev/test cycles before you deploy to real Azure infrastructure, not to replace it.
Nothing during the Public Preview period. Pricing will be announced at GA.
Public Preview runs until GA, currently expected in early 2027. We'll give you at least [30 days] notice before any transition.
Preview access will end at GA. You'll need to [INSERT ACTION: e.g., activate a paid plan or migrate your license]. We'll walk you through that process with advance notice and clear documentation.
Yes. Same workflow, different cloud. LocalStack for Azure uses the same local container model and tooling patterns your teams already know, so there's no new mental model to learn. Sign in with your existing LocalStack account and sign up for the Azure preview plan on the [LocalStack for Azure pricing page].
No. LocalStack for Azure runs locally and doesn't need a connection to a live Azure account for development and testing, so you don't have to hand out Azure credentials for dev/test work.
Sign up for the Azure preview plan on the [LocalStack for Azure pricing page], then follow the Getting Started guide. Most users run their first local Azure workload in under five minutes, including pulling the Azure image.
LocalStack for Azure is live in Public Preview. Run your first Azure workload locally in under five minutes.
