Unified API & Service Catalog in Kong Konnect Explained
Learn how Kong Konnect's new unified catalog brings APIs and services together into a single source of truth, helping organizations manage the full lifecycle of their API platform — from design to governance to consumption.
Key Takeaways:
- APIs and services are fundamentally different — APIs can exist as abstract designs before any code is written, while services are always running applications with operational needs.
- Kong Konnect now unifies APIs and services under a single Catalog, replacing the previous separate service catalog and dev portal API views.
- The Catalog is offered at no additional cost within Konnect, with pricing only applying when publishing to portals or enabling governance features like scorecards.
- Custom integrations allow you to pull live data from third-party sources like GitHub, Datadog, and PagerDuty, keeping your catalog automatically in sync.
- Dev Portal serves as the distribution channel for specific audiences, while Catalog is the engineering-focused ""sausage making"" engine where all assets are managed.
0:00 - Introduction: A New Holistic Approach
0:50 - APIs vs. Services: Why They're Different
3:10 - Who Uses APIs vs. Services?
5:30 - Catalog and Dev Portal Changes in Konnect
7:00 - Key Focus Areas: Custom Attributes, Linking, and Integrations
9:30 - Pricing: Catalog at No Additional Cost
10:15 - Dev Portal vs. Catalog: When to Use Each
13:00 - Governance, Scorecards, and Future Vision
15:30 - Audience Q&A: Enterprise Catalogs and Schema Registry
Explore Kong Konnect: https://konghq.com/products/kong-konnect
#KongKonnect #APICatalog #APIManagement #DevPortal #APIGovernance
Ready to unify your API and service landscape? Visit konghq.com to get started with Kong Konnect today.