In the rapidly evolving world of API management, the conversation around "the great unbundling of API management" has recently gained traction. This movement, highlighted by industry experts and analysts, including a recent [Forbes article](https://www.forbes.com/sites/forbestechcouncil/2024/02/07/four-trends-shaping-apis-in-2024/?sh=602e2e5d3369)Forbes article, reflects a shift towards a more componentized approach in API tooling offerings. Such an approach caters to the enterprise's specific needs, moving away from the traditional "does-it-all" solutions.
At Kong, we’re not just observers of this trend; we’re active participants and innovators, aligning our platform's philosophy with the needs of a changing landscape through what we call the "incremental buy-in" approach.
The concept of unbundling in API management points to the fragmentation of API lifecycle management into distinct, specialized tools and components. This trend stems from the need for flexibility and customization as enterprises look to address their unique challenges with tailored solutions that are each best designed to address the specific area of the API lifecycle at hand.
Kong’s incremental buy-in product principle is designed to empower organizations to start with what they need and expand their toolset organically as their requirements evolve. This approach isn’t about offering a one-size-fits-all solution but providing a suite of best-in-class capabilities that cater to different aspects of the API lifecycle and its stakeholders, including application teams, infrastructure teams, platform teams, and API product owners.
Kong’s platform comprises:
[](https://insomnia.rest/)Each of these products is designed to address specific needs of the API lifecycle management and provide the best possible experience for that specific need — it’s tailored for that specific aspect of the API lifecycle management.
As an example, one can start by introducing a K8s native API gateway for internal ingress traffic management to Kubernetes clusters leveraging the Kong Ingress Controller, and then, when ready or the need arises, introduce Kong Mesh for service-to-service traffic management and security. The solution can then, at a later time, be extended with Edge traffic management via the Kong Gateway, and last but not least, an organizational-wide rollout through a Platform Team enabled via Kong Konnect.
With the incremental buy-in philosophy, we’re designing each of these products to be independently adoptable, based on the use case at hand, without the necessity to commit to the entire suite from the outset. This enables a truly incremental approach, allowing organizations to grow into our ecosystem as their needs dictate.
The benefits of the incremental buy-in philosophy are multifold:
Kong's partnership with Rabobank, a premier international financial services provider, epitomizes the essence of our incremental buy-in philosophy. This collaboration highlights how our platform's adaptability and modularity enable organizations like Rabobank to customize their API management ecosystems to meet evolving needs.
[During a recent fireside chat](https://konghq.com/resources/videos/rabobank-customer-story)During a recent fireside chat at Kong’s API Summit, the Rabobank API platform team shared their journey of adopting Kong's Konnect platform as a foundation for their API platform development.
It began with the integration of Kong Gateway, laying a solid foundation for API traffic management and security. As their requirements grew, Rabobank further embraced Kong Konnect for its [federated governance](https://konghq.com/solutions/secure-and-govern-apis)federated governance capabilities, empowering their platform team to construct a comprehensive API platform. This platform was enriched with Rabobank’s own ecosystem of capabilities around API Portals, API Analytics, and more as depicted by the diagram below.
*Rabobank’s “constellation” of components forming their new API platform*
Rabobank’s approach illustrates the incremental buy-in model's strength, enabling them to begin with core Kong offerings and progressively integrate more components and external tools. This strategy not only aligns with their specific operational needs but also exemplifies how organizations can fluidly adapt to the "great unbundling" of API management.
The trend towards the unbundling of API management reflects the industry's move towards more agile, flexible, and customized solutions. At Kong, our incremental buy-in philosophy embodies this shift, providing a pathway for organizations to adopt and grow their API management capabilities in a way that aligns with their unique needs and pace. As we navigate the evolving API landscape, Kong remains committed to empowering our customers with the tools and flexibility they need to succeed in an increasingly interconnected world.
By embracing the principles of incremental buy-in, Kong not only acknowledges the trend of API management unbundling but also leads the way in providing adaptable, scalable, and efficient solutions for the modern enterprise.
To get started with Kong's portfolio of products (using incremental buy-in, of course) [try Kong Konnect](https://konghq.com/products/kong-konnect/register)try Kong Konnect for free.
How to empower engineers and increase velocity without shadow IT with fast and secure API infrastructure strategy We want our engineering teams to move fast and be agile, yet many organizations confuse ownership of the infrastructure with ownership
[](https://konghq.com/blog/enterprise/balancing-autonomy-and-control)
As API adoption continues, early autonomy incentives often have led to shadow IT and infrastructure sprawl. To secure our growing API attack surface, technology leaders must implement organizational accountability through security oversight, platfor
[](https://konghq.com/blog/enterprise/culture-accountability-application-development)
Imagine 47 million requests hitting your platform last month. Can you prove who made each one—and invoice with confidence? If that question tightens your stomach, you're not alone. Metered billing for APIs promises fair, transparent pricing that s
[](https://konghq.com/blog/enterprise/guide-to-metered-billing-for-apis)
In large organizations, platform architecture tends to be more historical artifact than intentional design. At the foundation of the stack sit monoliths that predate modern API standards; many of them are too risky or too costly to decommission full
[](https://konghq.com/blog/enterprise/api-composition-packaging)
This is the pitch to the board and the C-suite. It must be brutally concise, focused entirely on your business outcomes, not the technology. If the first page doesn't articulate value, the strategy dies. Why? It immediately frames the initiative in
[](https://konghq.com/blog/enterprise/enterprise-api-strategy-legacy-modernization)
The first pillar is enablement. Developers need tools that reduce friction when building AI-powered applications and agents. This means providing: Native MCP support for connecting agents to enterprise tools and data sources SDKs and frameworks op
[](https://konghq.com/blog/enterprise/agentic-ai-developer-platform)
APIs are the connective tissue of digital products and services, and they're the lifeblood of AI. APIs shape customer experiences, power partner ecosystems, and accelerate enterprise innovation. As organizations double down on API-first strategies,
[](https://konghq.com/blog/enterprise/api-product-management-guide)