We’re excited to announce new features in [Kong Konnect](https://konghq.com/products/cloud-api-platform)Kong Konnect, including the ability to take advantage of identity management APIs, streamlined certificate management, and latency metrics as part of [Analytics](https://docs.konghq.com/konnect/analytics/)Analytics. Read on to learn about these features and how kong helps [future-proof API security](https://konghq.com/campaign/secure-api-scalability)future-proof API security.
Now you can manage your users and their access to Kong Konnect from your choice of identity provider or enterprise resource planning (ERP) systems. You can build custom integrations with Konnect’s identity management APIs to manage users, teams, team memberships, team mappings, and role assignments.
Refer to our [documentation](https://docs.konghq.com/konnect/api/)documentation for additional details.
Now you can have better visibility for your certificate management operations to reduce operational complexity and ensure consistent certificate configurations. Use [Runtime Manager](https://docs.konghq.com/konnect/runtime-manager/)Runtime Manager to create, store, and organize all of the certificates required for runtime instances connected to your [runtime groups](https://docs.konghq.com/konnect/runtime-manager/runtime-groups/)runtime groups.
*Figure 1: Streamlined certificate management*
We’re happy to announce that developer portal integration with Okta now graduates to public beta for Enterprise subscribers. With this integration, you can reduce the overhead of creating the application and mapping the credentials in both the [Dev Portal](https://docs.konghq.com/konnect/dev-portal/)Dev Portal and third-party identity provider. The Dev Portal directly integrates with your existing identity provider for the client authentication and authorization management, providing a more secure solution for your distributed applications.
You can learn more about [dynamic client registration](https://datatracker.ietf.org/doc/html/rfc7591)dynamic client registration in the [documentation](https://docs.konghq.com/konnect/dev-portal/applications/dynamic-client-registration/okta/)documentation.
Now you can label services according to their lifecycle stage: [Publish, Deprecated, or Unpublished](https://docs.konghq.com/konnect/servicehub/service-versions/#manage-the-service-version-lifecycle)Publish, Deprecated, or Unpublished.
Apply these labels to individual service versions in [Service Hub](https://docs.konghq.com/konnect/servicehub/)Service Hub, which will also be reflected in the Dev Portal. Enable API developers to clearly communicate with API consumers (both internal and external) about the lifecycle of a service version. For example, a service version labeled "Deprecated" indicates that it will be deprecated soon, suggesting API consumers to switch to another service version.
*Figure 2: Service version lifecycle labels*
Get real-time insights into how your APIs and gateways are performing using [Kong Analytics](https://docs.konghq.com/konnect/analytics/)Kong Analytics (formerly known as "Vitals").
With Analytics, you can visually track the golden signals of monitoring — traffic, error rate, and now latency to help you quickly identify any application performance issues.
View latency information for each request for runtime groups and services across the Kong Konnect platform. Visibility into latency metrics helps you quickly identify and address any performance issues to optimize overall performance.
Update your runtimes to [Kong Gateway 3.0](https://konghq.com/blog/kong-gateway-3-0)Kong Gateway 3.0 to take advantage of latency monitoring. Get started with the [newest version](https://docs.konghq.com/konnect/runtime-manager/runtime-instances/gateway-runtime-docker/)newest version or [upgrade](https://docs.konghq.com/konnect/runtime-manager/runtime-instances/upgrade/)upgrade to the latest version of Kong Gateway in Konnect today.
*Figure 3: Analytics overview latency insights*
Enjoy an easier-to-use, more intuitive user experience in Runtime Manager. Now, runtime group IDs will not be shown in the summary view. You will be able to see IDs in the Runtime Group – Instances view.
The Runtime Instances table under the Runtime Manager – Instances view can now be refreshed using the refresh button to ensure the latest status for each instance is shown. Additionally, if a runtime instance is disconnected, you have the option to remove its entry from the table instead of waiting for it to be cleared as a part of the auto-refresh cycle.
Lastly, in the Runtime Instances view, after any edits to the runtime group, you will now return to the Runtime Instances view instead of returning to the Runtime Manager overview page.
*Figure 4: Runtime Instances view*
Want to learn more? Dive into all the details in the [documentation](https://docs.konghq.com/konnect/)documentation.
Ready to get started? Check out the available [Kong Konnect plans](https://konghq.com/pricing)Kong Konnect plans and choose one that fits your business needs. Not ready to subscribe? Start your [Kong Konnect free trial](https://cloud.konghq.com/register?_ga=2.64017455.1813879452.1666024254-1839953283.1663198607)Kong Konnect free trial or schedule a [personalized demo](https://konghq.com/contact-sales)personalized demo today!
Managed Redis cache is a turnkey "Shared State" add-on for Kong Dedicated Cloud Gateways. It is designed to combine the performance of an in-memory data store with the simplicity of a SaaS product. When you spin up a Dedicated Cloud Gateway in Kong
[](https://konghq.com/blog/product-releases/multicloud-cloud-gateways-managed-redis-cache)
The Kong MCP Registry acts as a central directory for AI agents and clients to access services that provide context or take action. For AI agents, think of it as a combination of a "Service Catalog" and a "Developer Portal." It offers the metadata,
[](https://konghq.com/blog/product-releases/kong-mcp-registry-tech-preview)A quick refresher: Kong Cloud Gateways Kong Cloud Gateways are fully managed, high-performance data planes running on customer-dedicated infrastructure, orchestrated and operated by Kong through Kong Konnect . Customers can choose between: Serverle
[](https://konghq.com/blog/product-releases/kong-cloud-gateways-2025-news-recap)
The challenge: A disconnected world Consider the typical enterprise architecture in a relatively mature organization, an API management layer defines and deploys services to an API gateway, an Identity Provider (IDP) manages human user identities, a
[](https://konghq.com/blog/enterprise/api-management-and-identity)
Feed Agents (and humans, too) with *all* of your APIs While multi-gateway vendor deployments have been found to be lacking as a long-term strategy, the reality is that every large organization is — at some point — going to struggle with trying to wr
[](https://konghq.com/blog/enterprise/enable-enterprise-wide-agentic-access-to-apis)
Bridging the API (and API access) gap between AI coding tools, agents, and the APIs that they “eat” Data might be the fuel for AI. But APIs are the proper way to package that “fuel” as AI-ready “food” is through the API. AI coding tools can do a lot
[](https://konghq.com/blog/product-releases/mcp-support-across-konnect)
Explore Kong Konnect’s new approach to API Orchestration Different teams, different preferences API orchestration at the gateway layer can involve coordinating multiple services, transforming data, and managing request flows. Some teams prefer worki
[](https://konghq.com/blog/product-releases/datakit-flow-editor-api-orchestration)