<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Devin </title>
    <description>The latest articles on DEV Community by Devin  (@dvnold).</description>
    <link>https://dev.to/dvnold</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3582171%2Fb5f9a350-4f04-4da4-8382-0b92e3721e2b.jpeg</url>
      <title>DEV Community: Devin </title>
      <link>https://dev.to/dvnold</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dvnold"/>
    <language>en</language>
    <item>
      <title>Kaeso</title>
      <dc:creator>Devin </dc:creator>
      <pubDate>Fri, 23 Oct 2026 05:11:47 +0000</pubDate>
      <link>https://dev.to/dvnold/kaeso-2aj9</link>
      <guid>https://dev.to/dvnold/kaeso-2aj9</guid>
      <description>&lt;p&gt;A long time has passed since I last worked on a personal project which I worked on solely by myself, and whenever I did, I learned an enormous amount by doing so. Today I will be presenting my plans for &lt;a href="https://kaeso.app" rel="noopener noreferrer"&gt;Kaeso&lt;/a&gt;, an open source AI Gateway which will initially aim to compete with &lt;a href="https://www.litellm.ai" rel="noopener noreferrer"&gt;LiteLLM&lt;/a&gt; and then move on by adapting new features. My goal is to build a foundation for the future, and by building Kaeso this is the perfect way. I personally love and believe in open source because without it, I would definitely not be where I am right now.&lt;/p&gt;

&lt;p&gt;From my understanding and knowledge of market needs, I believe that this idea is not a good one and will probably fail, at least as a startup it would. This project in its current state is a solved problem and the initial user base will be very small as LiteLLM is significantly further developed.&lt;/p&gt;

&lt;p&gt;Kaeso in its first version will be split into four core components which will shape its fundamental structure:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fc42o7cj0d72qjz6bqsmo.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fc42o7cj0d72qjz6bqsmo.png" alt="Kaeso architecture: the console (Next.js web interface) and the TypeScript client send API requests to the gateway (API, routing, auth, budgets, logs), which sends provider requests to the unified provider APIs" width="800" height="477"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As &lt;a href="https://archive.computerhistory.org/resources/access/text/2019/03/102789075-05-01-acc.pdf" rel="noopener noreferrer"&gt;Apple's early Marketing Philosophy&lt;/a&gt; said, people DO judge a book by its cover. So the first big difference will be the UX/UI for the people using Kaeso. In my view, the current LiteLLM User Interface has considerable room for a cleaner and more cohesive experience. Kaeso will aim to create a good environment for all kinds of users.&lt;/p&gt;

&lt;p&gt;Of course, announcing this as the only change is vague. In most cases nobody cares about the UI and it's the functionality which matters, but as I'm currently just trying to establish a baseline, this is the first and best visible best practice I can create.&lt;/p&gt;

&lt;p&gt;Lastly, I want to mention that the Kaeso Roadmap will be fully led by me and that will probably remain the case at its core.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>ai</category>
      <category>llm</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
