diff --git a/src/pages/blog/hipaa-compliant-agent-communication.astro b/src/pages/blog/hipaa-compliant-agent-communication.astro index d8978c0..cf6ae75 100644 --- a/src/pages/blog/hipaa-compliant-agent-communication.astro +++ b/src/pages/blog/hipaa-compliant-agent-communication.astro @@ -47,7 +47,7 @@ const bodyContent = `
Healthcare agent transport needs clear technical
Pilot Protocol is a peer-to-peer overlay network. It prefers direct encrypted UDP tunnels, while coordination services handle discovery and NAT traversal. When direct connectivity is unavailable, encrypted relay fallback can add a Pilot-operated intermediary to the data path; the relay forwards ciphertext and does not hold the tunnel key. Pilot Protocol is a peer-to-peer overlay network. It prefers direct encrypted UDP tunnels, while coordination services handle discovery and NAT traversal. When direct connectivity is unavailable, encrypted relay fallback can add a Pilot-operated intermediary to the data path; the relay forwards ciphertext and does not hold the tunnel key. This architecture can reduce the number of systems that handle plaintext. On a direct path, application data moves between the two endpoints without an application broker. Teams still need to account for endpoint software, optional relay paths, app services, logs, backups, and every other component in their own data-flow and vendor review. If you are building with AI agents and have run into the problem of connecting them across different environments, this page explains what Pilot Protocol is, how it works at a high level, and what problems it solves. Is Pilot Protocol a company? Pilot Protocol is an open-source project, not a proprietary platform. The implementation is AGPL-3.0 at github.com/pilot-protocol — a single Go binary with zero external dependencies that you install with one command and run yourself. The SDKs, docs, and app store are part of the same open project, and 243k+ agents and users are on the network. Every mainstream approach to agent communication assumes reachable endpoints. When an agent framework publishes a tool or an endpoint, it typically gives it a URL. Google's A2A protocol publishes Agent Cards with URLs. MCP servers connect over HTTP. LangChain agents call APIs by URL. The entire ecosystem assumes your agent has a publicly reachable HTTP endpoint. Every one of these capabilities ships in a single Go binary. The daemon has zero external dependencies — it uses only the Go standard library. There is no system dependency, no database to run, no runtime to install. Pilot Protocol is an open-source project, not a proprietary platform. The full implementation is AGPL-3.0 and published at github.com/pilot-protocol. You install a single Go binary with one command and run the daemon yourself — the code, the docs, and the SDKs (Go, Python, Node.js, Swift) are all public. That gives you a verifiable answer to "who is behind this?": read the source. You can audit the crypto, the NAT traversal, and the trust handshake, or fork the project and run your own build. Development happens in the open under the pilot-protocol organization, and the app store is part of the same open project — installable capability apps that run as typed IPC services on your own daemon. The network is open to anyone running the daemon. 243k+ agents and users are on Pilot, and joining is just installing the binary and starting it — no shared infrastructure to provision, no account to create. Every agent needs an identity, a way to be reached, and a way to trust other agents. Most agent frameworks stop at the application layer — they define how agents exchange tasks or call tools, but assume the network layer underneath is someone else's problem. Pilot Protocol takes the opposite route: it gives every agent its own networking stack, and that changes what an agent is in the first place. Every agent needs an identity, a way to be reached, and a way to trust other agents. Most agent frameworks stop at the application layer — they define how agents exchange tasks or call tools, but assume the network layer underneath is someone else's problem. Pilot Protocol takes the opposite route: it gives every agent its own networking stack, and that changes what an agent is in the first place. This page covers what makes an agent a Pilot agent: the capabilities that come from running on the overlay network, and how they differ from agents built on standard HTTP infrastructure. If you are evaluating Pilot Protocol for your agent fleet, this is the overview of what your agents gain at the network layer.The Pilot Approach: Minimize Intermediaries in the Data Path
- The Problem: Agents Cannot Reach Each Other
Is Pilot Protocol a Company?
+
+What Problems It Solves
Direct agent-to-agent communication
@@ -164,6 +176,10 @@ const faqItems = [
{
question: "Is Pilot Protocol open source?",
answer: "Yes. The entire implementation is open source under AGPL-3.0. The source code is at github.com/pilot-protocol. The daemon is written in Go with zero external dependencies."
+ },
+ {
+ question: "Is Pilot Protocol a company?",
+ answer: "Pilot Protocol is an open-source project, not a proprietary platform. The implementation is AGPL-3.0 at github.com/pilot-protocol — a single Go binary with zero external dependencies that you install with one command and run yourself. The SDKs, docs, and app store are part of the same open project, and 243k+ agents and users are on the network."
}
];
---
diff --git a/src/pages/learn/what-makes-a-pilot-agent.astro b/src/pages/learn/what-makes-a-pilot-agent.astro
index d514446..c7ba194 100644
--- a/src/pages/learn/what-makes-a-pilot-agent.astro
+++ b/src/pages/learn/what-makes-a-pilot-agent.astro
@@ -1,7 +1,7 @@
---
import BlogLayout from '../../layouts/BlogLayout.astro';
-const bodyContent = `