Tyk Self-Managed

Commercial self-managed API management platform with documented AWS, Azure and Google Cloud deployments.

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Docker, Helm, Linux packages or Ansible on customer cloud infrastructure

  2. Operated by

    Your team

    Customer manages hosts or Kubernetes, data stores, networking, TLS, identities, secrets, monitoring, backups, scaling, upgrades and the Tyk license.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Tyk Self-Managed on AWS ↗ · Source checked 2026-11-16

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Tyk Self-Managed on Microsoft Azure ↗ · Source checked 2026-11-16

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Tyk Self-Managed on Google Cloud ↗ · Source checked 2026-11-16

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodDocker, Helm, Linux packages or Ansible on customer cloud infrastructure
InfrastructureServers / containers
Tyk Self-Managed runs persistent gateway, management, analytics, portal and database services on customer virtual machines or Kubernetes.
Licensing modelCommercial Only
The selected full Tyk Self-Managed platform requires a commercial license. Tyk Gateway and Pump are separately available as open-source components, but they do not constitute the complete listed platform.
LicenseCommercial Tyk Self-Managed license required for the full platform; Gateway and Pump are available without that license.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

8 of 12 fields researched (67%) · 8 documented · 0 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery

The vendor AWS offer explicitly covers Cloud, Hybrid and Self-Managed. Its delivery classification is a SaaS contract and its public dimensions price Tyk Cloud; request terms that specifically license the self-managed deployment rather than treating it as an application AMI.

Vendor-published AWS offer; procurement and application hosting are distinct · Source ↗ · Offer prodview-pboluroscnqro ↗ — Tyk Technologies Ltd; SaaS contract listing covering multiple deployment modes; self-managed terms require confirmation · Reviewed 2026-11-16

Edition-dependent · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

Tyk documents Dashboard SAML login through its internal Identity Broker with Okta, and an OIDC integration with AWS Cognito. Configure the identity profile and user mapping for the licensed Dashboard; API-consumer authentication is a separate concern.

Commercial self-managed Dashboard with internal TIB · Source ↗ · Dashboard OIDC with Cognito ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The self-managed guide documents database-backed Dashboard audit-log storage from v5.7 onward. Operators must configure it, size the database and set retention/archive policies; example log sizes are workload assumptions, not a default retention guarantee or an attestation.

Dashboard 5.7+ audit-log configuration and storage responsibilities · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Air-gapped operation
DocumentedEvidence and scope for Air-gapped operation

Tyk documents mirroring all chart images, packaging the Helm chart and installing from private registries; Linux deployments can use local package mirrors. Include optional-component images and arrange the correct commercial licenses and compatible versions.

Documented self-managed offline installation workflow; selected integrations and license terms still require deployment-specific review · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

Tyk publishes the tyk-stack Helm chart and a trial-ready installation wrapper. Use the current tyk-charts repository; the former tyk-helm-chart repository is archived and deprecated. Select compatible chart/component versions, configure the required Dashboard license and production databases, and review trial defaults before production.

Full self-managed platform; not the standalone open-source gateway · Source ↗ · Deployment artifact ↗ (main (moving branch; select compatible chart release)) · Archived chart repository and replacement notice ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The current Kubernetes tutorial requires at least 4 GB RAM available to the cluster, but explicitly deploys a trial-ready configuration. Production sizing must include Gateway traffic, Redis, PostgreSQL and optional components; 4 GB is not a production capacity guarantee.

Self-managed Kubernetes tutorial prerequisites, not a universal production minimum · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The selected full Tyk Self-Managed platform requires a commercial license. Tyk Gateway and Pump are separately available as open-source components, but they do not constitute the complete listed platform.

Tyk Self-Managed: software license terms; infrastructure and operating costs are separate · Source ↗ · Edition and license conditions ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The reviewed vendor policy lists 5.13 as its current LTS line. Gateway/Dashboard LTS receives 12 months of full support with eight-week patches, then 12 months of critical maintenance. Other components and non-LTS releases have separate compatibility and lifecycle rules.

Published Gateway/Dashboard LTS policy as reviewed; not a single version or support guarantee for the entire platform · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Show all fields (4 not researched)
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry covers the full Tyk Self-Managed platform, not Tyk Cloud or the standalone OSS Gateway. The Dashboard and other full-platform components require a commercial license, and Kubernetes installation requires a multi-node license. Provider tutorials are starter deployments rather than production sizing or high-availability guarantees.

Category fit

Backend platforms
Provides a self-managed API gateway, management dashboard, analytics, developer portal and lifecycle controls for application APIs.

Compare within Backend platforms

  • Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
    • Northflank
    Customer-operated · Open Source / Open Core
  • Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Heroku
    Customer-operated · Open Source / Open Core

Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Tyk Self-Managed on AWS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

      Tyk documents creating an Amazon EC2 instance in the customer's AWS account and deploying the licensed Tyk Self-Managed platform with Docker.

    • Tyk Self-Managed on Microsoft Azure ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

      Tyk documents creating an Azure virtual machine and installing the Tyk Self-Managed stack with Docker in the customer's Azure environment.

    • Tyk Self-Managed on Google Cloud ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

      Tyk documents deploying its licensed Self-Managed platform on customer Google Cloud infrastructure.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory