Softwr

Databases · head to head

Valkey vs NATS

Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

From
Free
Rated
-
Full reviewWebsite
NATS logo

NATS

Databases

High-performance messaging system for cloud-native applications

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Valkey younger project, so its track record is short even though the codebase is not; NATS core NATS has no persistence at all, so messages are lost if no subscriber is listening
  • They diverge on capability: Valkey covers Redis-compatible, NATS covers Very low latency.

Where they differ

Only the attributes on which Valkey and NATS actually diverge.

Attributes where Valkey and NATS differ
AttributeValkeyNATS
Pricing modelOpen source, no licence fee; managed cloud billed separatelyOpen source, no licence fee
PlatformsLinux, macOS, Docker, Self-hostedLinux, macOS, Windows, Docker, Kubernetes

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Valkey

  • Redis-compatible
  • BSD licensed
  • Rich data structures
  • Replication and persistence

Only in NATS

  • Very low latency
  • JetStream
  • Single binary
  • Request-reply

What people use each for

The jobs each tool is most often brought in to do.

Valkey

  • Continuing on a permissively licensed in-memory store after the Redis licence changenot NATS
  • Caching and session storage where a foundation-governed project is a procurement requirementnot NATS
  • Migrating from Redis without rewriting application codenot NATS

NATS

  • Service-to-service messaging where latency is the binding constraintnot Valkey
  • Edge and IoT messaging where a lightweight broker mattersnot Valkey
  • Replacing a heavier broker when the workload does not need its guaranteesnot Valkey

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Valkey

  • Younger project, so its track record is short even though the codebase is not
  • Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
  • Ecosystem tooling and documentation still frequently assume Redis, leaving translation work

NATS

  • Core NATS has no persistence at all, so messages are lost if no subscriber is listening
  • JetStream adds the durability but also the operational complexity NATS is chosen to avoid
  • A much smaller ecosystem than Kafka or RabbitMQ, with fewer connectors and integrations
  • Fewer people know it, so hiring and existing organisational knowledge favour the alternatives

Pricing, plan by plan

Valkey

Free
  • ValkeyFree
    • Full functionality
    • Self-hosted
    • No usage limits

NATS

Free
  • NATSFree
    • Full functionality
    • No usage limits
    • Community support

Which should you pick?

Choose Valkey if

  • You need redis-compatible.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Self-hosted.
  • You also want bsd licensed.
Valkey review

Choose NATS if

  • You need very low latency.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker, Kubernetes.
  • You also want jetstream.
NATS review

Questions people ask

Is Valkey or NATS better?
Neither clearly leads. Valkey starts at Free and NATS at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Valkey or NATS?
Valkey starts at Free and NATS at Free.
Does Valkey or NATS run on more platforms?
Valkey runs on Linux, macOS, Docker, Self-hosted. NATS runs on Linux, macOS, Windows, Docker, Kubernetes.
Can I use Valkey for free?
Both have a free tier, so you can try either at no cost before committing.
What is Valkey best used for?
Valkey is most often used for continuing on a permissively licensed in-memory store after the redis licence change, caching and session storage where a foundation-governed project is a procurement requirement, migrating from redis without rewriting application code. Of those, continuing on a permissively licensed in-memory store after the redis licence change and caching and session storage where a foundation-governed project is a procurement requirement are not what NATS is typically brought in for.
What can Valkey do that NATS cannot?
Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence. NATS covers Very low latency, JetStream, Single binary, Request-reply.

Answered from the vendors’ own pages

Valkey: Is Valkey free?

Yes, BSD-licensed open source under the Linux Foundation.

NATS: Is NATS free?

Yes, open source and CNCF-graduated. Synadia sells a managed service.

Valkey: Why does Valkey exist?

Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.

NATS: Does NATS persist messages?

Core NATS does not — it is fire-and-forget. JetStream adds persistence, streaming and replay when you need them.

Valkey: Can I switch from Redis to Valkey?

At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.

NATS: NATS or Kafka?

NATS is far lighter and lower latency, and much simpler to run. Kafka is the answer when you need a durable replayable log and a large connector ecosystem.

Share

Related pages

More on Valkey

More on NATS

Keep looking

Other head to heads