Floci: Locally emulating any cloud service
theanonymousone
171 points
40 comments
September 26, 2026
Related Discussions
Found 5 related stories in 79.5ms across 7,763 title embeddings via pgvector HNSW
- Cloud in a Bottle: making self-hosting accessible to everyone zplizzi · 279 pts · September 06, 2026 · 55% similar
- Fuck Off as a Service (Foaas) speckx · 56 pts · September 03, 2026 · 52% similar
- Show HN: Kedge – Full-stack cloud with forkable VM snapshots and global SQLite wgjordan · 58 pts · July 29, 2026 · 51% similar
- Flux 3 ThouYS · 554 pts · July 24, 2026 · 50% similar
- Codefloe Is a Professionally Hosted Public Git Forge jeremyjh · 57 pts · August 24, 2026 · 49% similar
Discussion Highlights (16 comments)
elendilm
Good work. For us, floci-oci for object storage looks interesting. For everything else we have our own stack.
huffer
I just spilled my coffee; sorry for the trivial remark, but the name means 'pubic hairs' in Romanian. Apologies.. I thought it's better for you to know and ignore than not to (not quite a big population target for you, I imagine, anyway).
aeagentic
Would someone be interested in this but intended for production? Im already running a whole bunch of cloudflare and AWS services in my own AWS fake and it works surprisingly well! :)
mkirsten
This looks very cool! Is this only intended for testing and development, or as a feasible way to migrante away from e.g., GCP as well? I’m interested in something that would allow me to over time migrante away from a GCP project that uses many services today - e.g., Datastore, FileStorage etc.
thegagne
The cool part of this is it’s an example of what’s possible with a community of users armed with AI. Many users, (myself included), had need to test cloud stuff locally, but had no tool to do so. Localstack exists, but it started rug pulling the free tier and they didn’t support all the features. Meanwhile, Floci makes it easy to write your own cloud compatible test suite, then implement the feature to match. I was able to get a good enough coverage on a few features created in a weekend on the $20 tier of Claude to make it useful to me, then others picked up the work to round it out. It’s really cool to see it grow.
microflash
Been using it for a while to run integration tests with Testcontainers [1]. It's very good and much more lightweight than Localstack. [1]: https://testcontainers.com/
kwkelly
fakecloud is another project in the space, AWS only though https://fakecloud.dev/
VoidWhisperer
Most likely a false positive, but worth noting for the people who run the project: Malwarebytes currently flags the site as 'potentially unsafe' when trying to visit it - not sure what the best avenue for them to get that fixed beyond reaching out to Malwarebytes might be
n738
This is awesome, hope to see it mature over the years!
catlifeonmars
Both localstack and floci live in this weird spot where for a lot of my applications, all the cloud-vendor specific stuff is abstracted out anyway. So the only time I need to touch the cloud is for testing the abstractions and do end to end testing. The abstractions can be tested against real cloud APIs as it is generally cheap to do and provides the highest fidelity results. End to end testing includes testing against a production-like environment, so again, more bang for your buck to just test against the cloud. I’ve definitely reached for these local cloud tools from time to time, but in a well-architected piece of software, you aren’t getting that much value from them. Either you don’t have a hard cloud dependency, or you want a high fidelity test of a specific cloud dependency.
michaelastreiko
Local stubs for cloud services are a lifesaver when you're a one-person shop and don't want a surprise bill just to test a webhook path.
kikimora
How on earth I never came across this before? ChatGPD does not know about this project either. Looks very, very promising!
bensyverson
I've looked into developing "digital twins" of APIs that I rely on, similar to the StrongDM pattern, but the models talk me out of it every time. The rationale is that there could be subtle differences or drift between the behavior of the real service and the mocked API. So you may think you're on solid ground, but once you switch to prod, you could see show-stopping differences. I think if I was doing evals on the way an agent interacts with a service (e.g. Slack) the digital twin could make sense, but for rapid iteration or testing, it might not be what you want.
patriciobcs
right on time to try gke
nijave
For AWS, moto
conception
For a hot minute Eucalyptus https://www.eucalyptus.cloud was amazing - even matching aws bugs to keep compatibility. Wish it had rue support/resources to keep going. Maybe a viber will pick up and get it more up to date.