PARTNERS

Add selected Workbench capabilities through bounded OEM and partner integrations

Deliverablesdeliverable
deliverable

Partners Hub Ecosystem Figures

Canonical Markdown source for the Partners Hub Ecosystem Figures.

Public sample
Client deliverable
public-sample
System
Partners Hub Ecosystem Figures
Environment
Production pilot

# Partners Hub Ecosystem Figures

HUB-01

The AI Security LLC partner ecosystem.

Different partner types connect through distinct commercial motions while sharing a common capability, evidence, interoperability, and support foundation.

Different partner types connect through distinct commercial motions while sharing a common capability, evidence, interoperability, and support foundation.

Core
AI Security LLC partner foundation
Shared contracts
  • Canonical contracts
  • Evidence and interoperability
  • Partner workspaces
  • Enablement and support
Embed and integrate
OEM and scanner providers • Offensive platforms
Sell and deliver
Resellers • MSSP partners
Brand and distribute
White and private label • Marketplace
Consulting and services
Consulting partners • Delivery teams
Technology and interoperability
Technology partners • Round-trip integrations
HUB-02

Choose the partner motion.

The right program depends on who owns the product and who owns the customer and delivery.

Two-axis selector placing Deliver, Embed, Sell, and Integrate motions by who owns the product and who owns customer and delivery.

AI SECURITY LLC OWNS PRODUCT → PARTNER OWNS PRODUCTAI SECURITY LLC DELIVERS → PARTNER DELIVERSDeliverPartner owns client deliveryAI Security LLC supports technicaldeliveryBest fit: MSSP and consultingEmbedPartner owns product and customerWorkbench capability runs behind itBest fit: OEM and scanner providersSellPartner owns market accessAI Security LLC proves and fulfillsBest fit: resellersIntegrateProducts stay independentContracts and workflows connectBest fit: technology partnersSHARED FOUNDATIONEvery motion rests on canonical contracts, evidence, and support
HUB-03

From first conversation to a supported partner motion.

Every partner path begins with fit and a representative object, then advances through proof, operating-model design, launch, and support.

Every partner path begins with fit and a representative object, then advances through proof, operating-model design, launch, and support.

Program fitSTEP 1Representative objector workflowSTEP 2Bounded technicalproofSTEP 3Operating andcommercial modelSTEP 4Provisioning andenablementSTEP 5Partner launchSTEP 6Support and versioningSTEP 7ExpansionSTEP 8Partner resourcesProvisioned partner workspace • Pilot brief and diagrams • Technicalcontracts and fixtures