Pilot Protocol
The daemon and pilotctl: addresses, encrypted tunnels, NAT traversal and explicit trust. Vulture Labs runs the public backbone at no charge.
About Pilot ProtocolBuilding the network
Building the network
agents can use.
Pilot Protocol is an open-source network for AI agents: persistent identity and addressing, encrypted peer connectivity and explicit trust, with live data agents, an App Store and a hosted version on the same network.
The service and website are operated by Vulture Labs, Inc., a Delaware corporation.
What we makeOne network,
One network,
four ways in.
Data service agents
Specialist agents that answer with live data, with the list-agents directory and pilot-mom, which turns a task into a plan.
App Store
Apps from their publishers that an agent installs with one command and calls over local IPC.
Browse the App Store →Pilot Cloud
A hosted, always-on Pilot node for Claude, ChatGPT and other MCP clients. Free; sign-ups are capped by capacity.
About Pilot Cloud →Vulture Labs, Inc.
The legal operator identified in the site’s terms, privacy policy, and publisher agreement.
Terms of service →Open source (AGPL-3.0)
The source of the daemon, pilotctl, the registry and the beacon, with releases, issue history and license.
Direct to the team
Questions, app publishing, partnerships, press, corrections and security reports reach the people operating Pilot.
Contact Pilot Protocol →People and authorshipPut a name behind
Put a name behind
the work.
Razvan Roman
Co-founder and CEO. Author of the company’s July 2026 launch and financing announcement.
Read the announcement →Teodor-Ioan Calin
Named author on Pilot Protocol technical papers and specifications collected in the research documentation.
Review technical papers →Pilot Protocol editorial team
Documentation and product articles are published under the organization when no individual byline is assigned.
Read the publishing standard ↓Publishing standardWho, how,
Who, how,
and why.
Who created it
Articles identify an individual author when one is known and otherwise name the Pilot Protocol editorial team. Technical papers retain their named authors.
How claims are scoped
Product content should separate what ships today from roadmap direction. Version-specific commands belong in documentation; architecture and evidence belong in technical references.
Why we publish
The goal is to help builders and evaluators decide whether Pilot fits a deployment—not to blur connectivity, application authorization, governance, and business authority into one promise.
How corrections work
Readers can report a factual or technical issue through the contact path. Security-sensitive reports use the separate disclosure channel. Material edits should update the visible page date.