Skip to content
Brevor.
Brevor Tech / How we are organized

HowBrevorisorganized.

Brevor Tech operates as a focused holding company. We run lean. We list role titles, not names — our operators do their best work without a personal brand.

HOW WE OPERATE

Brevor Tech is a holding company. It operates eleven Bridge-branded products, an applied research arm, and the infrastructure that connects them. The holding-company posture is deliberate: each product team operates with autonomy on roadmap and engineering, while sharing routing, context, and audit primitives at the platform layer.

The applied research arm — Brevor Research — publishes openly. Product code is closed. The separation lets us contribute findings to the AI Safety Index and the broader behavioral-AI research community without exposing customer-deployment details.

Kyros Holding Inc. acquired Brevor Tech in 2017. Kyros operates with a 10+ year hold horizon and does not direct product roadmap. The relationship is capital and governance, not operational.

OPERATING PRINCIPLES

Six principles, applied daily.

01

We list roles, not names.

02

We deploy slowly. We renew quickly.

03

Audit trails are a product, not a footnote.

04

We measure what the customer pays for, not what we want to publish.

05

Behavioral context belongs outside the model.

06

We add operators rarely and intentionally.

LEADERSHIP

Eight operators. Five cities. No names.

Chief Behavioral Officer

Twelve years operating product organizations at the intersection of regulated industries and applied ML. Leads Brevor's strategic direction and the holding-company structure.

Based in New York

Head of Research

Background in interpretable ML and regulatory AI policy. Built Brevor Research from zero and authored the foundational behavioral-context architecture paper in 2019.

Based in San Francisco

Head of Trust & Safety

Eight years in healthcare AI compliance and regulated-industry deployment. Owns the audit-trail spec, the safety review process, and the AI Safety Index contribution.

Based in Miami

Head of Enterprise

Led enterprise-AI go-to-market at two prior infrastructure companies. Joined Brevor to build Bridge Workspace's deployment motion from the first pilot.

Based in New York

Head of Hardware

Hardware-software integration veteran with deployments across consumer and edge environments. Built Bridge Stone's edge-device runtime and the keyboard guardrail layer.

Based in Toronto

Head of Verticals

Operating background in healthcare, financial services, and public-sector technology procurement. Owns the four vertical Bridge products and the cultural-context module roadmap.

Based in Singapore

Head of Engineering

Distributed-systems and low-latency infrastructure background from prior model-serving and edge-compute roles. Owns the routing engine and the Bridge API platform.

Based in San Francisco

Head of Operations

Operations veteran across regulated-industry deployments and incident response. Built Brevor's status, changelog, and operational-cadence systems from the ground up.

Based in Miami

WHERE WE ARE

Five offices. One operating company.

SFNYTORMIASGP
San Francisco
2
operating roles
New York
2
operating roles
Toronto
1
operating role
Miami
2
operating roles
Singapore
1
operating role
INVESTOR

Brevor Tech is backed by Kyros Holding Inc.

Kyros Holding Inc. is a long-horizon technology holding company. It invests across infrastructure, applied AI, and regulated-industries technology with a 10+ year hold horizon.

Kyros acquired Brevor Tech in 2017, two years after Brevor's founding. The acquisition was structured to preserve Brevor's operating autonomy: Kyros holds the capital and governance relationship; Brevor's leadership directs product strategy, hiring, and deployment.

Kyros does not direct Brevor's roadmap. Kyros does not participate in customer scoping. The relationship is intentionally narrow.

The long hold horizon is the relevant detail for customers. Brevor's deployments are designed to operate for years inside regulated environments. Our investor structure matches.

Talk with the team that runs the layer.

Talk to sales