dev-tools 5 min read

Floci: a lightweight local AWS emulator

Floci is a MIT-licensed AWS emulator for local development that emulates 133 services on port 4566, starting in about 24ms inside roughly 13 MiB of memory.

By
Share: X in
GitHub social preview card for floci-io/floci

TL;DR: Floci is a local emulator for AWS services, written in Java under the MIT license, and it listens on port 4566 the way LocalStack does. The project’s docs cover 133 emulated services, and the install guide reports startup in roughly 24 ms inside about 13 MiB of memory. You pull a Docker image or grab a native binary, then point the AWS CLI at localhost.

What it is

Floci describes itself as “Light, fluffy, and always free - The AWS Local Emulator alternative”. The repository is a Maven project, with a pom.xml, a Maven wrapper, and src/main and src/test trees, packaged behind a Docker image and documented with MkDocs under docs/.

The project is young. The repository was created on February 18, 2026, and the last push landed on November 4, 2026, the same day this was written. It currently carries 28,849 stars, 3,208 forks and 170 open issues, and the repository topics are aws, aws-emulation, devops, docker, ec2 and ecs.

There is a page in the docs called migrate-from-localstack.md, which tells you what to expect if you are moving off LocalStack rather than starting from nothing.

How to try it

Docker is the recommended path. The image layers are compressed with zstd, so you need Docker 23.0 or newer plus the compose v2 plugin:

services:
  floci:
    image: floci/floci:latest
    ports:
      - "4566:4566"
    volumes:
      - ./data:/app/data
docker compose up -d

Once it is up, point the CLI at the local endpoint instead of AWS:

aws s3 mb s3://demo-bucket --endpoint-url http://localhost:4566

The image tags split into a variant, which decides what is inside, and a channel, which decides how stable it is:

TagContentsPick it when
latestStandard releaseMost setups
latest-compatAdds the AWS CLI and boto3Your workflow needs them inside the container
latest-baselineARM64 only, no CPU feature requirementRaspberry Pi 4-class ARM64 without LSE
x.y.zPinned standard releaseYou want reproducible builds
nightlyFloating nightly buildYou are tracking main

If you would rather not run Docker at all, every release attaches a standalone executable per platform to the GitHub release. The Linux binaries are the same native builds the image ships, and the macOS and Windows binaries are produced on their own runners and are not bundled into any image.

What it covers

The docs/services directory holds one page per service, 133 of them in total. A cross section of the ones with dedicated pages:

AreaServices with documentation
StorageS3, S3 Tables, S3 Vectors, Transfer, Backup
DatabasesRDS, RDS Data, Redshift, Redshift Serverless, Redshift Data, OpenSearch
MessagingSQS, SNS, Step Functions, Batch, Scheduler, Pipes
Serverless and AIBedrock, Bedrock Runtime, Bedrock AgentCore, SageMaker, Rekognition, Textract, Transcribe, Translate
NetworkingRoute 53, Route 53 Resolver, CloudFront, Private Origin, Verified Permissions, Cloud Map, CloudHSM v2
GovernanceAccess Analyzer, CloudTrail, CloudWatch, Organizations, Resource Groups, Resource Explorer, Service Catalog, Service Quotas, Budgets, Security Hub

A documentation page per service is a reasonable signal of coverage, but it is not a compatibility guarantee. The compatibility-tests directory and the docs/testcontainers page suggest the project is serious about checking emulated behavior against the real thing, so it is worth checking the specific service page you depend on before you migrate a test suite over.

Configuration

The configuration surface is documented separately under docs/configuration, and the page names describe the options directly: application-yml.md, environment-variables.md, ports.md, storage.md, tls.md, partitions.md, multi-account.md, initialization-hooks.md, docker-compose.md, docker.md and docker-images.md, plus an advanced folder.

Two of those are worth calling out. Multi-account setup means you can point different credentials at different account contexts without running several containers, and initialization hooks let you seed state when the emulator starts, which is the piece most local emulators make you script yourself.

When to use it

Floci fits the case where a test suite talks to AWS-shaped APIs and you want that to be cheap and fast. The startup and memory numbers in the install guide are the argument: a container that is ready in under a quarter second and holds about 13 MiB does not slow down a CI matrix the way a heavyweight stack does.

It also fits a team that wants to read the source. The project is Apache-style open, MIT licensed, and small enough to clone and step through.

When to skip it

The service catalog is broad, but depth is uneven across services, and a project this young with 170 open issues will have rough edges. If your pipeline depends on byte-exact parity with a specific managed service, test that service before you move your whole suite across.

Java is the implementation language, so anyone who needs to patch the emulator itself should expect to be in a JVM codebase.

Source and Accuracy Notes

  • Project page: https://floci.io/floci/ (homepage value from the GitHub API)
  • Source repository: github.com/floci-io/floci (MIT license, verified via GitHub API license.spdx_id)
  • Stars at time of writing: 28849
  • The count of 133 services comes from docs/services, and the startup and memory figures come from docs/getting-started/installation.md, both read on 2026-11-04
  • Repository was created 2026-02-18, last pushed 2026-11-04