Key takeaways
- Test AWS-dependent code locally: Floci is a free, open-source AWS emulator with no cloud account, auth token or paid feature gates required.
- Keep your tools: point your AWS SDK, CLI, Terraform, CDK or OpenTofu at it instead of the real cloud.
- Several services run real Docker containers, including Lambda, RDS, ECS and EC2, rather than shallow mocks.
- By the project's own table, startup is about 24 ms against about 3.3 s for LocalStack Community.
- The catches: some services are stubs or simulations, and Docker-backed services need the Docker socket.
What it is
Floci describes itself as a free, open-source local AWS emulator for development, testing and CI. It is written mainly in Java, released under the MIT licence, and the code is on GitHub at floci-io/floci.
The problem it solves
Anyone writing software that talks to AWS needs somewhere to run it that is not a live cloud account. Floci says it gives you AWS-shaped services on your machine without requiring a cloud account, an auth token or paid feature gates.
It is also aimed at teams already using LocalStack. The README calls Floci a drop-in replacement for LocalStack Community and the no-strings-attached alternative.
What you get
- Familiar tools: you point your existing AWS SDK, CLI, Terraform, CDK, OpenTofu or test suite at the local endpoint.
- More realistic behaviour: Lambda, RDS, ECS, EC2 and several other services use real Docker-backed execution instead of shallow mocks.
- Suited to pipelines: the native image starts in milliseconds and keeps idle memory low.
- Your choice of durability: in-memory, persistent, hybrid or write-ahead log storage.
- A published test base: the project reports 2,576 automated compatibility tests across 5 SDKs and 3 IaC tools.
How it compares
The README sets Floci against LocalStack Community in its own table. These are the project's figures, not ours: startup of about 24 ms against about 3.3 s, and idle memory of about 13 MiB against about 143 MiB. We did not measure either tool.
The catches
- Emulation is not AWS: Bedrock Runtime returns dummy responses, and Transcribe jobs complete immediately with no real audio processing.
- Some features are simulated: AWS FIS experiments do not inject faults into other services, and Application Auto Scaling policies are stored but inert.
- Docker access: Docker-backed services require the Docker socket, so think about what you are granting.
- Loose credentials: any non-empty values work unless you enable stricter service-specific checks.
- Uneven tooling: the Go Testcontainers module is still listed as in progress.
What we did not test
We did not run Floci, start any service, or compare it with LocalStack or AWS. Every claim here comes from a literal quote in the project's README or the GitHub API, and the speed, memory and test figures are the project's own.
Verdict
Editors' view: this is worth a look for developers and CI maintainers who build on AWS and want to test without a cloud account, especially anyone weighing a move away from LocalStack Community. If your code leans on the stubbed or simulated services, check coverage first, and keep a final run against real AWS.
Sources
Need help adopting this, or have a software project in mind?
Tell us what you are building. The initial consultation is free. Email [email protected] or follow @zolnaltd.
Start a conversation →