Floci: The Fast, Free Local Cloud Emulator Built for AI-Assisted Development

Published on AskGenAI | July 2026

What Is Floci?

Floci is a family of fast, free, open-source local cloud emulators that let you run AWS, Azure, and Google Cloud services on your laptop — no cloud account, no API keys, no billing surprises.

Named after cirrocumulus floccus (the cloud formation that looks like popcorn 🍿), Floci is built with Quarkus Native and compiled with GraalVM Mandrel for native binary speed.

One container per cloud. One port each. No auth tokens. No feature gates. No telemetry. Ever.

bash

docker run --rm -p 4566:4566 floci/floci:latest        # AWS
docker run --rm -p 4577:4577 floci/floci-az:latest     # Azure
docker run --rm -p 4588:4588 floci/floci-gcp:latest    # Google Cloud

That’s it. No sign-ups. No API keys.

Why Floci Exists Now

In March 2026, LocalStack’s community edition sunset — now requiring auth tokens and freezing security updates. Microsoft’s Azure emulators remain fragmented across Azurite, Cosmos DB Emulator (Windows-only), and Functions Core Tools. Google’s gcloud beta emulators each run on different ports with different configs.

Floci fills all of that with one consistent emulator family — and stays MIT-licensed forever.

Table

FeatureFlociLocalStack CommunityAzurite + Friendsgcloud Emulators
Auth tokenNoneRequired (since Mar 2026)N/AN/A
Unified endpointOne port per cloudOne portPer-servicePer-service
Startup time (AWS)~24 ms~3.3 sn/an/a
Idle memory (AWS)~13 MiB~143 MiBn/an/a
Docker image size~90 MB~1.0 GBvariesvaries
LicenseMITRestrictedvariesvaries
Real Docker engines✅ Lambda, RDS, EKS, MSKpartialpartial

Three Emulators, One Philosophy

☁️ Floci for AWS — Port 4566

GitHub:github.com/floci-io/floci

68 services including EC2, ECS, EKS, Lambda, RDS, ElastiCache, MSK, OpenSearch, ECR, CodeBuild, S3, DynamoDB, SQS, SNS, IAM, STS, KMS, Cognito, EventBridge, Step Functions, CloudFormation, API Gateway — with 100% SDK compatibility.

☁️ Floci-az for Azure — Port 4577

GitHub:github.com/floci-io/floci-az

Blob, Queue, Table, Cosmos DB, Functions, App Configuration, Key Vault, and Event Hubs on a single endpoint. No more running Azurite, Cosmos DB Emulator, and Functions Core Tools side by side.

☁️ Floci-gcp for Google Cloud — Port 4588

GitHub:github.com/floci-io/floci-gcp

Cloud Storage, Pub/Sub, Firestore, Datastore, Bigtable, Spanner, and Cloud Functions on one port. One container instead of seven separate gcloud beta emulators processes.

What Makes Floci Different

Real Engines, Not Mocks

Lambda, RDS, ElastiCache, ECS, EC2, EKS, MSK, OpenSearch, ECR, and CodeBuild spin up real Docker containers and speak real wire protocols (RESP, JDBC, k8s, IMDS). IAM auth and SigV4 validation work the same as production AWS.

Drop-In Replacement

Same ports. Same wire protocols. Switch from LocalStack, Azurite, or gcloud emulators by changing your endpoint URL — zero application code changes.

bash

export AWS_ENDPOINT_URL=http://localhost:4566
pytest tests/

Consistent Across Clouds

Same Quarkus Native foundation, same storage architecture (memory / hybrid / persistent / WAL), same Testcontainers patterns. Learn one Floci, you’ve learned them all.

Built for AI-Assisted Development

This is where Floci gets interesting for the AskGenAI community.

Coding agents write cloud code faster than ever, but they can’t safely run it against a real account. Point them at Floci instead:

Table

ProblemFloci Solution
Credentials to leakAgents connect with throwaway keys. No real cloud secrets in context.
Slow iteration loop24 ms cold start. Agents spin up, test, and tear down inside the edit loop.
Mock-shaped false positivesLambda, RDS, Redis, Kafka run for real. Code behaves the same in production.
Blast radiusWorst case: reset a local container. Not your staging environment or cloud bill.

Works with every SDK, CLI, Terraform/OpenTofu module, and test runner your agents already use.

Developer Tools: CLI + UI

Floci CLI

Unified command-line interface for all emulators:

bash

curl -fsSL https://floci.io/install.sh | sh
floci start
floci doctor

One install covers AWS, Azure, and GCP.

Floci UI

Visual dashboard to browse resources, inspect data, and manage services across all three clouds from one place.

Testcontainers Support

Table

LanguageModule
Javaio.floci:testcontainers-floci
Pythontestcontainers-floci-python
Node.jstestcontainers-floci-node
Gotestcontainers-floci-go
.NETtestcontainers-floci-dotnet

Plus floci-duck: a DuckDB-backed query sidecar powering Athena and Firehose.

Use Cases for AI Engineers

Table

Use CaseHow Floci Helps
Local MCP server developmentTest S3/DynamoDB integrations without AWS credentials
RAG pipeline testingRun OpenSearch, S3, and Lambda locally for vector search pipelines
LangGraph agent deploymentValidate ECS/EKS configurations before cloud deployment
CrewAI multi-agent systemsLocal Pub/Sub, EventBridge for agent communication testing
CI/CD for AI projectsEphemeral test environments in every pipeline job
Workshops & onboardingTeach cloud services with zero billing risk

Quick Start

bash

# Install
curl -fsSL https://floci.io/install.sh | sh

# Start and configure environment
floci start && eval $(floci env)

# Test S3
aws s3 mb s3://my-bucket
echo "Why pay for S3 when floci is free? 🎉" > hello-floci.txt
aws s3 cp hello-floci.txt s3://my-bucket/
aws s3 cp s3://my-bucket/hello-floci.txt hello-back.txt
cat hello-back.txt

68 AWS services ready on :4566.

License: MIT Forever

Everything is MIT licensed. Fork it, embed it, ship it. No “community edition” sunset. No enterprise feature flags.

Resources

Have you used Floci for local cloud development? Share your experience or ask questions about integrating it with your MCP servers, RAG pipelines, or LangGraph agents on AskGenAI.

This article is based on Floci’s open-source documentation and website, licensed under MIT.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top