● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement is rolling out.
KubeEra
K

KrakenD

Orchestration
Open source · NOASSERTION

KrakenD is an API Gateway written in Go.

updated 2026-07-01

What it is

KrakenD is an API Gateway written in Go. It sits in front of your backend services and handles the cross-cutting concerns you don't want scattered across every microservice: request aggregation, rate limiting, authentication (JWT validation, OAuth2), transformation, and response manipulation. It's configuration-driven — you define behavior in a JSON (or Lua/plugin-extended) config file rather than writing gateway logic by hand. No built-in service discovery or orchestration in the Kubernetes-controller sense; despite the category label here, it's better understood as an API gateway / edge layer, typically deployed as a stateless pod that fronts your cluster's services.

Official description: not publicly available from the data provided. Take the above as a practitioner's summary based on the project's known behavior, not a vendor claim.

Who builds it and why

KrakenD is developed primarily by a commercial company of the same name (KrakenD, formerly known under the Devops-focused predecessor "Kraken.io" branding in some contexts), which sells a paid Enterprise Edition on top of the open-source Community Edition. The open-source version is the actual gateway engine; the company monetizes via enterprise features (advanced plugins, support SLAs, multi-cluster management, security modules). This is a fairly standard open-core model — the CE is not a stripped-down demo, it's a functioning gateway used in production by real companies, but the roadmap and feature gating are controlled by a single vendor, not a foundation. Founded date: not publicly available. CNCF maturity: not publicly available — KrakenD is not a CNCF project.

Production readiness signal

  • 6,784 GitHub stars, 52 contributors — a real, established project, but contributor count is modest for something this widely deployed, suggesting most core development comes from the company's own engineers rather than a broad external community.
  • Last commit 2026-06-20 — actively maintained, no signs of abandonment.
  • Latest release v2.13.0 — mature version numbering, indicates a long iteration history and a project past its early-instability phase.
  • License: NOASSERTION. This is a red flag worth acting on, not ignoring — it means GitHub's license detector couldn't confidently classify the repo's license (often because of a non-standard LICENSE file, dual-licensing setup, or missing/altered license text). Before you deploy this anywhere near production, pull the actual LICENSE file and confirm terms yourself, especially if you're evaluating CE vs. Enterprise boundaries. Don't assume "open source on GitHub" means unrestricted use.

Who should use this

  • Teams that need a fast, config-first API gateway and don't want to run something heavier like Kong or a service mesh just to get rate limiting, JWT validation, and endpoint aggregation.
  • Go shops that want a gateway they can extend via Go plugins rather than Lua scripting in other tools.
  • Teams fronting many small backend services who want request aggregation (combining multiple backend calls into one client-facing response) without writing a BFF layer by hand.

Who should NOT use this

  • Anyone needing built-in service mesh capabilities (mTLS between services, traffic shifting, sidecar-based observability) — KrakenD is an edge gateway, not a mesh. Use Istio or Linkerd for that.
  • Teams that need dynamic, UI-driven configuration management out of the box — CE is file/config-based; if you want a control plane with a GUI and RBAC, that's Enterprise-only or belongs to a different product like Kong Konnect or Apigee.
  • Organizations that require clear, court-tested OSS licensing for compliance reasons — the NOASSERTION status means you need legal review before adoption, not after.
  • Teams already standardized on Envoy-based gateways (e.g., Contour, Gloo) where adding a second gateway technology increases operational surface for no clear gain.

Alternatives

  • Kong — more mature ecosystem, plugin marketplace, but heavier and Lua/OpenResty-based.
  • Envoy Gateway / Contour — if you're already running Envoy in your mesh, staying on Envoy-based ingress avoids running two different proxy technologies.
  • Traefik — simpler out-of-the-box Kubernetes integration via CRDs, weaker on request aggregation compared to KrakenD.

Pricing

Not fully open source in the "single license, no gating" sense. Core gateway is free and open (Community Edition), but the vendor sells a separate Enterprise Edition with additional features and support. Confirm exact CE feature boundaries and license terms directly from the repo given the NOASSERTION status — don't rely on marketing pages alone.

Frequently asked

What is KrakenD?+
KrakenD is an API Gateway written in Go. It sits in front of your backend services and handles the cross-cutting concerns you don't want scattered across every microservice: request aggregation, rate limiting, authentication (JWT validation, OAuth2), transformation, and response manipulation.
Who builds KrakenD?+
KrakenD is developed primarily by a commercial company of the same name (KrakenD, formerly known under the Devops-focused predecessor "Kraken.io" branding in some contexts), which sells a paid Enterprise Edition on top of the open-source Community Edition.
Is KrakenD production ready?+
6,784 GitHub stars, 52 contributors — a real, established project, but contributor count is modest for something this widely deployed, suggesting most core development comes from the company's own engineers rather than a broad external community. Last commit 2026-06-20 — actively maintained, no signs of abandonment.
Who should use KrakenD?+
Teams that need a fast, config-first API gateway and don't want to run something heavier like Kong or a service mesh just to get rate limiting, JWT validation, and endpoint aggregation. Go shops that want a gateway they can extend via Go plugins rather than Lua scripting in other tools.
Who should not use KrakenD?+
Anyone needing built-in service mesh capabilities (mTLS between services, traffic shifting, sidecar-based observability) — KrakenD is an edge gateway, not a mesh. Use Istio or Linkerd for that.
What are the alternatives to KrakenD?+
Kong — more mature ecosystem, plugin marketplace, but heavier and Lua/OpenResty-based. Envoy Gateway / Contour — if you're already running Envoy in your mesh, staying on Envoy-based ingress avoids running two different proxy technologies.
How much does KrakenD cost?+
Not fully open source in the "single license, no gating" sense. Core gateway is free and open (Community Edition), but the vendor sells a separate Enterprise Edition with additional features and support.