# Kong Bot Detector for Dedicated Cloud Gateways

Bots make up more than a third of internet traffic, and API endpoints attract more of it than web pages do. Scanners hunting for .env files, credential-stuffing scripts, LLM training crawlers, and the long tail of low-effort probes all hit your gate

# Event-Driven AI: Agents Shouldn’t Have to Keep Asking if Something Happened

Consider a bank using an AI agent to investigate potentially fraudulent transactions. A transaction is processed and the bank’s fraud detection system identifies suspicious activity. That event is published to Kafka: fraud.suspected The bank’s Fraud

# Kong API Gateway 3.16: Runtime control, API monetization, and FIPS 140-3

If you've run Kong at scale, you know the moment: a spike in 5xxs from one specific data plane node, a customer opening a ticket about intermittent failures, or a partner integration that fails calls no one else does. Debug-level logs would tell you

# Kong Gateway Now Supports FIPS 140-3

FIPS 140-3 is the U.S. and Canadian government standard for validating cryptographic modules - the code that does encryption, key generation, and digital signatures. It's issued by NIST and CCCS and enforced through CMVP, the Cryptographic Module Va

# Kong Gateway Enterprise 3.4.x.x EOL

# API + AI Summit 2026 Launch Recap

Standing up a production agent means taking it through six stages: React : the agent must be able to react to events as they occur internal or external to the business Discover : Once running, can the agent find what it needs? This means MCP Servers

# Kong Gateway 3.14: More Control, Less Toil With Simplified Security and Policies

Managing gateway configurations at scale is harder than it looks. When a plugin needs to apply to most routes, but not all, teams could either duplicate configuration across routes and violate DRY (“Don’t Repeat Yourself”) principles, or write custo

# Kong Bot Detector for Dedicated Cloud Gateways

Bots make up more than a third of internet traffic, and API endpoints attract more of it than web pages do. Scanners hunting for .env files, credential-stuffing scripts, LLM training crawlers, and the long tail of low-effort probes all hit your gate

# Event-Driven AI: Agents Shouldn’t Have to Keep Asking if Something Happened

Consider a bank using an AI agent to investigate potentially fraudulent transactions. A transaction is processed and the bank’s fraud detection system identifies suspicious activity. That event is published to Kafka: fraud.suspected The bank’s Fraud

# Kong API Gateway 3.16: Runtime control, API monetization, and FIPS 140-3

If you've run Kong at scale, you know the moment: a spike in 5xxs from one specific data plane node, a customer opening a ticket about intermittent failures, or a partner integration that fails calls no one else does. Debug-level logs would tell you

# Kong Gateway Now Supports FIPS 140-3

FIPS 140-3 is the U.S. and Canadian government standard for validating cryptographic modules - the code that does encryption, key generation, and digital signatures. It's issued by NIST and CCCS and enforced through CMVP, the Cryptographic Module Va

# Kong Gateway Enterprise 3.4.x.x EOL

# API + AI Summit 2026 Launch Recap

Standing up a production agent means taking it through six stages: React : the agent must be able to react to events as they occur internal or external to the business Discover : Once running, can the agent find what it needs? This means MCP Servers

# Kong Gateway 3.14: More Control, Less Toil With Simplified Security and Policies

Managing gateway configurations at scale is harder than it looks. When a plugin needs to apply to most routes, but not all, teams could either duplicate configuration across routes and violate DRY (“Don’t Repeat Yourself”) principles, or write custo

# Kong Bot Detector for Dedicated Cloud Gateways

Bots make up more than a third of internet traffic, and API endpoints attract more of it than web pages do. Scanners hunting for .env files, credential-stuffing scripts, LLM training crawlers, and the long tail of low-effort probes all hit your gate

# Event-Driven AI: Agents Shouldn’t Have to Keep Asking if Something Happened

Consider a bank using an AI agent to investigate potentially fraudulent transactions. A transaction is processed and the bank’s fraud detection system identifies suspicious activity. That event is published to Kafka: fraud.suspected The bank’s Fraud

# Kong API Gateway 3.16: Runtime control, API monetization, and FIPS 140-3

If you've run Kong at scale, you know the moment: a spike in 5xxs from one specific data plane node, a customer opening a ticket about intermittent failures, or a partner integration that fails calls no one else does. Debug-level logs would tell you

# Kong Gateway Now Supports FIPS 140-3

FIPS 140-3 is the U.S. and Canadian government standard for validating cryptographic modules - the code that does encryption, key generation, and digital signatures. It's issued by NIST and CCCS and enforced through CMVP, the Cryptographic Module Va

# Kong Gateway Enterprise 3.4.x.x EOL

# API + AI Summit 2026 Launch Recap

Standing up a production agent means taking it through six stages: React : the agent must be able to react to events as they occur internal or external to the business Discover : Once running, can the agent find what it needs? This means MCP Servers

# Kong Gateway 3.14: More Control, Less Toil With Simplified Security and Policies

Managing gateway configurations at scale is harder than it looks. When a plugin needs to apply to most routes, but not all, teams could either duplicate configuration across routes and violate DRY (“Don’t Repeat Yourself”) principles, or write custo