Floci: Locally emulating any cloud service
- ID
- 29140
- Status
- summarized
- Published
- 26 Sep 2026, 4:31 PM
- Fetched
- 28 Sep 2026, 1:59 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://floci.io/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.0
- Created
- 28 Sep 2026, 2:00 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Floci is a set of standalone, MIT-licensed local cloud emulators that run AWS, Azure, GCP and OCI services on your machine without credentials or a cloud account — the AWS one is pitched as a drop-in LocalStack replacement on the same port 4566 with 119 services and a claimed 24 ms cold start. Each cloud gets its own port (Azure 4577, GCP 4588, OCI 4599) and the pitch is explicitly aimed at AI coding agents: throwaway keys, nothing to exfiltrate or bill, and real Lambda/RDS/Redis/Kafka rather than mocks. The claims come from the project's own landing page; the Hacker News thread drew 195 points and 43 comments.
Why it matters
If you let coding agents run against a real cloud account, this is the alternative: point AWS_ENDPOINT_URL at localhost:4566 and agents can iterate with throwaway keys instead of staging credentials. The concrete decision is whether the port-4566 compatibility with LocalStack means a zero-code-change swap for your existing test setup, and whether 'Lambda, RDS, Redis and Kafka run for real' holds up for your stack before you delete your staging-based agent loop. All performance and parity numbers are self-reported, so verify against your own test suite before trusting it.
Discussion angle
The LocalStack drop-in claim at port 4566 is the live-testable part — run one existing test suite against both and see which services diverge, then ask whether 'real Lambda/RDS/Kafka locally' actually removes false positives or just relocates them.