<?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: Obed Meshach</title>
    <description>The latest articles on DEV Community by Obed Meshach (@obed_meshach_55c18b915f0f).</description>
    <link>https://dev.to/obed_meshach_55c18b915f0f</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%2F4199439%2F0a85162d-1c42-46fa-80b8-7c055a9b56ee.jpg</url>
      <title>DEV Community: Obed Meshach</title>
      <link>https://dev.to/obed_meshach_55c18b915f0f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/obed_meshach_55c18b915f0f"/>
    <language>en</language>
    <item>
      <title>Building AgentMesh: Exploring a Shared Compute Infrastructure for AI Workloads</title>
      <dc:creator>Obed Meshach</dc:creator>
      <pubDate>Mon, 02 Nov 2026 21:19:33 +0000</pubDate>
      <link>https://dev.to/obed_meshach_55c18b915f0f/building-agentmesh-exploring-a-shared-compute-infrastructure-for-ai-workloads-2k88</link>
      <guid>https://dev.to/obed_meshach_55c18b915f0f/building-agentmesh-exploring-a-shared-compute-infrastructure-for-ai-workloads-2k88</guid>
      <description>&lt;h1&gt;
  
  
  AgentMesh: Making Underutilized Compute Useful for AI Workloads
&lt;/h1&gt;

&lt;h2&gt;
  
  
  The problem I'm exploring
&lt;/h2&gt;

&lt;p&gt;AI development is becoming more accessible, but the infrastructure required to run AI workloads is still a significant barrier.&lt;/p&gt;

&lt;p&gt;Developers building AI applications often depend on cloud infrastructure, dedicated GPUs, or expensive compute services. For independent developers and early-stage startups, these costs can become difficult to sustain.&lt;/p&gt;

&lt;p&gt;But there's another side to this problem.&lt;/p&gt;

&lt;p&gt;A considerable amount of computing capacity sits underutilized across personal computers, workstations, and independent infrastructure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What if developers could access some of that capacity through a unified platform?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That's the question that led me to build AgentMesh.&lt;/p&gt;

&lt;h2&gt;
  
  
  Introducing AgentMesh
&lt;/h2&gt;

&lt;p&gt;AgentMesh is a platform designed to connect people who need computing power for AI workloads with people who have available computing resources and want to monetize them.&lt;/p&gt;

&lt;p&gt;Rather than requiring every developer to own or rent dedicated infrastructure from a single provider, AgentMesh aims to create a network of independent compute providers.&lt;/p&gt;

&lt;p&gt;🌐 &lt;strong&gt;Website:&lt;/strong&gt; &lt;a href="https://www.agentmeshx.tech/" rel="noopener noreferrer"&gt;agentmeshx.tech&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;p&gt;The architecture revolves around three major components.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Compute providers
&lt;/h3&gt;

&lt;p&gt;Providers contribute available computing resources to the network. These resources can be made available for eligible workloads, with the platform coordinating their availability and usage.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Workload orchestration
&lt;/h3&gt;

&lt;p&gt;The orchestration layer is responsible for managing workloads and matching them with suitable compute resources. Some of the problems I'm working through include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Resource discovery and allocation&lt;/li&gt;
&lt;li&gt;Provider availability monitoring&lt;/li&gt;
&lt;li&gt;Workload execution&lt;/li&gt;
&lt;li&gt;Usage metering&lt;/li&gt;
&lt;li&gt;Failure detection and recovery&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. Customer interface
&lt;/h3&gt;

&lt;p&gt;Developers can access available computing resources and deploy workloads through the platform. The objective is to simplify the experience of accessing distributed compute without requiring developers to manage every provider independently.&lt;/p&gt;

&lt;h2&gt;
  
  
  One challenge: What happens when a node fails?
&lt;/h2&gt;

&lt;p&gt;This is one of the more interesting engineering problems.&lt;/p&gt;

&lt;p&gt;Imagine a customer running a workload on &lt;strong&gt;Provider A&lt;/strong&gt;. Suddenly, Provider A goes offline.&lt;/p&gt;

&lt;p&gt;A naive implementation would simply terminate the workload and leave the customer to figure out what happened.&lt;/p&gt;

&lt;p&gt;I'm exploring a more resilient approach:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Detect that the active node has become unavailable.&lt;/li&gt;
&lt;li&gt;Verify the customer's remaining usable credits.&lt;/li&gt;
&lt;li&gt;Identify another suitable provider.&lt;/li&gt;
&lt;li&gt;Reinitialize the workload on the replacement node.&lt;/li&gt;
&lt;li&gt;Continue usage tracking under the applicable pricing rules.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Of course, this requires careful handling of workload state, resource compatibility, billing, and recovery semantics.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;A node switch doesn't automatically mean an application can resume from exactly where it stopped. Stateful workloads need checkpointing or another recovery mechanism.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That's an important part of the engineering challenge.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bigger picture
&lt;/h2&gt;

&lt;p&gt;I don't think access to AI infrastructure should be limited to organizations that can afford to build or rent entire compute environments.&lt;/p&gt;

&lt;p&gt;There is an opportunity to make underutilized computing resources more useful while giving developers more options for running their workloads.&lt;/p&gt;

&lt;p&gt;That's what I'm exploring with AgentMesh.&lt;/p&gt;

&lt;h2&gt;
  
  
  Let's connect
&lt;/h2&gt;

&lt;p&gt;I'm still early in the journey, and I'm interested in connecting with developers working on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Distributed systems&lt;/li&gt;
&lt;li&gt;AI infrastructure&lt;/li&gt;
&lt;li&gt;Container orchestration&lt;/li&gt;
&lt;li&gt;GPU scheduling&lt;/li&gt;
&lt;li&gt;Workload isolation and security&lt;/li&gt;
&lt;li&gt;Compute marketplaces&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you're interested in the problem, I'd appreciate your thoughts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I'd especially love to hear what you think the biggest technical obstacle to making this reliable would be.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;🔗 &lt;strong&gt;Project:&lt;/strong&gt; &lt;a href="https://www.agentmeshx.tech/" rel="noopener noreferrer"&gt;agentmeshx.tech&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>opensource</category>
      <category>startup</category>
      <category>nvidia</category>
    </item>
    <item>
      <title>AgentMesh: Let Idle Computers Run Your AI Models While Everyone Takes It Easy.</title>
      <dc:creator>Obed Meshach</dc:creator>
      <pubDate>Sat, 24 Oct 2026 04:18:33 +0000</pubDate>
      <link>https://dev.to/obed_meshach_55c18b915f0f/agentmesh-let-idle-computers-run-your-ai-models-while-everyone-takes-it-easy-3b6d</link>
      <guid>https://dev.to/obed_meshach_55c18b915f0f/agentmesh-let-idle-computers-run-your-ai-models-while-everyone-takes-it-easy-3b6d</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week3-2026-10-19"&gt;Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;Most computers spend their day the way a sloth does: switched on, barely moving, conserving energy. Meanwhile, developers who want to run an AI model have to buy a GPU, rent a cloud instance, or babysit a server.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AgentMesh&lt;/strong&gt; connects those two groups so that both can do less.&lt;/p&gt;

&lt;p&gt;It is an open-source platform that runs open-weight AI models on computers contributed by independent providers and exposes each deployment through an OpenAI-compatible API.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Developers get to be lazy.&lt;/strong&gt; Pick a model, click deploy, and call it with the OpenAI client you already use. AgentMesh finds a machine with enough capacity, downloads and verifies the model, runs a test generation, and keeps it alive. If a node goes offline, the deployment moves to another one with the same ID, endpoint and keys. No servers to manage, no 3 a.m. restarts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Providers get to be lazier.&lt;/strong&gt; Install a worker, set CPU, memory and disk limits and availability hours once, and walk away. The worker makes outbound connections only, so there are no ports to open. The machine serves models while it would otherwise sit idle, and the provider earns a share of every charge.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Live app: &lt;a href="https://agent-mesh-ten.vercel.app" rel="noopener noreferrer"&gt;https://agent-mesh-ten.vercel.app&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Docs: &lt;a href="https://agent-mesh-ten.vercel.app/docs" rel="noopener noreferrer"&gt;https://agent-mesh-ten.vercel.app/docs&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Calling a deployed model takes only your existing OpenAI client:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;os&lt;/span&gt;
&lt;span class="kn"&gt;from&lt;/span&gt; &lt;span class="n"&gt;openai&lt;/span&gt; &lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;OpenAI&lt;/span&gt;

&lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;OpenAI&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;base_url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;https://agentmesh-riuz.onrender.com/api/v1/deployments/&amp;lt;id&amp;gt;/v1&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;os&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;environ&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;AGENTMESH_API_KEY&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;reply&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;chat&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;completions&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;qwen2.5:0.5b&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;role&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;user&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;content&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Summarise this ticket&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;}],&lt;/span&gt;
    &lt;span class="n"&gt;stream&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="bp"&gt;True&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/meshach5667" rel="noopener noreferrer"&gt;
        meshach5667
      &lt;/a&gt; / &lt;a href="https://github.com/meshach5667/AgentMeshh" rel="noopener noreferrer"&gt;
        AgentMeshh
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;AgentMesh&lt;/h1&gt;
&lt;/div&gt;

&lt;p&gt;AgentMesh lets developers deploy open-weight AI models on computers contributed by independent providers and
call them through an OpenAI-compatible API. Workloads run inside resource limits on the provider's machine; the
provider can see the data a workload handles
Billing is prepaid, with Paystack top-ups and provider payouts. These run in Paystack test mode and have not
yet been exercised against Paystack's live API.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Documentation&lt;/h2&gt;
&lt;/div&gt;
&lt;p&gt;The full documentation is in the dashboard at &lt;a href="https://agent-mesh-ten.vercel.app/docs" rel="nofollow noopener noreferrer"&gt;agent-mesh-ten.vercel.app/docs&lt;/a&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://agent-mesh-ten.vercel.app/docs/getting-started" rel="nofollow noopener noreferrer"&gt;Getting started&lt;/a&gt;: roles, accounts, and what works today&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://agent-mesh-ten.vercel.app/docs/customers" rel="nofollow noopener noreferrer"&gt;Customer guide&lt;/a&gt;: deploy, call, and pay for models&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://agent-mesh-ten.vercel.app/docs/providers" rel="nofollow noopener noreferrer"&gt;Provider guide&lt;/a&gt;: install the worker and manage machines&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://agent-mesh-ten.vercel.app/docs/api" rel="nofollow noopener noreferrer"&gt;API reference&lt;/a&gt;: authentication, deployments, inference, errors&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://agent-mesh-ten.vercel.app/docs/operators" rel="nofollow noopener noreferrer"&gt;Operators &amp;amp; self-hosting&lt;/a&gt; and &lt;a href="https://agent-mesh-ten.vercel.app/docs/security" rel="nofollow noopener noreferrer"&gt;Security &amp;amp; limitations&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The Markdown files in &lt;a href="https://github.com/meshach5667/AgentMeshh/docs/" rel="noopener noreferrer"&gt;docs/&lt;/a&gt; hold the same material in more depth.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Prerequisites&lt;/h2&gt;
&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;Python 3.12+&lt;/li&gt;
&lt;li&gt;Node.js 20+&lt;/li&gt;
&lt;li&gt;Docker &amp;amp; Docker Compose&lt;/li&gt;
&lt;li&gt;PostgreSQL 16&lt;/li&gt;
&lt;li&gt;Redis 7&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Quick Start (Development)&lt;/h2&gt;

&lt;/div&gt;
&lt;ol&gt;
&lt;li&gt;Clone the repository&lt;/li&gt;
&lt;li&gt;Copy environment variables
&lt;div class="highlight highlight-source-shell notranslate position-relative overflow-auto js-code-highlight"&gt;…
&lt;/div&gt;
&lt;/li&gt;
&lt;/ol&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/meshach5667/AgentMeshh" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;AgentMesh has three parts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Control plane&lt;/strong&gt; (API deployed on Render, dashboard on Vercel): authentication, scheduling, capacity reservation, health checks, scoped API keys, per-request usage metering, prepaid billing and an audit log. Provider workers connect outbound to the Render service, so no provider ever has to open a port.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Provider worker&lt;/strong&gt;: a Docker worker or an installable agent for Linux and macOS. It enforces the provider's resource limits and supports pause, drain and availability schedules.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Model runtimes&lt;/strong&gt;: Ollama and llama.cpp serve the models. vLLM support for GPU nodes is built but not yet verified on real GPU hardware.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When a developer deploys a model, the scheduler reserves CPU, memory and, where available, GPU capacity on a node that fits. If no node fits, it explains why. The worker pulls the model, checks the weights against a pinned digest, and runs a real test generation. Only then does the endpoint go live with chat, completions and streaming.&lt;/p&gt;

&lt;p&gt;Small models such as Qwen2.5 0.5B and SmolLM2 run comfortably on ordinary CPU machines. That is exactly the kind of hardware sitting idle on desks and in dorm rooms.&lt;/p&gt;

&lt;h3&gt;
  
  
  Coming next: a deployment agent for maximum laziness
&lt;/h3&gt;

&lt;p&gt;Developers will describe what they want in plain language, such as "a small chat model for 24 hours within my budget," and set limits on spend, duration, hardware and recovery attempts. Gemma 4, running locally through Ollama on an internal inference machine, will turn that request into a structured deployment plan and help diagnose failures.&lt;/p&gt;

&lt;p&gt;The model only proposes. Every action with consequences, including pricing, wallet checks, node selection, capacity reservation and stopping a deployment, runs in the control plane's own code, and every limit is enforced in code rather than in the prompt. If the inference machine goes offline, requests wait in a queue, and running deployments, billing and spend limits keep working without the model.&lt;/p&gt;

&lt;p&gt;The adapter, configuration and tests are in the repository, but the agent is not live for users yet. Its inference machine is still being configured, and the end-to-end flow has so far been tested with scripted model answers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;AgentMesh is impossible with closed models.&lt;/p&gt;

&lt;p&gt;A closed model lives behind its vendor's API. You cannot ship its weights to a volunteer's laptop, verify them, or run them on hardware the vendor doesn't control. Open-weight models make every part of AgentMesh possible:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Any machine can serve.&lt;/strong&gt; Because the weights are public, a community laptop in Abuja can run the same model as a data-centre GPU, at a smaller scale.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verification is real.&lt;/strong&gt; Weights are pinned to exact versions and checked by digest, so you know exactly which model answered your request.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nothing is locked in.&lt;/strong&gt; Developers can swap models freely, and anyone can self-host the entire network using the operator guide.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open runtimes do the heavy lifting.&lt;/strong&gt; Ollama and llama.cpp make CPU inference practical, which is what lets ordinary idle computers join the network at all.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Even the agent stays open.&lt;/strong&gt; The planned deployment agent runs Gemma 4 locally, so planning doesn't depend on a paid closed API, and the model can be swapped with a single configuration change.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;An honest trade-off.&lt;/strong&gt; Distributed compute is not private compute. A provider can see the model and every prompt and response their node handles. Container isolation protects the provider's machine, not your data. AgentMesh is built for experimentation, prototyping and non-sensitive workloads. Confidential computing is on the roadmap but not available today.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Current status:&lt;/strong&gt; AgentMesh is in open beta. Deployment, failover, API keys, metering, dashboards and provider workers all work today. Billing runs in Paystack test mode, and no price list has been published yet, so usage is measured but not charged.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Render.&lt;/strong&gt; The AgentMesh control plane runs on Render at &lt;code&gt;agentmesh-riuz.onrender.com&lt;/code&gt;. It handles authentication, scheduling, capacity reservation, health checks, API keys, usage metering, billing and the audit log. Every OpenAI-compatible request passes through this Render-hosted gateway before it reaches a provider node.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Gemma.&lt;/strong&gt; Gemma 4 is the reasoning model behind the AgentMesh deployment agent. It runs locally through Ollama on an internal inference machine and turns plain-language deployment requests into structured plans. The integration includes a dedicated adapter, a hardware &lt;code&gt;doctor&lt;/code&gt; check, configuration for &lt;code&gt;gemma4:e2b-it-qat&lt;/code&gt; and &lt;code&gt;gemma4:e4b-it-qat&lt;/code&gt;, and tests. The agent is not live for users yet: its inference machine is still being configured, and the end-to-end flow has been tested with scripted model answers.&lt;/p&gt;

&lt;p&gt;Thanks for reading! I'd love to hear from developers working on open-source AI and distributed systems: how can we make compute more accessible without compromising reliability, security or performance?&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>opensource</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
