← Chronicle
Hector Ventura//

State of the Flock #005

Eight Months, Built by People

Eight months in: AWS shipped its own emulator, and this is what makes Floci different, told through the 30+ projects that moved their tests onto it. Plus today's release train and JConf Guatemala.

communitymilestoneopen-source

This week AWS released its own local emulator. I’ll admit it caught me by surprise. But the more I thought about it, the happier I got. When the biggest cloud provider in the world ships an emulator, it says out loud what this community has believed from day one: developers deserve a fast, free local cloud.

It also raises a fair question. If AWS has one now, what makes Floci different?

This issue is my answer, and it’s a story I’ve never told in one place. Eight months ago I open sourced Floci. Nine days later, Dagger swapped LocalStack for it in their CI, using an image that still had my name on it. Two weeks ago, GCHQ did the same, after weighing the alternatives first. In between, more than thirty projects I can point to moved their tests onto Floci, and every one of those moves was a person deciding to trust it. That story comes first. After it: what shipped this morning, my trip to Guatemala, and the usual sections.

AWS Emulator, and what stays the same

On November 11, AWS released AWS Emulator, free and under CC0. AWS says it was written entirely by autonomous AI agents, and that its own team “hasn’t written or reviewed any of the code”. That’s a real engineering achievement, and I mean it.

Floci uses AI too, but people stay at the center. Developers and AI build it together, and every change goes through real people: contributors who open issues, send pull requests, review each other’s code, argue about edge cases, and help each other in Slack at midnight. Many of them tell me they’re having fun. That matters to me more than any service count.

Floci was never only about code. It’s about community, collaboration, and a promise: free, MIT-licensed, no auth tokens, no feature gates. Real engines, not mocks. And not only AWS: Azure, Google Cloud and Oracle Cloud too. Same philosophy, same community, same plan.

The numbers

Month 7 (Oct 15) to month 8 (Nov 15):

  • GitHub stars (AWS emulator): 26,829 to 31,770
  • Forks: 2,928 to 3,498
  • Contributors: 329 to 396 on the AWS emulator, 367 to 443 across all four emulators
  • Merged PRs (all time): 3,409 to 5,327
  • Docker pulls: 4,365,939 to 8,129,007
  • AWS services: 125 to 135
  • Image size (floci/floci): 86.8 MB to 78.0 MB

Ten more services, and the image got smaller. I’ll take that trade every month.

Eight months of moving in

None of these projects asked me first. I found most of them by searching for our image name in other people’s code, and every time felt a bit like finding your name in someone else’s thank-you note. Here’s how it went, month by month.

March: the first one. Dagger was the first well-known project to move (#12048, March 24). The pull request started life as “fix: pin localstack” and ended up replacing it, so Dagger could test its AWS secret provider against SSM and Secrets Manager. It still pins 1.0.4, under the image name Floci had before it moved to its own organization.

April: a government, by template. The UK’s Department for Environment, Food and Rural Affairs (DEFRA) switched the service templates of its Core Delivery Platform to Floci. A template gets copied into every new service, so its one-line comment, “floci is a replacement for localstack”, now lives in more than eighty DEFRA repositories: waste tracking, trade imports, farming grants and more. By repository count, it’s probably Floci’s largest user.

May: the frameworks. This is the month Floci stopped being something projects used and became part of the tools other projects are built on. Apache Camel moved all of its AWS test infrastructure over (#23404, @Croway), and its full AWS test run dropped from 6.5 to 4.5 minutes. Testcontainers for .NET shipped a Floci module (#1690), and Micronaut added Floci to its test resources (#1084, @alvarosanchez).

Brighter swapped Moto for Floci and deleted the guards that used to skip its AWS tests (#4148, @slang25). Kestra and Reposilite left LocalStack the same month. Anyone who builds on one of these now gets Floci without ever choosing it.

Summer: the data projects. Next came the projects that store a lot of data and need S3 and Glue to behave. Trino moved most of its object storage suites over, much of that work by David Phillips (@electrum). Robert Stupp (@snazy) did it twice: Project Nessie replaced MinIO, Azurite and a fake GCS server with Floci’s three emulators (#12743), and Apache Polaris wired in all three (#5061).

DataHub backed its S3, DynamoDB and Kinesis tests with Floci (#18600). Graylog left a comment in its Kinesis test container explaining why LocalStack wasn’t an option. Spring Cloud AWS added Floci support next to LocalStack (#1604, @Mendred) and released it in 4.1.0. zot started running a second copy of its CI against Floci (#4295), and Alchemy made alchemy dev deploy to it (#1154, @sam-goodwin).

September: the measurements. Last issue told this part. The Singapore government’s GoGovSG measured its stack booting 18 seconds faster, Apache Iggy replaced MinIO, and Dapr started certifying its AWS components against Floci (#4578).

October: the ones I didn’t expect.

Twenty, the open source CRM with over 60,000 stars, merged integration tests for its Lambda driver on October 23 (#28574). The reason was right there in the first line: “The Lambda driver had no integration coverage because it needs real AWS.” That’s the whole point of Floci, in a sentence I didn’t write.

Zama builds encryption for blockchains, and its tests needed AWS KMS to sign Ethereum transactions (#4610, October 28). They wrote down why the other options didn’t work: “LocalStack needs an auth token for commercial use, and moto’s KMS Sign hashes a DIGEST message again, so no Ethereum signature it returns verifies.” Floci’s signatures verify. Real engines, not mocks, checked by people who would know.

GCHQ’s Sleeper picks up where last issue left off. Its first migration pull request had closed without merging on October 5. The second one merged on October 30 (#8539) and moved its Java integration tests off LocalStack.

And Union.ai, the company behind Flyte, put Floci inside its “onebox” chart as the local S3 store for an all-in-one install (#622). It’s the first time I’ve seen Floci shipped inside someone else’s product, not just running in their tests.

What eight months add up to. Most people came from LocalStack, after its community edition ended in March. The next biggest group came from MinIO, then Moto. And I couldn’t find a single project that moved onto Floci and then moved off it again. Three more are on their way: Langfuse’s move from MinIO, Payload’s Aurora adapter, and a Floci module for Azure in Testcontainers for .NET.

The ones that matter most aren’t the ones with the most stars. They’re the templates and frameworks: DEFRA’s platform, Camel, Micronaut, Spring Cloud AWS, Testcontainers. Each one hands Floci to people who never picked it, and those people only stay if it keeps working. That’s the job.

What ships today

The release train ran on the last day of October and again this morning, right on the new timetable both times. Here’s today’s:

  • AWS: floci/floci 2.5.0
  • Azure: floci/floci-az 0.17.0
  • Google Cloud: floci/floci-gcp 0.13.0
  • Oracle Cloud: floci/floci-oci 0.7.0

Seven new AWS services. @chhil built AWS Payment Cryptography, both the control plane and the data plane, with PIN operations and card verification values included (#7090, #7396, #7397). @dgl-ai added Signer and X-Ray (#7680, #7733). @allensanborn added EC2 Instance Connect, tested with the unmodified AWS agent running inside the instance (#7473). @rsov added EventBridge v2 (#6962), and @jwoa95 added QuickSight (#7529).

Floci in Kubernetes. @outof-place added a Helm chart (#7749), so a cluster can run Floci the same way it runs everything else.

Snapshots you can restore. @jibin-jusdb made RDS snapshots and restores work for MySQL and MariaDB (#7747), and added snapshots for DocumentDB clusters (#7585) and ElastiCache (#7744). @vuthehuyht kept going on Redshift: snapshot copies, audit logging to S3, and most of the COPY options people actually use.

On the other clouds. Azure learned role definitions and role assignments (floci-az#656), and its template deployments now work at management-group scope and resolve Key Vault references (floci-az#640, floci-az#641). On GCP, @gafiatulin closed BigQuery’s gaps with struct * (floci-gcp#582), David Opaogun (@avison9), now a floci-gcp maintainer, added the Managed Kafka schema registry (floci-gcp#607), and @midhun-pk brought RSA-PSS signing and key import to Cloud KMS (floci-gcp#592, floci-gcp#551). On Oracle Cloud, Database with PostgreSQL gained backups, point-in-time recovery and replicas (floci-oci#105, floci-oci#107).

Everything else is in the release notes above. The next train leaves on November 30.

In the room: JConf Guatemala

On November 7 I was at JConf Guatemala, at Centro TICS in Guatemala City, giving a talk called “Construye tu nube localmente con Floci”: build your cloud locally with Floci.

I started with how to get going, then why a local emulator pays off: in day-to-day development, in CI, in DevOps work, and in the fast loops that AI agents need. The middle of the talk was a side-by-side, timing the same operations against real cloud services and against Floci on a laptop. I closed with what matters once more than one person or pipeline shares a machine: Floci runs multiple accounts, multiple regions and Docker namespaces, so isolated environments can live side by side.

Hector Ventura speaking into a microphone at a lectern, with a Floci-stickered laptop on the lectern and the Intecap and Guatemalan flags in the background
Hector Ventura presenting “Construye tu nube localmente con Floci” at JConf Guatemala.
About forty attendees seated in the Intecap Centro TICS auditorium in Guatemala City, with Hector in the front row wearing a speaker badge
The room at Centro TICS, after the talk.

The questions afterwards were about services: Kubernetes, RDS, IAM authentication. And then people asked about the future of Floci. Four days later, AWS shipped its own emulator, and that question got a lot more interesting.

Four people standing in front of the Guatemala Java User Group and Los Altos JUG banners, one wearing a Floci cap and Hector holding a Duke figurine
From left: Priamo Germosen (@pgermosen), maintainer of the Floci AWS emulator; Eudris, lead and co-creator of JUG Dominicano; Hector Ventura (@hectorvent), creator of the Floci suite; and Maria, co-creator of the Guatemala JUG.

Thank you to the Guatemala Java User Group for the invitation and for the hospitality, from the first hour to the last. And if you’ve never been to Guatemala, go. Come for the history, stay for how beautiful it is, and you’ll understand why I already want to go back.

A green hillside with grass-roofed buildings and dirt paths, looking out over a valley and mountains under low cloud at Hobbitenango, Guatemala
Hobbitenango, in the Guatemalan highlands.

Flock highlights

75 people sent their first pull request to one of the emulators this month, 66 of them to the AWS emulator. Welcome, all of you.

Here’s the number I’m proudest of: 1,856 pull requests merged on the AWS emulator this month, and only 80 of them were mine. That’s 4%, down from 11% last month. When I open sourced it, it was all of them.

floci-gcp has a second maintainer. David Opaogun (@avison9) joined its maintainer file on November 7 (floci-gcp#612). David has 42 merged pull requests there so far, including the Managed Kafka schema registry in today’s release. Last issue I said a couple of people had answered the co-maintainer ask privately and I was evaluating them. David is where that landed. Welcome, David (@avison9). All four emulators now have at least two names on them, and the maintainer files match what these issues say.

@midhun-pk showed up on two clouds at once, both times in key management: RSA-PSS signing and key import in Cloud KMS on GCP, and key import for OCI’s KMS (floci-oci#79, floci-oci#80). That made @midhun-pk the only first-timer on floci-oci this month.

And the Java Testcontainers module caught up with the other four. @cfranzen wrote both missing modules, GCP and OCI, which merged on October 17 (#440, #465) and shipped in 2.17.0.

Sponsors this month

Two new sponsors joined this month. Blake Girardot became a Friend of the Flock on October 24, and RangeWX joined the Community Sponsors on November 6. Welcome, both of you.

And to everyone who has ever sponsored Floci, thank you:

Sponsorship buys gratitude and nothing else. Every emulated service is free for everyone, forever, and no sponsor gets features, priority, or roadmap influence that the rest of the Flock doesn’t. The full list is on floci.io.

What’s not going well

Some emulators are still mostly me. The AWS emulator has grown past me, but the smaller ones haven’t yet. I wrote 59% of this month’s merged pull requests on floci-az, and 50 of the 52 on floci-oci. The co-maintainer ask brought one new name this month: David Opaogun (@avison9), on GCP. Azure and Oracle Cloud each have two names in their maintainer files, but the pull requests there are still mostly mine.

One ask this month

If your project runs on Floci, tell me. I found everything in “Eight months of moving in” by searching other people’s code, and I’m sure I missed more than I found. Reply in Discussions with a link, and you’ll be in the next one.

Thank you

To everyone who moved a test suite onto Floci without telling me, and to everyone whose pull request is in today’s train: thank you. If you’ve ever contributed to Floci, this is your project too.

Floci stays free, MIT-licensed, no gates, no telemetry. Forever.

Same time next month for #006.

Join the Flock: GitHub · r/floci · Slack · LinkedIn

Any Cloud. Locally. Let’s keep Emulating.

#opensource #aws #azure #googlecloud #oraclecloud #devops #testing #docker #java