Neosync vs LocalStack
Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.
Entry price
Free and open source
Open sourceFrom $39 per licence/month (Base, billed annually; $45 monthly)
Free tierWhat drives the bill
The metric that actually scales your invoice.
The MIT-licensed code remains free to self-host. The paid cloud service no longer exists — neosync.dev is offline.
Plans are Hobby (free, non-commercial), Base $39 and Ultimate $89 per licence/month billed annually, then Enterprise. Commercial use needs a paid licence, and the higher tiers are what unlock advanced IAM enforcement and the wider service coverage.
Free tier
Everything, self-hosted
Hobby tier is free but explicitly non-commercial, and LocalStack has said the Community emulator will no longer receive product updates.
Open source
MIT
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Emerging
Nucleus Cloud (acquired by Grow Therapy) · since 2023
Category standard
LocalStack · since 2017
Strengths
- Open source and self-hostable, so sensitive data never leaves your infrastructure.
- Preserves referential integrity across tables.
- The last release is feature-complete for common Postgres and MySQL anonymisation work.
- Integration tests against AWS services run offline in seconds at no cloud cost.
- Removes the shared-sandbox-account contention that plagues cloud teams.
- Works with Terraform and CDK, so infrastructure code is testable.
Limitations
- Archived and unmaintained since August 2025 — no security patches, no new connectors, no support.
- The hosted cloud has been shut down, so self-hosting is the only option.
- Fewer database connectors than the incumbents.
- No longer open source: the Community edition is end-of-life, the repo is archived, and running it now requires an account and auth token.
- Using it in CI counts as commercial use, so the free tier does not cover the case most teams want it for.
- Emulation is not identical to AWS; some behaviours and IAM semantics differ.
Best for
Realistically, nobody starting fresh. Existing self-hosted users can keep running it, but plan a migration to Tonic or a maintained alternative.
AWS-native teams whose tests currently depend on a shared cloud account, and who are willing to pay for a licence now that the free community route has closed.
All of these integrate with: GitHub Actions.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.