Cloud-quality dev environments, isolated from the cloud
Simulate your production application environment in a local sandbox to iterate, debug, and validate code faster and better than in the cloud.
%201.svg)
1,500+
active customers
400M+
Docker pulls
8M+
weekly LocalStack sessions
35k+
Slack community members
The cloud was built to run software, not to develop it.
Building, breaking, and debugging is work the cloud was never built for. Three structural problems slow every team down:
You wait on the cloud to do work it was never meant to do.
Dev and test require validating how apps behave in the cloud. That doesn't mean every test needs to wait for one. Provisioning queues, DevOps tickets, and shared staging turn minutes of work into hours and days.
Shared dev accounts create conflicts, individual cloud accounts create bills.
Developers lose hours debugging conflicting shared deployments. Dedicated cloud environments fix clashes but multiply spend.
You can't break, inspect, or replay the cloud the way debugging demands.
The cloud runs production apps, not tests. Reproducing a failure often means redeploying remotely, without the ability to pause execution, inspect live state, or replay the exact request that broke.
Local sandboxes. Faster validation. Seamless deployment.
LocalStack simulates your production application in an on-demand sandbox that runs on your own infrastructure. Deploy the same code and IaC you already have, surface bugs that are hard to catch in the cloud, and validate fixes in minutes: cloud-quality sandboxes, isolated from the cloud.
A cloud sandbox for every developer
Production-grade cloud behavior on safe, private infrastructure, available on-demand. No shared staging, no DevOps requests. Just a personal sandbox that simulates your production app.
Faster iteration. Better visibility. Easier debugging.
Snapshot state, replay bugs, and share environments. Catch defects that would otherwise reach production, and do it faster than the cloud allows.
Deploy to production with no code changes
The same code that runs against your local sandbox runs against real cloud infrastructure. No rewrites, no special builds, no deployment friction.
What you get, every time you sandbox.
Independence, speed, and production-grade fidelity, without adding a cent to your cloud bill.
Independence
Every developer gets an isolated cloud on their own machine. No more queuing for shared dev accounts and waiting on DevOps-provisioned environments.
Speed
Sandboxes spin up in seconds, not days. Feedback is instant, so you iterate faster than the cloud allows.
Reduced cloud spend
Sandboxes run locally, adding nothing to cloud spend, no matter how many developers run them at once.
Production-grade fidelity
LocalStack runs the same APIs your cloud provider does, so what passes locally behaves the same in production.
Debuggability
Snapshot state, replay a failure, and simulate outages with chaos testing: capabilities you can't get when debugging remote cloud infrastructure.
Faster onboarding
Engineers set up a complete cloud dev environment on day one: no cloud credentials, no provisioning, no DevOps queue.
Deploy locally. Review bugs. Fix fast. Validate in minutes.
LocalStack provides a closed loop on your own machine: deploy to a local sandbox, review what breaks, push a fix, and validate against production-grade APIs. All in minutes, not deploy cycles.
Step 1
Deploy locally
Spin up local sandboxes in a single container using the same application code and IaC you already run in the cloud. No remote provisioning, no shared account.
main.tfresource "aws_s3_bucket" "test-bucket" {bucket = "my-bucket"}terminallstk tf initlstk tf applyStep 2
Review bugs
Inspect logs, catch IAM misconfigurations, and debug service-to-service payload issues that are hard to spot in the cloud.
Step 3
Fix fast
Failures surface in seconds with full logs and traces. Patch your code and hot reload without redeploying, then re-run as many times as you need. Break and rebuild dozens of times a day.
terminal$ lstk aws lambda invoke --function-name list out.txt{"StatusCode": 200,"ExecutedVersion": "$LATEST"}$ cat out.txt{"result": 4}Step 4
Validate in minutes
Confirm fixes against the same APIs production runs, then ship. Code validated in the local sandbox runs in production unchanged.
Works across your team
Snapshot a sandbox with Cloud Pods and share the exact state, so bugs that are found can be reproduced. The same environment for everyone, every time.
Works in your pipeline
Run a complete cloud sandbox per CI job. Spin up per pipeline. Pay nothing per run.
Built for developers, platform teams, and pipelines.
Every developer, DevOps engineer, and CI pipeline needs the cloud differently. LocalStack meets each one where they work.
Developers
Build, test, and debug in ways you can't on the cloud. Break and rebuild your environment without touching a shared account or cloud bill.
Platform & DevOps engineers
Give your team a local cloud sandbox that fits your existing golden paths: same code, same IaC, no per-developer cloud accounts to provision or govern.
CI/CD pipelines
Replace slow, expensive live-cloud test stages with repeatable local sandboxes. Spin up a complete cloud sandbox per pipeline. Pay nothing per run.
Under the hood, a full cloud dev toolkit.
LocalStack isn't just service emulation. It's the debugging, testing, and state control you need to develop against the cloud with confidence.
Chaos engineering
Inject faults and outages to test how your app behaves under failure: safely, on infrastructure you can actually break.
Multi-cloud emulation
Run production-grade AWS and Snowflake services locally, and point your app at a single local endpoint. Azure emulation is in public preview.
IaC testing
Deploy and test everything you ship to production, and catch misconfigurations before they reach the cloud.
Debugging & visibility
Step through your functions as they run, watch permission changes in real time, and inspect your entire stack, all locally.
State management
Snapshot the full state of a sandbox, replay it, and share it across your team: reproduce any bug on demand.
Trusted by the world's most innovative development teams
10x
faster onboarding
70%
faster resource creation vs. AWS
15x
operational efficiency
30%
reduction in development and testing time
“LocalStack allows us to move away from costly shared test environments to local environments where developers can experiment freely and test aggressively without stepping on each other.”
John Calhoun,
Chief Cloud Architect, PayNetWorx
Set up your first sandbox in minutes.
Everything you need to go from install to first validated test is a few commands away. Install LocalStack, start a sandbox, and point your app at a single local endpoint.
Docs
Which services LocalStack runs, how to configure and integrate them into your dev and CI workflows.
Quickstart
Install the lstk CLI, run your first sandbox, and validate a deployment against production-grade APIs.
GitHub
Pre-built workflows and integrations for LocalStack.
Community
35k+ engineers sharing patterns, integrations, and help.
Frequently asked questions
A local cloud sandbox, also called a local cloud development environment for developers, is an isolated environment that simulates cloud services, like AWS, on a developer's own infrastructure. Developers deploy, test, and debug cloud applications against production-grade APIs without cloud credentials, non-production cloud costs, or risk to shared environments.
Shared cloud accounts create conflicts: developers overwrite each other's configurations and debug failures that aren't theirs. Real cloud accounts add provisioning delays and per-run cost. A local sandbox gives each developer an isolated environment that behaves like the cloud, without the conflicts, delays, or cost.
Yes. LocalStack runs the same APIs your cloud provider does, so code validated in the local sandbox deploys to production with no code changes.
Mocks are static. LocalStack runs the real APIs against local implementations, with production-grade behavior for testing, debugging, and validation across the full development lifecycle.
Yes. Each developer gets an isolated sandbox, and Cloud Pods let you snapshot and share the exact state of an environment, so any teammate can reproduce a bug on demand. The same sandbox runs per CI job.
Nothing for the workloads it replaces. Sandboxes run on local or self-hosted infrastructure, so dev, test, and CI validation move off the non-production cloud bill regardless of how many run at once.
Give every developer a cloud they can't break
Cloud-native development without the overhead, costs, or risk of the cloud. A cloud-quality sandbox for every developer, AI agent, and pipeline.
