Which Companies Offer Apigee Support?

AceMQ offers Apigee support: 24/7 cover with a 15-minute emergency response, for the proxies, policies, backends and infrastructure around Apigee. The other sources are Google, for Apigee X, hybrid and Edge under your Google Cloud or Apigee contract, and partners, compared below.

For on-premises installations in particular, each release is supported for a fixed window, and running an older release means running without patches.

What Google supports, and for how long

According to the Apigee release process, each major and minor version of Apigee Edge for Private Cloud receives full support for approximately 18 months from its initial release. During that window Apigee provides security patches, bug fixes and hotfixes. At the end-of-life date it stops providing new bug fixes, security updates, hotfixes or patches for that line; the software keeps running, but nobody maintains it. Version 4.53.00 reached end of life on 11 April 2026, the supported software page states that 4.53.00 and earlier are no longer supported, and 4.53.01, first released on 26 August 2025, is the active line. The release notes and the supported software list name the operating system, JDK and TLS requirements, so a patch or upgrade installation can also mean an operating system or Java change. Read both before you install.

Apigee hybrid follows its own schedule on the supported platforms page. At the time of writing hybrid 1.17 was released on 14 September 2026 and hybrid 1.14 has a scheduled end of life of 19 December 2026. Hybrid 1.13 and earlier are end of life and no longer supported except for customers with explicit exceptions; monthly patches for them have stopped.

Edge for Private Cloud, hybrid and Apigee X

The three deployment models put the support boundary in different places. In Apigee X, Google runs the runtime on Google Cloud. In Apigee hybrid, Google runs the management plane and your team runs the runtime plane in your own Kubernetes cluster, so cluster upgrades, certificates, ingress and capacity are yours. In Edge for Private Cloud, often called OPDK, everything runs in your data centre: Routers, Message Processors, the Management Server, and third-party services including Apache Cassandra, Apache ZooKeeper, OpenLDAP, PostgreSQL and Qpid. Google supports the Apigee software. The operating system, the hardware and the health of every one of those services are your configuration to maintain.

What vendor support does not cover

In every model, the API proxies, shared flows and policies are your code. Quota and Spike Arrest settings, OAuth and API key verification, JavaScript and Java callouts, target endpoints and timeouts are configuration your team owns, and they are where most production incidents start. Vendor support will tell you whether the platform is healthy. It will not redesign a proxy that holds connections open to a slow backend.

The Apigee incidents that actually page people

• Backends overwhelmed despite a quota. Quota counts requests over a period and Spike Arrest smooths bursts; using one where the other was needed, or counting per Message Processor rather than across the cluster, lets traffic through that the backend cannot handle.
• Latency added by the proxy. Synchronous logging, service callouts and large payload transformations in the request path add time to every call. Moving logging off the critical path and caching lookups usually fixes it.
• 502 and 504 errors from target timeouts. The target endpoint's connect and I/O timeouts do not match the backend's behaviour, or keep-alive settings differ between the Router and the backend.
• Expired certificates. A TLS certificate on a virtual host, environment group or truststore expires and every API behind it fails at once.
• Cassandra and ZooKeeper in Private Cloud. Disk, repair and compaction problems on the Cassandra ring, or a ZooKeeper ensemble that loses quorum, take down token storage, KVMs and configuration with them.
• OpenLDAP. In an on-premises installation, OpenLDAP holds the usernames, credentials and roles of Edge users, so an OpenLDAP failure or an expired administrator password locks users out of the UI and the management API.

Moving from Edge to Apigee X or hybrid

With each Private Cloud version on an 18-month clock, most on-premises Apigee customers are now planning their next platform. Google publishes migration documentation and a migration assessment tool. The work is in the details: policies and features that behave differently in Apigee X, Developer Services portal and analytics changes, certificate and DNS cutover, and a period of running both platforms in parallel. Plan it with an API-by-API inventory and a rollback path for each API.

Where independent Apigee support fits

• Proxies, shared flows and policies, which no vendor support plan covers.
• On-premises Apigee infrastructure, including Cassandra, ZooKeeper and the upgrade to a supported 4.53 release.
• Apigee hybrid runtime clusters on Kubernetes, including version upgrades before end of life.
• The Edge to Apigee X or hybrid migration, planned and tested API by API.

AceMQ provides 24/7 Apigee support with a 15-minute emergency SLA and named senior engineers, alongside Apigee consulting for design and migration. Examples: a quota and Spike Arrest remediation, proxy latency support and an Edge to Apigee X migration.