Ten years inside IBM. One pivot to Kong. Now writing the playbook on how enterprises survive the AI cost crisis - one token budget at a time.
Before most organizations had even admitted they had an AI bill, Dan Temkin was already writing about tokenomics. The Senior Technical Product Marketing Manager at Kong sits at a specific and undervalued intersection: he can read a Kubernetes config and then immediately explain to a CFO why it costs too much. That combination is rarer than it sounds.
At Kong, the San Francisco-based API management platform that has raised $424 million in total funding and crossed $146 million in annual revenue, Temkin shapes the external language of the platform. His blog posts on API monetization, AI cost governance, and identity-driven security carry the tone of someone who has actually wrestled with these problems rather than studied them from a safe distance. When he writes that enterprises are "subsidizing innovation" by not metering their LLM usage, it is a provocation backed by architecture experience, not a marketing placeholder.
"Stop subsidizing innovation - make AI pay its own way."
- Dan Temkin, KongThe decade-plus at IBM was not wasted time. IBM API Connect, the enterprise integration platform Temkin spent years shaping as Senior Product Manager and API evangelist, gave him a front-row seat to how large organizations actually adopt (and misadopt) API strategy. He watched enterprises buy into service-oriented architecture, rebuild around microservices, stare down the Kubernetes learning curve, and then face the new crisis: they now had hundreds of APIs and no coherent story for how those APIs are secured, monetized, or governed. That pattern became Temkin's specialty.
At Kong, he arrived at the moment the company was expanding from pure API gateway tooling into a full platform play. Kong Gateway and Kong Mesh had established serious technical credibility. What was needed was the next layer: helping buyers understand what to do with an API platform once they had one. Temkin brought that instinct. His work on Kong Konnect's metering and billing launch, on Kong Identity's unified authentication story, and on the Kong AI Manager - a product designed to govern LLM traffic the way Kong Gateway governs API traffic - carries the fingerprints of someone who has explained integration architecture to audiences ranging from infrastructure engineers to vice presidents of digital transformation.
Based in Madison, Wisconsin while Kong operates from San Francisco, Temkin has lived the distributed-work reality he writes about. His GitHub carries 44 repositories including a receipt classification machine learning model, financial analysis tools, and user-agent string utilities - a collection that reflects what happens when a technically fluent person lets their curiosity run unsupervised. He earned the GitHub Arctic Code Vault Contributor badge, which means some of his code now lives in a decommissioned Norwegian coal mine vault designed to survive civilizational disruption. An unusual credential for a product marketer.
The conferences reflect his range. Apidays Helsinki in 2022, presenting multi-form API management from his IBM vantage point. API Summit 2025, making the case for unified API identity. AWS re:Invent, where Kong maintains a visible presence and Temkin helps carry the technical conversation. The through-line in all of it is the same: the API layer is not a technical footnote. It is the place where business rules, security policies, cost governance, and developer experience all collide. Whoever controls the gateway controls an enormous amount of organizational destiny.
Right now, the conversation Temkin is most interested in is AI governance - not as a compliance checkbox, but as an engineering and economic problem. When an enterprise runs dozens of LLM workloads and each model call costs money and carries latency implications, the API gateway becomes the most natural enforcement point. Token budgets, semantic caching, prompt security guardrails, model switching - these are API gateway problems wearing AI costumes. Temkin is building the language to make that argument, one blog post and conference talk at a time.
Over a decade of practice spanning IBM API Connect and Kong Konnect - as implementer, customer, seller, and product manager. Temkin has seen API governance fail and succeed from every seat at the table.
When LLMs run at scale, they run through APIs. Temkin argues that token budgets, model switching, semantic caching, and prompt guardrails are API gateway problems dressed in new clothes. Kong AI Manager is the product that proves it.
Security at the API layer is not a feature - it is an organizational stance. Temkin's writing on enabling business agility through API security governance focuses on policy-as-code and enforcement at the gateway, not in each individual service.
Usage-based billing, metering, entitlements - the commercial layer that turns API infrastructure from a cost center into a revenue engine. The Kong Konnect Metering & Billing product, powered by OpenMeter, reflects this work directly.
Fragmentary authentication - a different IdP per service, inconsistent claim handling, duplicated policy - is the silent killer of API platform coherence. Kong Identity exists to consolidate it. Temkin writes the case for why consolidation matters.
From ESB-centric patterns to API-led integration to cloud-native microservices - Temkin has narrated the evolution at both IBM and Kong, helping enterprises understand which architectural chapter they are actually in.
Series A through Series E
Latest funding round
Kong Inc. run rate
Globally distributed
Each layer of Kong's platform has a story. Temkin is the one who tells it.
The argument that AI cost governance is not optional anymore - it is an infrastructure requirement. Kong Konnect's new metering layer makes token budgets and API billing a first-class platform feature.
Kong BlogWhy fragmented identity - different authentication providers per service - is the root cause of security debt that no number of individual fixes can resolve. Kong Identity as the consolidation layer.
Kong BlogToken economics for LLM workloads: why the API gateway is the most natural enforcement point for token budgets, semantic caching, and cost allocation across teams and use cases.
Kong BlogThe reframe: API security is not a cost center constraint. It is the mechanism that makes an organization's APIs safe to expose and therefore actually useful. A case study in governance enabling speed.
Kong BlogThe acquisition integration story: how Kong turned OpenMeter into the commercial backbone of Konnect and what it means for enterprises that want to monetize their API surface area.
Kong BlogArchitecture patterns for the transition from ESB-centric integration to API-led approaches. Written from the IBM vantage point, the article remains one of the clearer explanations of why the transition is not just technical.
APIsceneMore than a decade at IBM shaping IBM API Connect from a top-5 product to an industry leader in API lifecycle management. Front-row seat to the transition from SOAP to REST, from monoliths to microservices.
Alongside product management, built a track record as an integration evangelist - explaining enterprise API strategy to both technical and business audiences across conferences and publications.
Presented "Multi-form API Management" at Apidays Helsinki representing IBM's perspective on the API lifecycle, one of several international conference appearances building the thought leadership track record.
Moves from IBM to Kong at the moment Kong is scaling from API gateway tooling to a full platform play. Takes responsibility for technical positioning of Kong Gateway, Kong Mesh, Kong Konnect, and subsequently Kong AI Manager.
November 2024: Kong secures its largest funding round to date. Temkin contributes to the go-to-market messaging for Kong Identity and the Kong AI Manager product announcement. Total funding reaches $424M.
Featured speaker at API Summit 2025 on Kong Identity and API management strategy. Regular presenter at AWS re:Invent representing Kong's perspective on cloud-native API and AI governance. Authors major blog posts on tokenomics and identity unification.
Continues driving Kong's positioning at the intersection of API management and AI governance - making the case that token budgets, MCP governance, and LLM traffic management are API gateway problems for the enterprise.
"Stop subsidizing innovation - make AI pay its own way."
On AI cost governance, Kong Blog"Unified API management and identity accelerates innovation, strengthens security posture, reduces operational costs, and improves the developer experience."
On Kong Identity, Kong Blog"API security isn't just a technical challenge - it's how you enable business agility."
API Summit 2025His GitHub includes a receipt classification machine learning model - not a standard side project for a product marketer. 44 repositories and counting.
GitHub Arctic Code Vault Contributor: some of Temkin's open source code is preserved inside a decommissioned Norwegian coal mine designed to outlast civilization. Not many product marketers can say that.
Works from Madison, Wisconsin while his company runs out of San Francisco. Fully distributed before distributed work was a policy debate.
Spent over 10 years at IBM - long enough to watch the API management market cycle from SOAP to REST, from ESBs to microservices, from containers to Kubernetes, and now from K8s to AI gateways.
Wrote about "tokenomics" for APIs and AI systems before most enterprises even knew they had a token bill. The vocabulary got there first; the budget conversations followed.