For Strategic Partners

Build at protocol scale.

If your roadmap depends on a low-altitude airspace protocol — and you'd rather not build one — VerSky is open to strategic conversations. Licensing terms are designed to be transparent and predictable.

§1 · Paths

Four ways to engage.

The shape of the engagement depends on where you sit in the stack. Pick the one closest to your situation — we'll start from there.

Manufacturers

Embed in the airframe

Drone, eVTOL, and avionics OEMs integrating the protocol natively. Licensing covers protocol implementation and the embedded SDK.

Fleet operators

Operate at scale

Logistics, surveillance, agriculture, infrastructure inspection. Commercial use of the patented protocol across an operating fleet.

Platforms

UTM / deconfliction / flight-planning

Software vendors building services on top of the protocol. Licensing covers redistribution of protocol implementations to customers.

Strategic

Joint roadmap

Multi-product collaborations — co-marketing, joint integration, technology exchanges. Terms by negotiation.

§2 · Access Tiers

Three tiers, clearly separated.

“Open protocol” means three distinct things. We separate them so you know exactly what you're getting at each tier — and what sits behind a licence.

Tier 1

Public Specification

Free

For: Researchers, students, evaluators, journalists

·Filed patent applications (published Aug 2027)
·Whitepaper (v1.0, 23 pages)
·Public protocol documentation
·Canonical wording reference

Read the spec →

Tier 2

Reference Implementation

Gated · request access

For: Engineers building production integrations

·Python reference implementation (MVP)
·Test vectors, conformance fixtures
·Integration support during early-access window
·SDK roadmap visibility

Request SDK access →

Tier 3

Commercial Licence

Terms by class of use

For: Manufacturers, operators, platforms shipping at scale

·Patent licence covering implementation rights
·Per-class terms (manufacturer / operator / platform)
·Standards-aligned renewal terms
·Direct inventor liaison during integration

Open a licence inquiry →

Tier 1 and Tier 2 do not require a commercial licence. Tier 3 covers commercial deployment of the patented protocol at production scale.

§3 · Principles

How licensing is structured.

Final terms are TBD and will be published on the Trust & License page ahead of formal availability. The principles below describe how those terms are being designed.

Transparent

Tiers and engagement paths are public. Commercial terms are scoped by class of use, not negotiated bespoke per company.

Predictable

Multi-year visibility on roadmap, licence renewal, and protocol evolution. Standards bodies need stability.

Non-exclusive

The protocol stays open. Strategic partners get earlier roadmap access — not a moat against others.

Standards-aligned

Licence terms are written to be compatible with future ASTM F38 / ICAO RPAS adoption.

§4 · Coverage Map

Where each product category touches the protocol.

Capabilities below describe which parts of the filed protocol each product category typically intersects. This is a conversation starter, not a claim chart. Formal claim-level mapping is performed under NDA with counsel during scoping calls.

Product Category	Typical Product	P1 Capabilities Touched	P2 Capabilities Touched
Drone / UAV OEMs	Embedded flight controller, altitude-direction encoding firmware	Altitude-direction encoding · hex-grid sub-layer assignment	AACP Layer 1 broadcast · Layer 2 P2P negotiation on-vehicle
eVTOL / UAM Manufacturers	Passenger-class avionics, multi-floor traffic integration	Multi-floor sub-layer math · per-floor capacity · directional banding	Passenger-class precedence in negotiation · uncertainty broadcasting
UTM / Deconfliction Platforms	Server-side traffic management, reservation aggregation	4D reservation primitives · cell-occupancy bookkeeping	Layer 1 aggregation · inter-vehicle prediction comparison
Fleet Operators	Commercial fleet deployment using compliant equipment	Method-use at fleet scale	Method-use at fleet scale
Avionics Suppliers (PX4 / ArduPilot)	Open-source flight controller integrations	Altitude-direction primitive embedding	Reference negotiation + DFR integration
Audit / Logging Infrastructure	Tamper-evident decision-log storage and verification	—	AACP Explainability layer · hash-chain audit-log custody

Not a claim chart: this table identifies protocol capabilities that typically come into play for each product category. It is not a representation of claim coverage and is not an offer. Claim-level scope, infringement analysis, and licence boundaries are determined only by USPTO examination outcomes and the executed licence agreement, under counsel review.

§5 · FAQ

Questions BD and legal teams ask first.

Compiled from real conversations. Click any question to expand — additions welcome from your scoping call.

Licensing

At a conceptual level, Tier 3 is the path for implementing the patented methods at production scale, scoped to a product category (manufacturer / operator / platform). The actual rights, scope, fee structure, and any associated obligations are defined only in the executed licence agreement — nothing on this page constitutes an offer or a grant.

Technical

Process

Nothing in this FAQ is an offer, a binding commitment, or legal advice. Final rights, fees, indemnities, patent commitments, and renewal terms are defined only in the executed licence agreement.

§6 · Process

Four steps from introduction to executed licence.

No long sales motion. The shape is built for technical and legal teams that value clarity — not for procurement gauntlets.

Introduction

A short note about your organisation, your use case, and what success looks like. NDA can be put in place before a second message if needed.

Scoping call

30–60 minutes to align on scope, timeline, and the form of engagement. Held under whatever confidentiality terms you need.

Term sheet

Once scope is clear, a term sheet covering licence type, fees, milestones, and renewal. Drawn from the standard template where applicable.

Execution

Definitive licence agreement. Integration support, technical liaison, and a clear handoff into the engineering relationship.

§7 · Inquire

Open a confidential conversation.

All inquiries are read by the inventor directly. NDAs can be put in place before details are exchanged. Treat the contact form as a sketch — the real conversation starts on the call.

Start a partnership thread Or a standard licence inquiry

PGP key available on request. Spokesperson availability subject to time-zone (ICT, UTC+7).