Local cloud emulation was a comfortable assumption for years. You pulled an image, started a container, and your test suite talked to an S3 bucket that belonged to nobody. Then LocalStack retired its community edition in March 2026: using it now requires authentication tokens, and security updates to the old community image were frozen. For teams whose CI pipeline stood on that container, this was not a product change. It was a deadline.
Floci is the answer that grew into that gap. The project describes itself as the light, fluffy, always-free AWS emulator — an MIT-licensed drop-in for LocalStack with no account, no token, no enterprise feature flags, and no announcement of a later edition that quietly costs money. The repository sits at roughly 28,000 stars on GitHub, and by the trending numbers it picked up over a thousand of them on a single day this week.
The feature set is no longer the compromise it once would have been. Version 1.5.5 covers 31 services, MSK and Kafka included, all behind a single endpoint. Startup is quoted at around 24 milliseconds — a number that only means anything once you have felt it inside a test suite that wants a fresh state for every case. Where execution fidelity actually matters, the project leans on real Docker-backed services rather than stubs that only mimic an API's shape.
The interesting part is not the technology but the reason it is needed right now. A local emulator is trust infrastructure. It exists so a developer can try things without generating an invoice, and so a pipeline can run without someone provisioning a cloud account with permissions attached. The moment that emulator demands an account, it stops being a local emulator and becomes a remotely administered service with a local face. The licensing question and the network-boundary question turn out to be the same question.
That explains the violence of the GitHub response. It is not about milliseconds of startup time. It is about a dependency everyone had filed under "obvious" suddenly arriving with terms — and about an MIT-licensed project removing the terms rather than explaining them.
Floci is not without irony here. It exists by replacing something, and its own future rests on exactly the promise it holds against LocalStack: that "always free" will still be true after the growth. The licence, not the marketing, is what settles that — MIT gives the community the right to fork the project if the commitment ever stops being honoured.
For most teams the decision is unglamorous. If the pipeline is pinned to the old community image and the tokens are breaking it, an equivalent replacement with the same surface is simply the correct answer. The proof does not live in the repository; it lives in the first green build after the swap.
And the lesson is bigger than the tool. The most convenient layer in a developer's kit is also the most fragile: it is convenient precisely because someone else absorbed the cost of maintaining an imitation of a cloud. Anyone testing locally against a rebuilt cloud ought to know what licence that rebuild sits under, and whether they could keep running it themselves if they had to.
