<?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>Forem: Dmitry</title>
    <description>The latest articles on Forem by Dmitry (@if).</description>
    <link>https://forem.com/if</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3849096%2Fde44c27c-bd8f-4070-b244-59f9ee927335.png</url>
      <title>Forem: Dmitry</title>
      <link>https://forem.com/if</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/if"/>
    <language>en</language>
    <item>
      <title>Aximo — a local Rust STT API for CPU-only inference</title>
      <dc:creator>Dmitry</dc:creator>
      <pubDate>Wed, 22 Apr 2026 22:20:47 +0000</pubDate>
      <link>https://forem.com/if/aximo-a-local-rust-stt-api-for-cpu-only-inference-3e5d</link>
      <guid>https://forem.com/if/aximo-a-local-rust-stt-api-for-cpu-only-inference-3e5d</guid>
      <description>&lt;p&gt;I built a local speech-to-text API in Rust that runs on CPU&lt;/p&gt;

&lt;p&gt;I recently built Aximo, a self-hosted speech-to-text microservice designed to run locally on CPU, without depending on cloud APIs or external SaaS.&lt;/p&gt;

&lt;p&gt;The idea was straightforward: I wanted an STT service that could be deployed like any other backend, stay fully local, and still be clean enough architecturally to evolve beyond a quick experiment.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/agent-axiom/aximo" rel="noopener noreferrer"&gt;Aximo&lt;/a&gt; is written in Rust, uses Parakeet v3 for local inference, exposes an HTTP API for transcription, and includes a WebSocket layer for realtime use cases. I also added Docker, OpenAPI, and a multi-crate workspace layout to keep the codebase modular from the start.&lt;/p&gt;

&lt;p&gt;One detail I particularly liked: I extended Swagger UI so I can record audio directly from the microphone and send it to the API for testing. It’s a small feature, but it makes the developer experience much nicer when iterating on the service.&lt;/p&gt;

&lt;p&gt;At this point, I’d call it a solid MVP rather than a production-ready system, but it already works well for local experimentation and as a foundation for a self-hosted STT stack.&lt;/p&gt;

&lt;p&gt;One notable addition: I extended Swagger to support sending recordings directly from the microphone.&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.amazonaws.com%2Fuploads%2Farticles%2Fkg1xeza6l7r6yyig7a6m.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.amazonaws.com%2Fuploads%2Farticles%2Fkg1xeza6l7r6yyig7a6m.png" alt=" " width="800" height="769"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/agent-axiom/aximo" rel="noopener noreferrer"&gt;github.com/aximo&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>rust</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Secure AI Agent Architecture</title>
      <dc:creator>Dmitry</dc:creator>
      <pubDate>Sun, 29 Mar 2026 10:35:30 +0000</pubDate>
      <link>https://forem.com/if/secure-ai-agent-architecture-4317</link>
      <guid>https://forem.com/if/secure-ai-agent-architecture-4317</guid>
      <description>&lt;h1&gt;
  
  
  I’ve Started Writing an Open Book on Secure AI Agent Architecture
&lt;/h1&gt;

&lt;p&gt;I’ve started writing an open book on the architecture of secure AI agents.&lt;/p&gt;

&lt;p&gt;The goal is to build a practical engineering reference — not a collection of flashy demos, but a structured guide to production-grade agent systems: control planes, policy boundaries, tool execution, memory, observability, evaluations, approvals, and governance.&lt;/p&gt;

&lt;p&gt;The first chapters are already live:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;English:&lt;/strong&gt; &lt;a href="https://agent-axiom.github.io/agent-arch/en/" rel="noopener noreferrer"&gt;https://agent-axiom.github.io/agent-arch/en/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Chinese:&lt;/strong&gt; &lt;a href="https://agent-axiom.github.io/agent-arch/zh/" rel="noopener noreferrer"&gt;https://agent-axiom.github.io/agent-arch/zh/&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Repository: &lt;a href="https://github.com/agent-axiom/agent-arch" rel="noopener noreferrer"&gt;https://github.com/agent-axiom/agent-arch&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There is a lot of excitement around agents, but far less shared engineering guidance on how to build them safely and operate them reliably in production. This project is my attempt to help close that gap.&lt;/p&gt;

&lt;p&gt;I’d genuinely appreciate thoughtful feedback from the community:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;what feels solid&lt;/li&gt;
&lt;li&gt;what is missing&lt;/li&gt;
&lt;li&gt;what seems debatable&lt;/li&gt;
&lt;li&gt;what should be improved&lt;/li&gt;
&lt;li&gt;what operational or security practices deserve more attention&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If this topic is close to your work, I’d be glad to hear your critique, ideas, counterexamples, and contributions.&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>architecture</category>
      <category>security</category>
    </item>
  </channel>
</rss>
