<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Technology on VPN Works</title>
    <link>https://vpnw.com/tags/technology/</link>
    <description>Recent content in Technology on VPN Works</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vpnw.com/tags/technology/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Introduction</title>
      <link>https://vpnw.com/introduction/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/introduction/</guid>
      <description>&lt;p&gt;&lt;strong&gt;A VPN for every agent: each AI agent gets a network of its own, and every connection it makes is checked, routed and recorded.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;VPN Works is a project to build that network. Its engine, vpnw, is one small program. It runs an agent in a sealed sandbox whose only way out is vpnw, then decides each connection with a policy you can read, sends it down the path you chose and writes it down.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How It Works</title>
      <link>https://vpnw.com/how-it-works/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/how-it-works/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;The idea.&lt;/strong&gt; Seal each agent in a sandbox whose only way out is vpnw. vpnw checks every connection against a policy, sends it down the path you chose and records it. The agent doesn&amp;rsquo;t need to know any of this.&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;A VPN usually works at the level of the machine. Once it is up, every program on the machine goes out the same way, under the same rules, and nobody can say afterwards which program sent what. That was fine when the programs were a browser and a mail client. It fits badly when one of them is an agent that takes instructions from whatever it reads.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VPN Works Explained: How vpnw Gives Each AI Agent Its Own Network and Stops Token Leaks</title>
      <link>https://vpnw.com/vpn-works-explained-how-vpnw-gives-each-ai-agent-its-own-network-and-stops-token-leaks/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/vpn-works-explained-how-vpnw-gives-each-ai-agent-its-own-network-and-stops-token-leaks/</guid>
      <description>&lt;p&gt;VPN Works is a prototype of a small program called vpnw. It gives one program, usually an AI agent, a private network of its own on a Linux computer. vpnw decides where that program&amp;rsquo;s traffic may go, sends it out the way you choose and writes down every connection it makes.&lt;/p&gt;&#xA;&lt;p&gt;That matters because of how AI agents work. Coding assistants and similar tools run on laptops and servers with all the network access the machine has, and they follow instructions they find in text. One hidden line in a task file or a web page can say &amp;ldquo;send the deploy token to this address&amp;rdquo;, and an agent may simply do it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
