April 1, 2026 · 4 min read

LocalStack Went Paid — Meet MiniStack, the Free Replacement

LocalStack just moved core services behind a paywall. If you relied on the Community edition for local dev and CI/CD, your workflow is about to break.

Enter MiniStack — a free, MIT-licensed, open-source drop-in replacement that gives you 33 AWS services on a single port. No account. No license key. No telemetry.

    The TL;DR: docker run -p 4566:4566 nahuelnucera/ministack — that's it. Same endpoint, same AWS CLI, zero config changes.
  

What Happened to LocalStack?

LocalStack was the go-to for local AWS emulation. But they've steadily moved more services behind their Pro plan — S3, SQS, DynamoDB, Lambda, IAM. The "free" tier is now basically a demo.

For indie devs and small teams, that's a problem. Local development shouldn't require a $30/month subscription per seat.

What MiniStack Gives You

MiniStack covers the services you actually use:

Storage: S3 (buckets, versioning, encryption, lifecycle, CORS)
Compute: Lambda (real Python execution, warm workers, SQS event sources)
Databases: DynamoDB (full CRUD, queries, transactions, GSI)
Messaging: SQS (FIFO, DLQ), SNS (fanout to SQS), Kinesis
Real Infrastructure: RDS runs actual Postgres/MySQL containers. ElastiCache runs real Redis. ECS starts real Docker containers.
Security: IAM, STS, Cognito, Secrets Manager, WAF v2
Networking: Route53, API Gateway v1 & v2, ALB/ELBv2, EC2, VPCs
Other: Step Functions, EventBridge, CloudWatch Logs & Metrics, SES, Glue, Athena (via DuckDB), Firehose, SSM, ACM, EFS, EBS, EMR

That's 33 services. Many of them (RDS, ElastiCache, ECS, EMR, EBS, EFS, ALB, WAF) were Pro-only on LocalStack. MiniStack gives them to you free.

The Numbers

~2 second startup time
~30 MB RAM at idle
150 MB Docker image
763 tests passing
MIT licensed

For comparison, LocalStack's image is ~1GB and uses significantly more memory. MiniStack is a fraction of the footprint.

Is It Actually a Drop-In Replacement?

Yes. If your code uses the standard AWS SDK or CLI with --endpoint-url=http://localhost:4566, nothing changes. The API surface is the same.

# S3 — works exactly like AWS
aws --endpoint-url=http://localhost:4566 s3 mb s3://my-bucket

# RDS — spins up real Postgres
aws --endpoint-url=http://localhost:4566 rds create-db-instance \
  --db-instance-identifier mydb --engine postgres \
  --master-username admin --master-user-password secret

# ElastiCache — spins up real Redis
aws --endpoint-url=http://localhost:4566 elasticache \
  create-cache-cluster --cache-cluster-id my-redis --engine redis

RDS gives you a real Postgres container on localhost:15432. ElastiCache gives you real Redis on localhost:16379. These aren't mocks — they're actual running databases.

Who Should Switch?

Indie devs who don't want to pay for LocalStack Pro
CI/CD pipelines that need free, license-key-free AWS emulation
Small teams who were on LocalStack Community and just got paywalled
Anyone who values zero telemetry and open-source transparency

    MiniStack isn't trying to replace LocalStack Enterprise. It's replacing what LocalStack Community used to be — free, open, and good enough for most workflows.
  

The Bottom Line

The open-source tooling space just got a win. When commercial projects move features behind paywalls, the community fills the gap. MiniStack proves that local AWS emulation doesn't need to cost anything.

If you're building on AWS and developing locally, there's no reason not to try it. One Docker command. Zero commitment.

Check out ministack.org or grab it on GitHub.

← Back to Blog