For partners

Three partnership types. One substrate.

Model providers, integration partners, and channel partners each get different shapes. Find the section that fits you.

Shared context

What Raptor is.

Raptor is a deterministic governance layer for AI applications. Multi-provider by design. Currently:

  • Phase B-2 closed — classifier shadow infrastructure shipped; production activation pending operator action
  • Phase B-1 validated multi-provider parity — Llama 3.3 70B and Claude Sonnet both at 100% accuracy on a 20-scenario truth set, ~78% lower cost on open-weight
  • 9-unit UI design system implemented and deployed in Preact
  • 85 documented API routes, TypeScript SDK generated, MCP server functional
  • First external prospect profile defined; no prospect deployed yet
  • One founder + AI senior staff; HITS is an SDVOSB based in Maryland
Section 1

Model provider partnerships.

Who: Anthropic, OpenAI, Together AI, future open-weight or specialized model providers.

Partnership shape

Raptor's multi-provider architecture means we're not competing for any single model provider's customers — we're a value-add layer on top of whoever the customer is already using. The natural partnership shape is co-sell or value-add for your enterprise/regulated-industry customers who need governance, audit, or compliance capabilities your platform doesn't natively provide.

What we'd want

  • Stable model access and predictable pricing
  • Technical signal-up on roadmap changes
  • Co-sell motion on regulated buyers
  • Public reference as first-class Provider

What we offer in return

  • Substrate adds enterprise/regulated value to your model
  • Empirical performance data from cross-model eval
  • First-mover positioning in deterministic-AI category
What we are not offering: Co-marketing budget. Exclusivity (invalidates multi-provider architecture). Reselling your model.
Section 2

Integration partnerships.

Who: MCP-client vendors, identity providers beyond Clerk, observability vendors, agent-framework maintainers, eval/testing platforms, adjacent governance-infrastructure tools.

Partnership shape

Integration partnerships are joint feature opportunities. The partnership shape is mutual API integration, joint roadmap items, and co-marketing of the integration to mutual customers.

Concrete shapes near-term

  • MCP-client integration certification (once Raptor's MCP server publishes to a public registry)
  • Identity provider beyond Clerk (driven by first prospect's enterprise identity requirements)
  • Observability visualization (Phase B-2 shadow window data; a vendor that wants to visualize agreement-rate analytics is a near-term opportunity)

What we'd want

  • Documented integration paths maintained jointly
  • Joint customer support at integration seam
  • Roadmap coordination on integration surface
  • Co-marketing of the integration to mutual customers

What we offer in return

  • Engineering bandwidth proportional to mutual customer demand
  • Joint customer support at our end of the seam
  • Reference customer access as prospect base grows
  • MCP server functional today — integration technically possible immediately
What we are not offering: Exclusive integration. Free engineering with no clear mutual customer. Branding agreements at this stage.
Section 3

Channel partnerships.

Who: Consultancies and system integrators with practices in regulated industries, vertical specialists, managed-service providers that deploy AI infrastructure on behalf of clients.

Partnership shape

Your firm deploys Raptor for your clients, with training, technical enablement, and professional-services economics that work for both sides.

What we'd want

  • Active practice in a regulated industry with current AI clients
  • Technical capability to deploy without our team writing every line
  • Joint deal pursuit
  • Feedback loop from client deployments to roadmap

What we offer in return

  • Technical enablement, direct engineering access
  • Professional-services economics that scale with your firm
  • First-mover positioning in deterministic-AI category
  • Engineering responsiveness to client deployment issues
  • SDVOSB set-aside access for defense/government channels. Set-aside contracting paths non-SDVOSB substrates cannot access.
What we are not offering: Formal channel program with tiers and quotas. White-label or branded versions. Procurement-ready enterprise sales motion.

Near-term: We're not actively recruiting channel partners. The right shape near-term is partner-first deployments — your client, your engagement, Raptor as the substrate, our team engaged enough to make sure it works.

How partnerships start

A conversation. Not a partnership track.

For all three partnership types: a direct conversation with the founder. No procurement track. No partnership-of-the-month program.

If you reference which partnership type you're considering (model / integration / channel), the conversation routes faster.

info@harpyits.com