Softwr

Databases · head to head

Valkey vs Xata

Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

From
Free
Rated
-
Full reviewWebsite
Xata logo

Xata

Databases

Apache 2.0 platform for running many Postgres instances on Kubernetes, with copy-on-write branching and scale-to-zero.

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; Xata self-hosting means operating Kubernetes and CloudNativePG, so the Apache 2.0 licence removes the vendor bill but replaces it with a platform team, and a database platform is not something a part-time operator maintains safely.
  • They diverge on capability: Valkey covers Redis-compatible, Xata covers Copy-on-write branching.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Valkey and Xata actually diverge.

Attributes where Valkey and Xata differ
AttributeValkeyXata
Pricing modelOpen source, no licence fee; managed cloud billed separatelyusage-based
PlatformsLinux, macOS, Docker, Self-hostedWeb

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 Xata

  • Copy-on-write branching
  • Scale-to-zero compute
  • Compute autoscaling and bin-packing
  • High availability with failover
  • Point-in-time recovery
  • Serverless driver
  • pgroll migrations
  • pgstream replication

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 Xata
  • Caching and session storage where a foundation-governed project is a procurement requirementnot Xata
  • Migrating from Redis without rewriting application codenot Xata

Xata

  • Giving every pull request or coding agent its own branch of the production database, with real data volumes rather than a seeded fixturenot Valkey
  • Running managed-Postgres economics in your own cloud account where data residency or compliance rules out a third-party control planenot Valkey
  • Consolidating many small, mostly idle Postgres databases onto shared infrastructure where scale-to-zero and bin-packing recover the idle costnot Valkey
  • Testing a destructive migration against a copy of production without waiting for a full restore or paying for a duplicate of the storagenot 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

Xata

  • Self-hosting means operating Kubernetes and CloudNativePG, so the Apache 2.0 licence removes the vendor bill but replaces it with a platform team, and a database platform is not something a part-time operator maintains safely.
  • Copy-on-write branches are cheap to create but diverge as they are written to, so a long-lived branch carrying a heavy backfill quietly accumulates real storage and the cost arrives later than the decision that caused it.
  • Scale-to-zero means the first connection after an idle period pays a cold start, which is invisible in a busy production database and very visible in a demo, a staging environment or a cron job that runs once an hour.
  • The Xata sold before 2025 was a different product, a proprietary API and SDK layered over Postgres, so tutorials, blog posts and SDK examples from that era describe something that no longer exists and existing users had to migrate.
  • As a managed service it competes with RDS, Aurora and Cloud SQL, and it is a much smaller company, so procurement, certification coverage and the depth of the support bench behind a 3am corruption incident are all weaker than the incumbent even though the underlying Postgres is the same.

Pricing, plan by plan

Valkey

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

Xata

Free
  • Free TrialFree
    • 14 days free
    • No credit card required
  • Usage-Based$1/per 1000 branches
    • 1,000 branches for $1
    • Scale-to-zero compute model
    • Branches hibernate when idle

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 Xata if

  • You need copy-on-write branching.
  • You want to start without paying.
  • You also want scale-to-zero compute.
Xata review

Questions people ask

Is Valkey or Xata better?
Neither clearly leads. Valkey starts at Free and Xata at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Valkey or Xata?
Valkey starts at Free and Xata at Free.
Does Valkey or Xata run on more platforms?
Valkey runs on Linux, macOS, Docker, Self-hosted. Xata runs on Web.
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 Xata is typically brought in for.
What can Valkey do that Xata cannot?
Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence. Xata covers Copy-on-write branching, Scale-to-zero compute, Compute autoscaling and bin-packing, High availability with failover.

Answered from the vendors’ own pages

Valkey: Is Valkey free?

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

Xata: Is it real Postgres or a compatible reimplementation?

Real Postgres. It runs upstream Postgres instances on Kubernetes via CloudNativePG, so extensions, the wire protocol and version upgrades behave as they do anywhere else.

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.

Xata: Can I self-host the whole thing?

Yes. The platform is Apache 2.0 and designed for self-hosting a large number of Postgres instances on your own Kubernetes. Xata Cloud is the same platform run as a service.

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.

Xata: Does branching copy my data?

No. Branches are copy-on-write at the storage layer, so creating one is near-instant regardless of database size and storage is only consumed as the branch diverges from its parent.

Xata: Is this the same Xata I used a couple of years ago?

No. The earlier product was a proprietary database API with its own SDK and search layer. The current product is a Postgres platform, and material written for the old one does not apply.

Xata: What happens to a branch when the parent changes?

A branch is a point-in-time fork. Later changes on the parent are not propagated, so long-lived branches drift and need to be recreated rather than refreshed if you want current data.

Share

Related pages

More on Valkey

More on Xata

Keep looking

Other head to heads