Gravitee API Management Self-Hosted

Open-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.

10 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

    Official Helm chart, Docker deployment or Linux packages on customer infrastructure

  2. Operated by

    Your team

    Customer manages Kubernetes or hosts, databases, search, networking, ingress, TLS, identity, secrets, monitoring, backups, scaling, upgrades and any Enterprise license.

Deployment boundaries by provider

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

Install methodOfficial Helm chart, Docker deployment or Linux packages on customer infrastructure
InfrastructureServers / containers
Gravitee APIM runs persistent management, gateway, portal, database and analytics services on customer hosts or Kubernetes.
Licensing modelOpen Source / Open Core
Gravitee APIM Community Edition is Apache-2.0 licensed. Enterprise Edition capabilities require a separate commercial license.
LicenseApache License 2.0 Community Edition; Enterprise Edition requires a commercial 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.

7 of 12 fields researched (58%) · 6 documented · 1 unresolved. Evidence coverage is not a feature score.

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

APIM documents delegating Console and Portal authentication to a corporate OAuth2/OIDC provider or LDAP, with role/group mapping. The New Developer Portal has its own SSO configuration and requires APIM 4.10+.

Self-hosted APIM 4.10 Console/Portal; not a blanket entitlement to the separate Access Management product · Source ↗ · New Portal SSO setup ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The security page’s printed certificate scope describes a marketing platform rather than APIM. That mismatch does not establish assurance for this listing; obtain a current certificate/report identifying the APIM organization, product boundary and validity dates.

Published certificate-scope mismatch; current self-hosted APIM assurance remains unresolved · Source ↗ · Reviewed 2026-11-16

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

Production guidance recommends external identity, least-privilege roles/groups and signed session cookies. Operators must replace example JWT/cookie secrets and scope cookies to the correct environment. These are configuration requirements, not a compliance attestation.

APIM 4.10 production authentication configuration · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

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

The current APIM chart source is in the API Management repository; the older standalone helm-charts repository points there. Use the versioned installation guide and a compatible chart release, database and search backend.

Self-hosted APIM 4.10 installation guidance; chart repository moves independently · Source ↗ · Deployment artifact ↗ (master (moving branch; select a chart compatible with APIM 4.10)) · APIM chart relocation ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

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

The APIM 4.10 guide gives the combined Portal/Console/REST API a baseline of 2 vCPU, 4 GB RAM and 20 GB disk. Gateways, analytics and configuration databases are additional; production HA recommends multiple nodes and traffic-dependent sizing.

Self-hosted component baselines, not the total platform footprint or guaranteed throughput · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Gravitee APIM Community Edition is Apache-2.0 licensed. Enterprise Edition capabilities require a separate commercial license.

Gravitee API Management Self-Hosted: 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

Gravitee APIM 4.10.36 and supported 4.13.4 were released November 13, 2026. Plan separately for v2 API removal in October 2027 and the 2027 Alpine-to-Debian image transition.

Gravitee APIM self-hosted 4.10 branch, with 4.13 support and migration context · Source ↗ · 4.13.4 changelog ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Show all fields (5 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry covers Gravitee APIM with both control and data planes self-hosted. Gravitee recommends its cloud option for new installations, and multi-environment self-hosted configuration requires a connection to Gravitee Cloud. The provider-specific Kubernetes guides are development and quick-start material, not production reference architectures. Gravitee APIM 4.10.36 fixes Kafka OAUTHBEARER reauthentication, subscription metadata deletion, dead-letter-queue failure handling, and health-check POST bodies. Supported 4.13.4 also fixes upgrade and Redis-cache behavior; v2 APIs are scheduled for removal in October 2027, and unqualified images move from Alpine to Debian in March 2027 before Alpine images stop in June 2027.

Community & maintenance

Gravitee maintains public releases and contributor history for its Apache-licensed API Management project. This evidence establishes continuing upstream activity, not Enterprise support or production support for a particular cloud configuration.

Category fit

Backend platforms
Provides a self-hosted API gateway, management control plane, developer portal, policy engine and API lifecycle tooling.

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
  • 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
  • Red Hat OpenShift Container PlatformCommercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
    • AWS
    • Azure
    • Google Cloud
    • Alibaba Cloud
    • IBM Cloud
    Customer-operated · Commercial Only

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.

    • Gravitee APIM self-hosted deployment on EKS, AKS or GKE ↗ · AWS, Azure, Google Cloud

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

      Gravitee's current self-hosted guide lists AWS EKS, Azure AKS and Google GKE as Kubernetes deployment methods and states that the customer manages both the control plane and data plane. Provider quick starts are development guidance rather than production architecture commitments.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory