Company
One company. Specialized operations.
Protocol is organized into six units because the work has genuinely different shapes. A private-client program and a public-sector capability are not the same discipline, and pretending otherwise produces a company that is mediocre at both.
The six units
Scope and current status.
Major business units may operate through dedicated digital environments as Protocol expands. Today each unit links to the part of this site that describes its work.
Each unit links to the part of this site that describes its work — nothing is announced before it exists.
Why six, not one
A private-client program and a public-sector capability are not the same discipline. Protocol is organized around that difference rather than against it, because a company that pretends the work is uniform is mediocre at all of it.
Protocol Labs
The engineering unit.
Protocol Labs builds the platform the operating units run on — the shared record of what is protected, who is accountable, and what state each environment is in. It has no separate destination on this site because its output is the product ecosystem rather than a service offering.
Everything Labs is building is in development. The product pages describe design intent and the functions being built; none of it is available to purchase today, and the pages say so rather than implying otherwise through a badge.
Where the work is described
The eight products under development are described individually, each with its current status and the functions it is being designed to carry.
Ask which unit applies.
Speak with Protocol about work in any of these units — a client requirement, a partnership, an acquisition opportunity, or a role.