Partner offer catalog for buying, piloting, and productizing AI security.
Select the partner offer by buyer type, pressure, duration, inputs, deliverables, success criteria, commercial next step, and relevant partner route. Internal SKU identifiers are secondary.
Catalog filters
Filter by the partner you are: product company, scanner provider, offensive platform, MSSP, consultancy, reseller, training platform, or technology alliance.
Product Company
OEM Engine Pilot and Technology Integration Review.
Scanner Provider
Scanner OEM Feasibility Sprint and OEM Engine Pilot.
Offensive Platform
Offensive Platform APC Pilot and Technology Integration Review.
MSSP
MSSP Service Launch Pilot and AI Security Evidence Retainer.
Consultancy
Consulting Practice Launch and Private-Label Assessment Pilot.
Reseller
Reseller application, approved offer catalog, and opportunity registration.
Training Platform
Workforce Platform Pilot and Workforce White-Label Productization.
Technology Alliance
Technology Integration Review and Native Contract Request Checklist.
Buyer-facing partner offers
A buyer should see the offer and outcome first. Registry-backed SKU details can support operations after fit is clear.
Scanner OEM Feasibility Sprint
Who it is for: Scanner Provider. Pressure solved: Customers are asking for AI-native coverage, but the invocation and output contract need validation before productization. Duration: 2 weeks. Inputs: Sample finding model, scanner workflow, severity model, supported output formats, and representative non-sensitive target. Deliverables: Invocation plan, output mapping, fixture notes, feasibility decision, and pilot SOW. Success criteria: The partner can make a defensible go/no-go productization decision. Commercial note: Discuss an OEM feasibility sprint.
Offensive Platform APC Pilot
Who it is for: Offensive Platform. Pressure solved: The partner wants attack-path context, independent validation, and remediation chokepoints without replacing its attack engine. Duration: Scoped pilot. Inputs: Representative attack trace, target class, validation workflow, evidence boundary, and desired remediation output. Deliverables: APC mapping, evidence-qualified path outputs, support boundary, and launch criteria. Success criteria: The platform can show a useful attack-to-remediation loop using target-, environment-, or system-specific evidence. Commercial note: Scope an APC pilot.
OEM Engine Pilot
Who it is for: Product Company. Pressure solved: Add differentiated AI security capability inside an existing product without rebuilding the engine. Duration: 30 days. Inputs: Representative target, invocation path, output requirements, deployment boundary, and commercial packaging hypothesis. Deliverables: Working pilot, structured outputs, evidence package, license path, and production-readiness notes. Success criteria: The partner can present SecEng outputs inside its own product or service workflow. Commercial note: Request the OEM Pilot Packet.
MSSP Service Launch Pilot
Who it is for: MSSP. Pressure solved: Launch recurring AI security services with a repeatable catalog, evidence model, and support boundary. Duration: First customer or test-customer cycle. Inputs: Service scope, customer profile, delivery cadence, report path, account model, and escalation needs. Deliverables: Service catalog, customer-facing report, evidence workflow, enablement plan, and expansion criteria. Success criteria: The MSSP can repeat the service with clear ownership and renewal logic. Commercial note: Request the MSSP Service Catalog.
Consulting Practice Launch
Who it is for: Consultancy. Pressure solved: Build a profitable AI security practice without recreating methodology, tooling, templates, QA, and evidence structures. Duration: Launch sprint plus initial engagements. Inputs: Target clients, delivery team, current methods, sales motion, and desired service catalog. Deliverables: Service catalog, scoping questionnaire, proposal language, SOW templates, report templates, QA checklist, and escalation rules. Success criteria: The consultancy has a repeatable practice package ready for first engagements. Commercial note: Request the AI Security Practice Launch Pack.
Private-Label Assessment Pilot
Who it is for: Consultancy. Pressure solved: Deliver SecEng-enabled professional services under a client-facing partner brand while preserving evidence integrity. Duration: Scoped client or internal pilot. Inputs: Target assessment, brand requirements, report wrapper needs, evidence boundary, and QA requirements. Deliverables: Partner-branded report wrapper, evidence package, delivery workflow, QA model, and attribution boundaries. Success criteria: The partner can deliver a branded service without misrepresenting SecEng IP or altering technical evidence. Commercial note: Scope a Private-Label Assessment Pilot.
Workforce Platform Pilot
Who it is for: Training Platform. Pressure solved: Add employer-legible AI security readiness to an existing learning platform or cyber range. Duration: Cohort or platform pilot. Inputs: Target roles, learner population, desired scoring, content surfaces, and reporting requirements. Deliverables: Role mapping, assessment or lab package, readiness report, and platform packaging recommendation. Success criteria: Learners and administrators can see role-aligned readiness evidence inside the partner workflow. Commercial note: $25k–$40k.
Workforce White-Label Productization
Who it is for: Training Platform. Pressure solved: Package SecEng workforce intelligence behind the partner's own platform identity and commercial model. Duration: 8-12 weeks. Inputs: Product packaging, LMS constraints, taxonomy needs, entitlement model, and support obligations. Deliverables: White-label workforce package, content boundaries, readiness scoring model, entitlement plan, and release coordination. Success criteria: The partner can launch a branded workforce readiness product with clear IP, support, and update boundaries. Commercial note: $180k–$350k+.
Technology Integration Review
Who it is for: Technology Alliance. Pressure solved: Validate whether a native product integration is technically and commercially supportable before joint GTM. Duration: Scoped technical review. Inputs: Representative API object, finding, trace, schema, content contract, test-tenant access where available, and secret-boundary requirements. Deliverables: Build/Validate/Launch plan, adapter maturity rating, contract gaps, support ownership, and joint-solution next step. Success criteria: Both parties know what is public, projected, fixture validated, native partner confirmed, or live partner validated. Commercial note: Propose a Technology Integration.
Capability to listing
From a partner capability to a transactable marketplace listing: the steps that turn a proven module into something a buyer can purchase.
From partner capability to transactable listing.
A marketplace offer moves through packaging, validation, listing, discovery, commercial action, provisioning, and delivery.
A marketplace offer moves through packaging, validation, listing, discovery, commercial action, provisioning, and delivery.
A packaging and fulfillment path - not a claim of an existing marketplace relationship.
Partner Marketplace defines how approved SecEng capabilities or services may be packaged, procured, fulfilled, or distributed through a partner-controlled channel. A route, listing template, or technical package does not imply acceptance by any third-party marketplace.
Packaged offer
A bounded SecEng service or capability is described with approved scope, price structure, fulfillment, and claim language.
Private offer
Commercial terms are issued for a specific buyer, account, or partner motion.
Connector distribution
An approved connector, adapter, or package is distributed under defined version, support, and licensing terms.
Partner fulfillment
The partner sells or delivers the approved offer while responsibilities and customer ownership remain contractually defined.
No unvalidated marketplace claims
Do not describe a third-party listing, marketplace relationship, procurement availability, or platform certification unless it is live, validated, and approved for public use.
SKUs still matter, but they should not lead the story
Commercial operations can keep registry-backed identifiers while the public page leads with recognizable offers and outcomes.
OEM Pilot
Thirty-day OEM integration pilot for scanner providers and platform partners.
OEM Base Monthly License
Base monthly license for partners embedding or invoking SecEng capabilities.
MSSP Base Monthly License
Base license for managed security providers offering AI security services.
Consultancy Private-Label License
Private-label assessment and report delivery for consulting partners.
Academy Content License
License Academy, AIPSA, lab, flash-card, SCORM, and related training assets.
Enterprise Site License
Negotiated enterprise-wide access to SecEng capabilities, workers, evidence, and Academy assets.
Listing pilot
One listing and fulfillment pilot proves the transaction, entitlement, and delivery loop before broad marketplace publishing.
One listing and fulfillment pilot.
A bounded pilot proves the listing metadata, commercial action, provisioning, delivery, usage signal, and renewal path for one offer.
A bounded pilot proves the listing metadata, commercial action, provisioning, delivery, usage signal, and renewal path for one offer.
Every offer states its availability before you scope it
Available now, scoped engagement, licensed capability, pilot available, partner validation required, or planned - match the CTA to what you can actually get today.