[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3ezl2o77v5u49":3},{"code":4,"message":5,"data":6,"timestamp":51},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":26,"summary_md":27,"topic":28,"github_topics":31,"license":41,"homepage":42,"updated_at":43,"history":44},"floci-io\u002Ffloci",13,"Light, fluffy, and always free - The AWS Local Emulator alternative","Java",27101,2974,42,249,[16,22],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},49793744,"Floci: Local AWS Emulator for Development, Testing, and CI",3,0,"2026-09-21",{"id":23,"title":24,"points":19,"comments":20,"posted_at":25},48103426,"Floci: Light, fluffy, and always free – The AWS Local Emulator alternative","2026-05-12","A local AWS emulator for developers and CI pipelines that need AWS-shaped services without an account or paid tiers.","Floci is worth a look if you write AWS-dependent code and want it running locally without an account, auth token or paid tier. The catch: it emulates a broad surface, so you need to test the specific services you rely on rather than assume parity.\n\n## The problem\nA developer wants to exercise S3, DynamoDB or a Lambda handler before pushing. Today that means either a shared cloud account, credentials, and cleanup, or a narrow mock that drifts from real AWS behavior. Floci replaces that step with a local endpoint: the same SDK and CLI calls go to `http:\u002F\u002Flocalhost:4566`, and resources appear locally. The result is a local workflow that does not touch a cloud account for day-to-day development.\n\n## What's different\nFloci's bet is breadth combined with real Docker for services where behavior matters. Lambda, RDS, ECS, EC2, EKS and several others run as Docker-backed workloads rather than shallow HTTP mocks, according to the README. Stateless services are handled directly by the emulator, and storage can be in-memory, persistent, hybrid or write-ahead-log, so you choose how much state survives a restart. The project also ships a compatibility suite with 2,576 automated tests across five SDKs and Terraform, OpenTofu and CDK, which is the most useful evidence that standard tooling works against it.\n\nThe trade-off is that a broad service list is not a guarantee of behavioral fidelity for every API. The compatibility tests are self-reported by the project, and the README's comparison table is the author's own claims, including startup and memory figures. If you depend on subtle AWS semantics, per-service differences may still surface.\n\n## Who should try it\nGood fit: a developer who runs AWS SDK code or Terraform locally and wants a free endpoint with no login friction; a team wiring CI that needs AWS-shaped services on each run; someone migrating off a community edition that now requires tokens. Poor fit: a team that needs exact production parity for a service not represented in the compatibility suite, or one already comfortable with a different emulator and no migration pressure. The CLI quick start is optional; the README also documents Docker Compose and points to a [Terraform guide](https:\u002F\u002Fgithub.com\u002Ffloci-io\u002Ffloci\u002Fblob\u002Fmain\u002Fdocs\u002Fgetting-started\u002Fterraform.md).\n\n## Requirements and limitations\nDocker is central: the README says the CLI is the fastest path, and Docker-backed services and the web console rely on it. The console at `\u002F_floci\u002Fui` runs as a sidecar container that is pulled on first request, so the first open needs network access and Docker networking. Persistent and WAL storage modes require decisions about where state lives; switching modes has ongoing implications for test isolation. Broad compatibility is tested, but the README's service table is large enough that you should check the [compatibility tests](https:\u002F\u002Fgithub.com\u002Ffloci-io\u002Ffloci\u002Fblob\u002Fmain\u002Fcompatibility-tests\u002F) for your specific SDK and tooling before committing. There is also a published [console contract](https:\u002F\u002Ffloci.io\u002Ffloci\u002Fui\u002Fconsole-contract\u002F) if the built-in UI does not suit you.\n\n## HotRepo's take\nHotRepo's dated view is thin: 27,096 stars on 2026-10-24 and 27,097 on 2026-10-25, with two daily-board appearances in that window. That is a snapshot, not evidence of durable momentum, so persistence cannot be judged yet. The project was created on 2026-02-18. For adoption, verify the compatibility coverage for the exact services and IaC workflow you use, not just the headline test count.",{"slug":29,"name":30},"devops","DevOps & Self-hosting",[32,33,29,34,35,36,37,38,39,40],"aws","aws-emulation","docker","ec2","ecs","localstack","s3","sqs","testcontainers","MIT","https:\u002F\u002Ffloci.io\u002Ffloci\u002F","2026-10-25T03:10:14Z",[45,49],{"date":46,"stars":47,"stars_gained":48},"2026-10-24",27096,41,{"date":50,"stars":11,"stars_gained":13},"2026-10-25",1792906193]