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

Two kinds of problems only show up once an API is already live. Something breaks, and a team needs visibility into one specific node right now — not after a redeploy. Or the right behavior for a request depends on who's calling it: a consumer's plan, a token claim, metered usage, or boolean feature…











