Otoroshi 18.0.0 is the largest release we have shipped in years, and probably the most carefully prepared one. The whole runtime moved to Scala 3, Play 3 and Apache Pekko, and Service Descriptors -- deprecated for four years -- are finally gone.

It is also, by design, meant to be one of the most boring upgrades you will ever do. Your routes, plugins, API keys, certificates and exporters are untouched. Your traffic does not care.

And once the new foundations were in, we started building on them: every caller of an API is now an API key, consumers can carry their own plugin chain, any plugin can run conditionally, and the whole gateway went through two security audits. Then we checked everything, twice.

For a long time, getting a clear picture of what was actually happening on your gateway meant plugging Otoroshi into an external observability stack -- Elastic, Kafka, Grafana, you name it -- then maintaining yet another set of dashboards, queries and alert rules far away from where your routes and APIs actually live.

We thought this should be a lot simpler. So we built User Analytics & Dashboards: a complete analytics stack that lives directly inside Otoroshi, on top of a dedicated PostgreSQL data exporter, with curated queries, a beautiful grid of widgets and a threshold-based alert engine. No external stack to plug, no extra UI to learn.

The Otoroshi backoffice has been with us for a long time, and over the years it grew organically -- screen by screen, feature by feature. The result was a UI that worked, but felt dated, a little inconsistent from one page to another, and frankly a bit harsh on the eyes (especially in light mode, where staring at a wall of pure white is no one's idea of fun).

We took the time to refresh both themes from the ground up, and we are pretty happy with the result.

Welcome to the official Otoroshi blog! This is the place where we will share news, release announcements, tutorials, and insights about Otoroshi and the API gateway ecosystem.