Any cloud.
Locally.

A local cloud your coding agents can't break. AWS, Azure, GCP and OCI emulators that start in 24 ms: no credentials, no bill, no blast radius.

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

# Start the AWS emulator and load its endpoints
floci start && eval $(floci env)
126 AWS services ready on :4566. S3 · SQS · DynamoDB · Lambda · RDS · +121 more

Needs Docker or Podman running. Homebrew, Windows and other options

Give your AI agents a cloud they can't break.

Coding agents write cloud code faster than ever, but they can't safely run it against a real account. Point them at Floci instead: a local cloud to build, run, and verify against. Instant, free, and credential-free.

The agent loop, on any cloud

# agent task: add an upload endpoint backed by S3
floci start
eval $(floci env)       # endpoint → :4566
aws s3 mb s3://uploads
pytest tests/           # ✓ no AWS account used

Teach your agent once

# Asks which agents to install it for
npx skills add floci-io/floci-cli

The Floci skill teaches Claude Code, Codex, Cursor, Kiro and other coding agents to run the emulators with floci-cli.

No skill support? Paste these rules into AGENTS.md or CLAUDE.md
## Local cloud (floci)
- Never run code or tests against a real cloud account. Use floci instead.
- Start the emulator you need: `floci start` (AWS), `floci az start`, `floci gcp start` or `floci oci start`.
- Load its endpoints before running anything: `eval $(floci env)` (or `floci az env`, `floci gcp env`, `floci oci env`).
- State is disposable: `floci stop` then `floci start` gives you a clean cloud.

Works with Claude Code, Cursor, GitHub Copilot, OpenAI Codex, Aider and Gemini CLI: anything that can run a shell command.

  • No real credentials, nothing to break.

    Agents connect with throwaway keys, so no cloud secret reaches their context or sandbox. Worst case, they reset a local container, not your staging environment or your bill.

  • Starts in 24 ms, idles at 13 MiB.

    Each emulator is a GraalVM native image in a small container, fast enough to start, test and tear down inside the edit loop. The first run also pulls the image.

  • Real engines, not mocks.

    Lambda runs in real Docker containers, RDS on real PostgreSQL and MySQL, ElastiCache on real Redis. Real wire protocols, so code an agent verifies locally behaves the same in production.

  • MIT, free forever, no auth token.

    No sign-up, no API key, no telemetry, no paid tier or feature flags. Every service is available to everyone.

Four clouds. Four emulators.

Each one is standalone, runs on its own port, and needs no cloud account. Run one, or all four side by side.

  • AWS floci · :4566

    Drop-in replacement for LocalStack.

    126 services S3, SQS, Lambda, DynamoDB, RDS +121 more

  • Azure floci-az · :4577

    No Azure account required.

    29 services Blob, Queue, Table, Functions, Key Vault +24 more

  • GCP floci-gcp · :4588

    No GCP project, no billing account.

    27 services GCS, Pub/Sub, Firestore, Datastore, Secret Manager +22 more

  • OCI floci-oci · :4599

    No Oracle Cloud account required.

    8 services Object Storage, Queue, Streaming, KMS, Vault +3 more

Install floci-cli and make your first bucket.

No account, no token. One CLI starts and manages all four emulators.

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

# Start the AWS emulator and load its endpoints
floci start && eval $(floci env)

# Create a bucket
aws s3 mb s3://my-bucket

# Upload a file
echo "hello from floci" > hello-floci.txt
aws s3 cp hello-floci.txt s3://my-bucket/

# Download it back
aws s3 cp s3://my-bucket/hello-floci.txt hello-back.txt
cat hello-back.txt
126 AWS services ready on :4566. S3 · SQS · DynamoDB · Lambda · RDS · +121 more

Something not starting? Run floci doctor.

One toolchain. All clouds.

Manage and explore every Floci emulator from a unified CLI or visual dashboard.

CLI
floci-cli

A unified command-line interface to start, stop, and inspect all Floci emulators. One install covers AWS, Azure, GCP, and OCI from a single tool.

Something not starting? floci doctor checks Docker, ports and your environment.

UI
floci-ui

A visual dashboard for all Floci cloud emulators. Browse resources, inspect data, and manage services across AWS, Azure, GCP, and OCI from one place.

floci-ui Console Home for AWS: runtime reachable, 19 active services, and a grid of services such as Compute, Storage, SQS and EventBridge with their resource counts.

On laptops, in CI and in workshops.

Anywhere a real cloud account is too slow, too risky, or too expensive.

  • One cloud per CI job.

    Run Floci as a service container. Every job gets an isolated cloud, and teardown is free.

  • Local-first development.

    Build against S3, Pub/Sub or Service Bus on your laptop, offline if you want. No shared dev account, no credentials to rotate.

  • Infrastructure-as-code dry runs.

    Apply Terraform, OpenTofu or CloudFormation against localhost first, and catch drift and bad refactors before a real account sees them.

  • Workshops and onboarding.

    Every student runs the whole stack on their own machine with zero billing risk. Start from the 101 Labs.

jobs:
  test:
    runs-on: ubuntu-latest
    services:
      floci:
        image: floci/floci
        ports: ["4566:4566"]
    env:
      AWS_ENDPOINT_URL: http://localhost:4566
      AWS_ACCESS_KEY_ID: test
      AWS_SECRET_ACCESS_KEY: test
      AWS_DEFAULT_REGION: us-east-1
    steps:
      - uses: actions/checkout@v4
      - run: pytest tests/

Where to next.

Learn by doing

Hands-on 101 Labs for AWS, Azure, GCP and OCI, each runnable against a local emulator.

Browse the labs

Coming from LocalStack?

Same SDK endpoint override, same CLI flags. 138× faster startup and 91% less memory.

See the comparison

Follow the flock

Releases, engineering notes and the monthly State of the Flock in the Chronicle.

Read the Chronicle