How do you extend a Kono API gateway?

Drop a Go file implementing four methods. Compile. Load. No source reads, no forking.

Kono vs KrakenD: Which for plugins?

Kono if you hate boilerplate. KrakenD if you need battle-tested scale — but expect the 60-line tax.

What's Lumos in Kono?

LuaJIT sidecar for dynamic scripts. Unix socket comms. Perfect for hot auth tweaks without restarts. One last jab: If your gateway forces forking, fire the architect. Kono shows better.

🏗️ DevOps & Infrastructure

Why Forking API Gateways Is for Suckers — Kono Proves It

API gateways promise extensibility. Most deliver a nightmare. Kono changes that — with plugins you write in minutes, not hours.

theAIcatchup Apr 09, 2026 3 min read

Kono API gateway plugin architecture with LuaJIT Lumos sidecar

⚡ Key Takeaways

Kono cuts API gateway plugin boilerplate to four simple methods — no wrappers or registerers. 𝕏
Lumos delivers fast Lua scripting via Unix socket, dodging embedded interpreter pitfalls. 𝕏
Ditch forking: Kono's design predicts the death of custom gateway forks in OSS. 𝕏

Published by

theAIcatchup

Community-driven. Code-first.

#API gateway #Go plugins #Kono #KrakenD

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

Kubernetes Just Killed Ingress NGINX: Half Your Clusters Are Suddenly Vulnerable

That Friday Deploy That Nuked 20% of Users — And the Fixes That Actually Stuck

Three Hours of Green Lies: How OpenTofu and GitHub Actions Fixed My IaC Nightmares

The Single Score That Made Factory Operators Obsessed with Dashboards

Stay in the loop