<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>VioX AI Blog</title>
  <subtitle>Frontier AI dispatches from VioX.</subtitle>
  <link href="https://www.viox.ai/feed.xml" rel="self"/>
  <link href="https://www.viox.ai/blog"/>
  <id>https://www.viox.ai/blog</id>
  <updated>2026-04-29T00:00:00Z</updated>
  <author><name>VioX AI</name><uri>https://www.viox.ai</uri></author>
  <entry>
    <title>Mistral Medium 3.5 ships remote agents — here&apos;s why we still wouldn&apos;t route production traffic through them</title>
    <link href="https://www.viox.ai/blog/mistral-medium-35-remote-agents"/>
    <id>https://www.viox.ai/blog/mistral-medium-35-remote-agents</id>
    <published>2026-04-29T00:00:00Z</published>
    <updated>2026-04-29T00:00:00Z</updated>
    <summary>Mistral just shipped Medium 3.5 with remote agents that execute code server-side. We explain why VioX still orchestrates tool calls client-side — and when remote execution makes sense.</summary>
    <category term="Frontier"/>
  </entry>
  <entry>
    <title>OpenAI on AWS Bedrock — one day after the Microsoft split</title>
    <link href="https://www.viox.ai/blog/openai-on-aws-bedrock-one-day-after-microsoft-split"/>
    <id>https://www.viox.ai/blog/openai-on-aws-bedrock-one-day-after-microsoft-split</id>
    <published>2026-04-29T00:00:00Z</published>
    <updated>2026-04-29T00:00:00Z</updated>
    <summary>Microsoft and OpenAI dissolve exclusivity. 24 hours later, AWS announces OpenAI models on Bedrock plus a jointly-built agent service. The math: never run on one vendor.</summary>
    <category term="Frontier"/>
  </entry>
  <entry>
    <title>The 6-layer agentic stack we deploy for SMBs</title>
    <link href="https://www.viox.ai/blog/six-layer-agentic-stack"/>
    <id>https://www.viox.ai/blog/six-layer-agentic-stack</id>
    <published>2026-04-29T00:00:00Z</published>
    <updated>2026-04-29T00:00:00Z</updated>
    <summary>Reasoning at the bottom, business outcomes at the top. The architecture we run inside every VioX OS deployment — and why each layer earns its place.</summary>
    <category term="Stack"/>
  </entry>
  <entry>
    <title>Evals on day zero — why VioX OS ships every agent with a test suite</title>
    <link href="https://www.viox.ai/blog/evals-on-day-zero"/>
    <id>https://www.viox.ai/blog/evals-on-day-zero</id>
    <published>2026-04-28T00:00:00Z</published>
    <updated>2026-04-28T00:00:00Z</updated>
    <summary>An agent without evals is a complaint waiting to happen. Here&apos;s the discipline we hard-code into every VioX OS deployment, and the eval suite every one of our eight agents ships with.</summary>
    <category term="Stack"/>
  </entry>
  <entry>
    <title>We migrated Goldie from Retell to ElevenLabs in 4 days. Here&apos;s the diff.</title>
    <link href="https://www.viox.ai/blog/migrating-goldie-retell-to-elevenlabs"/>
    <id>https://www.viox.ai/blog/migrating-goldie-retell-to-elevenlabs</id>
    <published>2026-04-27T00:00:00Z</published>
    <updated>2026-04-27T00:00:00Z</updated>
    <summary>The catering concierge agent for Golden Plate was running on Retell. We ported it to ElevenLabs ConvAI in four working days. What changed, what broke, what got better — and the playbook we&apos;ll use next time.</summary>
    <category term="Field notes"/>
  </entry>
</feed>
