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

Tyk

Orchestration
Open source · NOASSERTION

Tyk is an API gateway and API management platform written in Go.

updated 2026-07-01

What it is

Tyk is an API gateway and API management platform written in Go. It handles the usual gateway workload — request routing, rate limiting, authentication (API keys, OAuth2, JWT, mTLS), quota management, and analytics — sitting in front of your backend services or microservices mesh. It ships as a self-hosted open-source gateway (Tyk Gateway) with an optional dashboard, developer portal, and multi-cloud/multi-data-center management layer (Tyk Pump for analytics pipelines) that are part of the commercial tier. Category-wise it's Orchestration & Management: you're not deploying this to orchestrate containers, you're deploying it to control and observe API traffic at the edge or between services.

Who builds it and why

Tyk is built by Tyk Technologies, a commercial company that maintains the open-source gateway as a lead-gen and adoption funnel for its paid Cloud and Enterprise tiers (dashboard, developer portal, multi-org support, SLA-backed support). This is a classic open-core model: the gateway itself is fully functional standalone, but production teams running multi-team or multi-tenant API programs will eventually hit walls that push them toward the commercial layer (RBAC, SSO, GraphQL federation UI, dedicated support). Founding date isn't publicly available in the data set, but the project has been actively maintained for years and has a stable commercial entity behind it — this isn't a side project.

Production readiness signal

136 contributors and 10,755 GitHub stars indicate real adoption and an active contributor base beyond the core company. Last commit dated 2026-07-01 shows the repo is actively maintained, not abandoned. That said, two things warrant scrutiny before you deploy:

  • License is NOASSERTION. GitHub's license detector couldn't confidently identify the license from the repo. This isn't necessarily a red flag on its own (custom LICENSE files sometimes trip the detector), but you need to manually verify licensing terms before adopting this in a commercial product — don't assume MIT or Apache 2.0.
  • Latest release is v5.11.1-alpha2. An alpha tag on what looks like a patch release (5.11.1) is unusual — it suggests either an in-progress feature backport or unstable tooling around release tagging. Check the changelog and pin to a known-stable prior release for production, don't grab latest by default.

CNCF maturity is not publicly available — Tyk is not a CNCF project, so don't expect CNCF governance, security audits, or roadmap transparency that come with that ecosystem.

Who should use this

Teams that need a self-hosted, Go-based API gateway with strong out-of-box auth/rate-limiting and don't want to hand-roll Envoy/Kong configs. Good fit if you're managing external-facing APIs for partners or customers and want a developer portal without building one. Also reasonable for teams already comfortable running and patching their own infrastructure who want to avoid vendor lock-in to a fully managed API gateway SaaS.

Who should NOT use this

If you're already deep in a service mesh (Istio, Linkerd) handling east-west traffic, adding Tyk on top for the same job is redundant complexity — use the mesh's native gateway or Envoy directly. If you need CNCF-graduated governance guarantees for compliance reasons, look elsewhere since Tyk isn't a CNCF project. If your team can't tolerate ambiguity around licensing terms (NOASSERTION), get legal sign-off first or pick a project with an unambiguous SPDX license (Kong OSS, for example). And if you want a fully managed, zero-ops gateway, Tyk's commercial cloud exists but you're then paying for what AWS API Gateway or Apigee already do turnkey.

Alternatives

  • Kong — larger community, Lua/Nginx-based, similarly open-core, more plugin ecosystem maturity.
  • Envoy / Emissary-Ingress — CNCF-graduated, better fit if you're already in a Kubernetes-native, service-mesh-adjacent stack.
  • AWS API Gateway / Apigee — fully managed, less operational overhead, but vendor lock-in and less control over gateway internals.

Pricing

Not fully open source in the commercial sense — the gateway is open source and free to self-host, but the dashboard, developer portal, multi-org management, and enterprise support require a paid Tyk Cloud or Tyk Enterprise license. Exact pricing not publicly available; expect a sales-quote model typical of open-core API vendors.

Frequently asked

What is Tyk?+
Tyk is an API gateway and API management platform written in Go. It handles the usual gateway workload — request routing, rate limiting, authentication (API keys, OAuth2, JWT, mTLS), quota management, and analytics — sitting in front of your backend services or microservices mesh.
Who builds Tyk?+
Tyk is built by Tyk Technologies, a commercial company that maintains the open-source gateway as a lead-gen and adoption funnel for its paid Cloud and Enterprise tiers (dashboard, developer portal, multi-org support, SLA-backed support).
Is Tyk production ready?+
136 contributors and 10,755 GitHub stars indicate real adoption and an active contributor base beyond the core company. Last commit dated 2026-07-01 shows the repo is actively maintained, not abandoned. That said, two things warrant scrutiny before you deploy: License is NOASSERTION.
Who should use Tyk?+
Teams that need a self-hosted, Go-based API gateway with strong out-of-box auth/rate-limiting and don't want to hand-roll Envoy/Kong configs. Good fit if you're managing external-facing APIs for partners or customers and want a developer portal without building one.
Who should not use Tyk?+
If you're already deep in a service mesh (Istio, Linkerd) handling east-west traffic, adding Tyk on top for the same job is redundant complexity — use the mesh's native gateway or Envoy directly. If you need CNCF-graduated governance guarantees for compliance reasons, look elsewhere since Tyk isn't a CNCF project.
What are the alternatives to Tyk?+
Kong — larger community, Lua/Nginx-based, similarly open-core, more plugin ecosystem maturity. Envoy / Emissary-Ingress — CNCF-graduated, better fit if you're already in a Kubernetes-native, service-mesh-adjacent stack.
How much does Tyk cost?+
Not fully open source in the commercial sense — the gateway is open source and free to self-host, but the dashboard, developer portal, multi-org management, and enterprise support require a paid Tyk Cloud or Tyk Enterprise license.