floci
floci-io/flociReviewed by AI
Checked by RepoPicks Radar on
What is floci?
Floci is a local stand-in for Amazon Web Services. You start one container and point the AWS command line, the SDKs, Terraform or your test suite at http://localhost:4566 instead of the real cloud, with no Amazon account and no token. Dozens of services are covered; the ones where fidelity matters (Lambda, RDS, ECS, EC2, Kafka, OpenSearch) start real Docker containers, and a browser console at /_floci/ui shows what you created. It is a tool for programmers: you need Docker and a terminal.
floci is free and open source (MIT) and can replace LocalStack and Amazon Web Services.
How easy is it to install floci?
D · terminal, several tools or a specific graphics card · Windows
- Windows D
- macOS D
- Linux D
All three platforms are a D and work the same way: install Docker, write a small compose file or use the separate command-line tool, then set environment variables and type AWS commands in a terminal. There is no installer or graphical setup, and nothing here is meant for someone who does not program.
Coming soon: install in 1 click with the RepoPicks app.
floci on GitHub
- Stars
- 31,274on Nov 10, 2026
- Downloads
- —all releases
- Growth
- +1,763stars in 6 days
Stars over time
Facts
- Runs on
- Windows, macOS, Linux
- You need to install
- Docker
- To build from source
- Docker
- Disk space
- not determined
- Accounts or keys
- None
- Cost
- Free · MIT licence, no account, token or paid tier; the README says "always free". You pay nothing, but the containers it starts use your own disk, memory and CPU.
- License
- MIT (Permissive)
- Can replace
- LocalStack, Web Services
- Last change on GitHub
- Nov 10, 2026
floci risk signals (5)
- Attentionneeds the docker socket as root
To start its Docker-backed services and the web console, the README and docker-compose.yml mount the host's Docker socket into the container: "- /var/run/docker.sock:/var/run/docker.sock", and the documented run command adds "-u root". A container with that socket can control every container and image on your machine.
AI review
- Attentionreachable from the network with any credentials
README: "Credentials can be any non-empty values unless you explicitly enable stricter service-specific auth checks", and FLOCI_SERVICES_UI_BIND_ADDRESS is documented as "Unset publishes on every interface". The repository's docker-compose.yml publishes port 4566 plus the ranges 6379-6399, 7001-7099 and 9200-9299, so anything your machine can be reached from can use it.
AI review
- Infodownloads and runs many third party images
The default images table pulls software from other projects, some on moving tags: valkey/valkey:8, postgres:16-alpine, mysql:8.0, mongo:7.0, redpandadata/redpanda:latest, rancher/k3s:latest, registry:2, apache/airflow. The console also "pulls the console image" on the first request to /_floci/ui.
AI review
- Infonative binary claim not in the latest releases
The README says "Each release also ships a standalone floci-aws binary for Linux, macOS and Windows", but the three most recent releases recorded here (2.4.0, 2.3.0 and 2.2.0) list no platform binaries at all.
AI review
- Infoseveral services are only pretend
The service notes mark parts as stubs: "Textract: In-process stub", "Transcribe: jobs complete immediately, no real audio processing", "Bedrock Runtime: In-process stub - Dummy Converse and InvokeModel responses", "AWS FIS: experiment execution is a safe control-plane simulation and does not inject faults". Code that passes here can still fail against the real cloud.
AI review
Evidence is shown in its original language.
What Radar could not check about floci
- How closely each emulated service matches the real Amazon service beyond the project's own test counts.
- Whether a standalone binary is really available for your system, since the latest releases list none.
- How much disk and memory the whole thing uses once all the extra Docker images are downloaded (the checks could not estimate it).
- Whether the published speed and memory comparisons hold on your machine.
- How quickly the project follows changes in the real Amazon APIs.