<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pages on VPN Works</title>
    <link>https://vpnw.com/pages/</link>
    <description>Recent content in Pages on VPN Works</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://vpnw.com/pages/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>About</title>
      <link>https://vpnw.com/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/about/</guid>
      <description>&lt;p&gt;VPN Works is a project at an early stage. Its engine works on Linux, a live demo replays it and runs its policy engine in your browser, and the next step is real agents on more systems. This site shows where the project stands, gaps included.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-the-project-exists&#34;&gt;Why the Project Exists&lt;/h2&gt;&#xA;&lt;p&gt;AI agents now run code and call APIs on their own. They run on developer laptops, in CI and on servers, usually with all the network access of the machine they run on. That is a lot of access for a program that takes instructions from whatever text it reads.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Contact</title>
      <link>https://vpnw.com/contact/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/contact/</guid>
      <description>&lt;p&gt;The project would like to hear from:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Teams running AI agents,&lt;/strong&gt; coding agents in particular, who would like to try the Beta on their own machines or in CI.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Security and platform engineers&lt;/strong&gt; with an agent, a tool or a network setup the project should test.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Anyone&lt;/strong&gt; with a question about the engine, the demo or the figures on this site.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Write to &lt;strong&gt;&lt;a href=&#34;mailto:info@vpnw.com&#34;&gt;info@vpnw.com&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;If you are writing about a setup, it helps to mention the agent, where it runs (a laptop, CI or a server), the operating system and distribution, what the agent needs to reach, and how your network is organized: an office VPN, a proxy, fixed egress addresses.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Live Demo</title>
      <link>https://vpnw.com/demo/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/demo/</guid>
      <description>&lt;p&gt;A coding agent runs a task whose task file hides an instruction to send a deploy token to an attacker. Six steps show what VPN Works does about it. Every line in the terminal below comes from real runs of the Alpha on Linux and is replayed here, and the decisions in the two panels under it are made by the Alpha&amp;rsquo;s own policy engine, running in your browser. There is nothing to sign up for or install, and nothing you do here leaves this page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Roadmap</title>
      <link>https://vpnw.com/roadmap/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/roadmap/</guid>
      <description>&lt;p&gt;The Alpha proves the design on one Linux machine, with stand-ins for the agent and the network. What comes next puts real agents under vpnw on more systems, then leads to a first release, and after that to the parts a company would pay for. Durations are estimates, and what real agents turn up could stretch them.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://vpnw.com/images/roadmap.png&#34; alt=&#34;Two lanes. The engine: Alpha, done, a working engine with run, trace, guard and learn on Linux; Beta, next, about 14 weeks for WireGuard, the file-system layer, macOS, packages and agent recipes; toward v1.0, 6 to 9 months of product work (estimate) for workspaces, a frozen event format, an outside review and pilots; v1.0, the first release, with the command line, policy files and events frozen. After v1.0, what companies would pay for: team policies, audit retention, managed exits and fleet configuration.&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Alpha</title>
      <link>https://vpnw.com/alpha/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/alpha/</guid>
      <description>&lt;p&gt;The Alpha is the working prototype of the VPN Works engine: one Go program called vpnw, its tests, a few tools and a demo. On Linux it runs a program in a sealed sandbox whose only way out is vpnw. Each connection is decided by a policy, sent down the path you chose and recorded.&lt;/p&gt;&#xA;&lt;p&gt;Everything so far ran on one Linux machine, a virtual machine with two CPUs. The demo&amp;rsquo;s agent, servers, office and attacker are stand-ins in a private network namespace. The engine also compiles for arm64 Linux and for macOS, but neither build has run yet. On macOS it is meant to route and trace programs that honor proxy settings; it can&amp;rsquo;t seal them. No real coding agent has run under vpnw so far. That is the job of the &lt;a href=&#34;https://vpnw.com/roadmap/&#34;&gt;Beta&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
