LocalStack Alternatives: Free AWS Emulators for Localhost and CI
Since March 23, 2026, the LocalStack image needs an account and an auth token, CI included. Here is what teams are moving to, how each tool runs, and how to switch without breaking the pipeline.
For years the default way to run AWS on localhost was one container: localstack/localstack, port 4566, AWS_ENDPOINT_URL=http://localhost:4566, no sign-up. That changed on March 23, 2026. LocalStack for AWS now ships as a single image, and its latest releases need a LocalStack account and an auth token, including in CI. The same day, the localstack/localstack GitHub repository was archived.
LocalStack still has a free Hobby plan for non-commercial work, and free access for students and open-source projects. Commercial teams need a paid plan; check localstack.cloud/pricing for current terms rather than any number quoted secondhand. Pinning an old Community tag keeps a pipeline green for a while, but that image gets no fixes and drifts further from AWS with every API change.
So most teams that relied on Community are choosing between paying, pinning or moving. This guide covers the moves: AWS's own emulator, released on November 11, 2026, the open-source emulators that copy LocalStack's port-4566 model, Moto, and the single-service emulators that are often all a test suite needs.
At a glance
| Tool | What it is | License | How it runs | Best for |
|---|---|---|---|---|
| AWS Emulator | AWS's own local emulator of the AWS APIs, released November 11, 2026. | CC0-1.0 | Linux RPM or Debian package; a Docker image you build yourself on macOS and Windows. HTTPS on 127.0.0.1:9297. | Wide API coverage, with requests and errors shaped like AWS's. |
| Floci | An open-source AWS emulator built as a drop-in for the LocalStack container. | MIT | The floci/floci Docker image or the floci CLI. Port 4566. | Swapping the image in docker-compose.yml and changing little else. |
| MiniStack | An open-source AWS emulator that keeps LocalStack's conventions. | MIT | The ministackorg/ministack Docker image or pip install ministack. Port 4566. | Suites that lean on LocalStack init scripts and Terraform or CDK. |
| kumo | A lightweight AWS emulator written in Go. | MIT | A single binary or ghcr.io/sivchari/kumo. Port 4566. | Go teams and CI jobs that want the smallest possible footprint. |
| fakecloud | An open-source AWS emulator that puts conformance to AWS first. | AGPL-3.0 | ghcr.io/faiscadev/fakecloud, Homebrew, an install script or cargo. Port 4566. | A few services that must behave exactly like AWS. |
| Moto | The long-standing Python library for mocking AWS, with a standalone server mode. | Apache-2.0 | @mock_aws inside Python tests; moto_server or the motoserver/moto image (port 5000) for other languages. | Fast Python tests that need no separate process. |
| Single-service emulators | DynamoDB Local, ElasticMQ for SQS, S3Mock for S3. | AWS terms; Apache-2.0; Apache-2.0 | amazon/dynamodb-local (port 8000), softwaremill/elasticmq-native (port 9324), adobe/s3mock. | Suites that only touch one or two AWS services. |
Service lists on the newer projects change often. Check each project's own docs for the services and operations you call before you switch.
The alternatives, one by one
AWS Emulator
License: CC0-1.0. Runs: Linux RPM or Debian package; a Docker image you build yourself on macOS and Windows. HTTPS on 127.0.0.1:9297.
AWS Emulator is built from the same AWS API models the SDKs use, so request and error shapes match AWS. It is written in Rust, and AWS says autonomous agents write and maintain the code. For each release, AWS publishes how many fidelity tests pass per service (as k of n), and the tests themselves are public, including the failing ones. An operation it doesn't implement yet returns HTTP 501, so a test fails loudly instead of passing against a stub.
It is not a drop-in for a LocalStack setup. On start it generates its own credentials, config file and certificate under ~/.aws/emulator/9297/, and every request must be SigV4-signed with those keys. You point the SDK at it with AWS_ENDPOINT_URL, AWS_SHARED_CREDENTIALS_FILE and AWS_CONFIG_FILE, and some SDKs (Java, for one) need to be told to trust its certificate. Rust tests can skip the server entirely: the aws-emulator-embedded crate runs an isolated emulator inside each test process.
Watch out for:
- It does not evaluate IAM or resource policies the way AWS does: a request AWS would deny can succeed.
- One account, no cross-account or cross-Region behavior.
- No published Docker image; on macOS and Windows you build one from the Dockerfile in its docs.
- Sends anonymous usage and error data by default; you can turn it off.
- Check the fidelity score for every service you call in its documentation before you rely on it.
Floci
License: MIT. Runs: The floci/floci Docker image or the floci CLI. Port 4566.
Floci listens on 4566 and answers LocalStack-style endpoints, so most suites only change the image name. It is a native build, so it starts fast and idles small, which matters when every CI job boots its own copy. Services that run code or databases (Lambda, RDS, ECS and others) start real containers next to it. The same project also ships emulators for Azure, GCP and OCI on their own ports.
It went public in February 2026 and has moved quickly since, so coverage of edge cases is still being filled in by its users. Run your own suite against it before you trust a service list.
Watch out for:
- Container-backed services need the Docker socket mounted, which is a real risk on shared self-hosted CI runners.
- Young project: pin a version and read the changelog before you upgrade.
MiniStack
License: MIT. Runs: The ministackorg/ministack Docker image or pip install ministack. Port 4566.
MiniStack keeps more of LocalStack's surface than most: the /etc/localstack/init/ready.d init-script path and some LOCALSTACK_* environment variables still work, and it can back RDS with real PostgreSQL or MySQL containers. Its docs include a migration checklist from LocalStack that is worth reading even if you pick something else.
Watch out for:
- Its own docs say IAM policies are not enforced and some services store metadata only.
- Read the service page for anything beyond S3, SQS, SNS and DynamoDB before you plan around it.
kumo
License: MIT. Runs: A single binary or ghcr.io/sivchari/kumo. Port 4566.
kumo keeps state in memory by default and writes it to files when you set KUMO_DATA_DIR, so you can choose a clean start for tests or a persistent one for local development. With the AWS SDK for Go v2, setting the base endpoint to http://localhost:4566 is the whole change.
Watch out for:
- Still on v0.x releases with one main maintainer: map the depth of the services you use before adopting it across a company.
fakecloud
License: AGPL-3.0. Runs: ghcr.io/faiscadev/fakecloud, Homebrew, an install script or cargo. Port 4566.
fakecloud generates its conformance tests from AWS's Smithy models and runs the upstream Terraform AWS provider acceptance tests in its CI. It can verify SigV4 signatures and enforce IAM, two things most emulators skip, and ships its own test SDKs for several languages for when a test needs to see more than the AWS SDK shows.
Watch out for:
- It covers fewer services than the broad emulators; check its operations index for yours.
- AGPL-3.0. Its FAQ says using it as a dev and test dependency has no AGPL implications for your application; bundling it or offering it as a service to others is a question for your lawyer.
Moto
License: Apache-2.0. Runs: @mock_aws inside Python tests; moto_server or the motoserver/moto image (port 5000) for other languages.
Moto predates LocalStack's change by years and is still actively maintained. In Python, the @mock_aws decorator intercepts boto3 calls inside the test process, which makes it the fastest option there is. Server mode exposes the same in-memory state over HTTP so a Java, Go or Node suite can point AWS_ENDPOINT_URL at it.
Moving from LocalStack to Moto usually means moving tests closer to the code rather than swapping an image: Moto mocks the AWS API in memory, it is not a stand-in for a whole local cloud.
Watch out for:
- Not port-compatible with LocalStack (5000 by default), so endpoint configuration changes.
Single-service emulators
License: AWS terms; Apache-2.0; Apache-2.0. Runs: amazon/dynamodb-local (port 8000), softwaremill/elasticmq-native (port 9324), adobe/s3mock.
Plenty of LocalStack setups only ever started S3, SQS or DynamoDB. For those, a mature tool built for one service is often closer to AWS than a broad emulator. DynamoDB Local is AWS's own. ElasticMQ covers FIFO queues, dead-letter queues, visibility timeouts and long polling. S3Mock fits JVM suites through Testcontainers and JUnit.
If you used MinIO as a local S3: its GitHub repository was archived in April 2026, so pick something that is still maintained for new setups.
Watch out for:
- S3Mock supports path-style requests only, and accepts presigned URLs without verifying them.
- Each one is another container and another endpoint to configure.
Staying on LocalStack
If you depend on features only LocalStack has (Cloud Pods, persistence snapshots, its web app and resource browser, chaos testing), none of the tools above replace them. Staying means each developer uses their own auth token and CI uses a CI auth token stored as a secret and injected as LOCALSTACK_AUTH_TOKEN. Never commit a token or print it in logs.
Which one to pick
- Change one line in docker-compose.yml: Floci or MiniStack. kumo if you want a single small binary.
- Many services, errors that match AWS: AWS Emulator, after checking its fidelity score for each service you call.
- A few services that must behave exactly like AWS, IAM included: fakecloud.
- Python unit tests: Moto, in process.
- Only S3, SQS or DynamoDB: the single-service emulators.
- You need Cloud Pods or LocalStack's web app: stay on LocalStack with a token.
Mixing is normal: a broad emulator for most services and ElasticMQ or DynamoDB Local where fidelity matters most.
Switching without breaking CI
- List what you actually call:
SERVICES=in compose files, scripts under/etc/localstack/init/, everyendpoint_urlin test code. - Find what is LocalStack-only (Cloud Pods, snapshots, LocalStack-specific endpoints) and decide what replaces it.
- Write golden tests for the flows that must not break before you swap anything.
- Try two candidates on a branch with a
docker-compose.override.yml, and compare pass rate, start-up time and flakiness. - Check the differences that bite: IAM enforcement, SigV4, path-style versus virtual-hosted S3, presigned URLs, persistence, and how state resets between tests.
- Run the old and new setups side by side in CI for a while, and keep the old configuration so you can roll back.
- Tell your coding agents. Put the emulator, port and endpoint in
AGENTS.md, or they will keep writinglocalstack/localstackinto compose files.
What an AWS emulator won't cover
Every tool here stops at AWS. If the same tests call Stripe, Slack or GitHub, those calls still go to the internet, with the rate limits and live credentials that come with them. They need their own local stand-ins, and the same rules apply: state that persists across calls, a clean reset between tests, and evidence that the stand-in matches the real API. Rystic builds stateful simulators for APIs like Stripe, Slack and GitHub that run locally or in CI and are verified against the real APIs before each release.





