APIs · head to head
Kong Gateway vs Valkey

Kong Gateway
APIs
Open-source and cloud API gateway for managing microservices traffic
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Kong Gateway the free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.; Valkey younger project, so its track record is short even though the codebase is not
- They diverge on capability: Kong Gateway covers API request routing, Valkey covers Redis-compatible.
- Prices and features above were last checked on 29 August 2026.
Where they differ
Only the attributes on which Kong Gateway and Valkey actually diverge.
| Attribute | Kong Gateway | Valkey |
|---|---|---|
| Pricing model | freemium | Open source, no licence fee; managed cloud billed separately |
| Platforms | web, linux, api | Linux, macOS, Docker, Self-hosted |
| Category | APIs | Databases |
| Founded | 2017 | Unknown |
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).
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 Kong Gateway
- API request routing
- Plugin ecosystem
- Developer portals
- AI Gateway
- Analytics and observability
- SSO and audit logs
Only in Valkey
- Redis-compatible
- BSD licensed
- Rich data structures
- Replication and persistence
What people use each for
The jobs each tool is most often brought in to do.
Kong Gateway
- Routing and securing traffic across microservicesnot Valkey
- Publishing internal or external developer portalsnot Valkey
- Managing rate limits and authentication at the API edgenot Valkey
- Gateway-level routing to multiple LLM providersnot Valkey
Valkey
- Continuing on a permissively licensed in-memory store after the Redis licence changenot Kong Gateway
- Caching and session storage where a foundation-governed project is a procurement requirementnot Kong Gateway
- Migrating from Redis without rewriting application codenot Kong Gateway
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Kong Gateway
- The free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.
- Plus tier caps API requests at 1M/month before incurring per-million overage charges.
- Enterprise pricing is custom and not published, making budgeting harder without sales contact.
- Configuration and plugin management can require significant operational expertise to run at scale.
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
Pricing, plan by plan
Kong Gateway
Free- Free TrialFree
- 30-day enterprise functionality trial
- Unlimited gateways
- 30-day analytics retention
- Plus$undefined/month
- Up to 5 serverless, 2 hybrid, 2 dedicated cloud gateways
- 1M API requests/month included
- Up to 2 developer portals
- Enterprise$undefined/month
- Unlimited hybrid and dedicated cloud gateways
- Unlimited developer portals
- SSO and audit logs
Valkey
Free- ValkeyFree
- Full functionality
- Self-hosted
- No usage limits
Which should you pick?
Choose Kong Gateway if
- You need api request routing.
- You want to start without paying.
- You work on web, linux, api.
- You also want plugin ecosystem.
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.
Questions people ask
- Is Kong Gateway or Valkey better?
- Neither clearly leads. Kong Gateway starts at Free and Valkey at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Kong Gateway or Valkey?
- Kong Gateway starts at Free and Valkey at Free.
- Does Kong Gateway or Valkey run on more platforms?
- Kong Gateway runs on web, linux, api. Valkey runs on Linux, macOS, Docker, Self-hosted.
- Can I use Kong Gateway for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Kong Gateway best used for?
- Kong Gateway is most often used for routing and securing traffic across microservices, publishing internal or external developer portals, managing rate limits and authentication at the api edge, gateway-level routing to multiple llm providers. Of those, routing and securing traffic across microservices and publishing internal or external developer portals are not what Valkey is typically brought in for.
- What can Kong Gateway do that Valkey cannot?
- Kong Gateway covers API request routing, Plugin ecosystem, Developer portals, AI Gateway. Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence.
Answered from the vendors’ own pages
Kong Gateway: Is Kong Gateway free?
Kong's core gateway is open source and free to self-host. Kong Konnect, the managed cloud platform, offers a 30-day free trial before moving to paid Plus or custom Enterprise pricing.
SourceValkey: Is Valkey free?
Yes, BSD-licensed open source under the Linux Foundation.
Kong Gateway: How is usage metered on the Plus plan?
The Plus plan includes 1M API requests per month, with additional usage billed at $200 per extra 1 million requests up to a 10M/month cap, plus per-gateway and per-LLM-model charges.
SourceValkey: 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.
Kong Gateway: What support is included?
Plus includes email support with a 2-business-day SLA, while Enterprise adds dedicated success managers and professional services.
SourceValkey: 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.
Related pages
More on Kong Gateway
Other head to heads
- Kong Gateway vs Tyk
- Kong Gateway vs Moesif
- Kong Gateway vs Treblle
- Kong Gateway vs Convoy
- Kong Gateway vs Janus Gateway
- Kong Gateway vs Spring Cloud Gateway
- Kong Gateway vs Gravitee
- Kong Gateway vs Strapi
- Kong Gateway vs WSO2 API Manager
- Kong Gateway vs AWS API Gateway
- Kong Gateway vs GraphQL Apollo
- Kong Gateway vs Appwrite
- Kong Gateway vs Payload CMS
- Kong Gateway vs Portkey
- Kong Gateway vs Prisma
- Kong Gateway vs RapidAPI
- Kong Gateway vs REST Client VSCode
- Kong Gateway vs Rutter
- Kong Gateway vs Dragonfly
- Kong Gateway vs Memcached
- Kong Gateway vs MariaDB
- Kong Gateway vs Aiven
- Kong Gateway vs Redpanda
- Kong Gateway vs Timeplus
- Kong Gateway vs PostgreSQL
- Kong Gateway vs Apache Kafka
- Kong Gateway vs RabbitMQ
- Kong Gateway vs Meilisearch
- Kong Gateway vs NATS
- Kong Gateway vs DataGrip
- Kong Gateway vs Estuary
- Kong Gateway vs Apache Airflow
- Kong Gateway vs Apache Pinot
- Kong Gateway vs Apache Pulsar
- Kong Gateway vs Cassandra
- Kong Gateway vs CouchDB
- Valkey vs Tyk
- Valkey vs Moesif
- Valkey vs Treblle
- Valkey vs Convoy
- Valkey vs Janus Gateway
- Valkey vs Spring Cloud Gateway
- Valkey vs Gravitee
- Valkey vs Strapi
- Valkey vs WSO2 API Manager
- Valkey vs AWS API Gateway
- Valkey vs GraphQL Apollo
- Valkey vs Appwrite
- Valkey vs Payload CMS
- Valkey vs Portkey
- Valkey vs Prisma
- Valkey vs RapidAPI
- Valkey vs REST Client VSCode
- Valkey vs Rutter
- Valkey vs Dragonfly
- Valkey vs Memcached
- Valkey vs MariaDB
- Valkey vs Aiven
- Valkey vs Redpanda
- Valkey vs Timeplus
- Valkey vs PostgreSQL
- Valkey vs Apache Kafka
- Valkey vs RabbitMQ
- Valkey vs Meilisearch
- Valkey vs NATS
- Valkey vs DataGrip
- Valkey vs Estuary
- Valkey vs Apache Airflow
- Valkey vs Apache Pinot
- Valkey vs Apache Pulsar
- Valkey vs Cassandra
- Valkey vs CouchDB

