Commercial

Start with one governed decision, not a platform migration.

The public repository builds trust through architecture, SDK contracts, and reproducible evidence. The first commercial motion is deliberately narrow: one decision workflow, a few enforced controls, and evidence a buyer can inspect. There is no rate card at this stage because fit determines scope.

First engagement

Governed AI Decision Pilot

One existing AI or operational decision workflow, governed end to end, with evidence you can put in front of an auditor.

For teams that already have a decision engine — fraud, AML, sanctions, credit, risk, or an AI-assisted investigation workflow — and need enforceable policy and reconstructable evidence around it without replacing it.

What the pilot covers

  1. Map one decision or event lane end to end, including the systems that participate in the execution path.
  2. Agree on three to five governance controls that must be enforced at execution time.
  3. Connect StreamKernel to the appropriate point in that execution path.
  4. Enforce the agreed controls, fail closed, in the live path.
  5. Produce Governed Event Receipts for the governed executions.
  6. Measure the runtime performance impact against the pre-pilot baseline.
  7. Demonstrate reconstruction of a specific decision from the retained evidence.
  8. Document production-readiness gaps, integration work, and the next decision worth governing.

What it is not. The pilot governs the decision path. It does not replace your fraud platform, AML platform, risk engine, model, LLM gateway, streaming platform, or case-management system, and it does not produce a certification or regulatory authorization.

Scope, duration, and commercial terms are set per engagement after the fit assessment. There is no published rate card at this stage.

Low-friction starts

Smaller starting points, if a pilot is premature.

Each of these ends in something inspectable rather than a follow-up meeting.

Governed Pipeline Assessment

For buyers with one AI or event pipeline who need to know where governance breaks before committing to a pilot.

Output: A short gap map covering enforcement, provenance, cost ceiling, route controls, reconstructability, and the first StreamKernel profile to test.

Proof Replay Demo

For teams that want to inspect evidence before a commercial conversation gets heavy.

Output: A sample Governed Event Receipt plus a replay of a financial-services, PHI-aware, defense, or agentic event path.

Air-Gap Readiness Pilot

For defense, public-sector, healthcare, or regulated enterprise teams that cannot send sensitive event execution to a hosted service.

Output: A scoped runtime deployment with fail-closed enforcement, per-event provenance, local audit evidence, and an exportable proof package.

Packages

Commercial paths by buyer and deployment model.

Each path starts from the deployment shape, evidence needs, and operational risk profile rather than a one-size-fits-all tier.

Evaluation

For technical teams validating the public repo, benchmark suite, and plugin contracts before a deeper commercial review. The goal is to prove the runtime shape, reproduce local baselines, and identify the first buyer scenario worth pursuing.

Production

For enterprises moving StreamKernel from evaluation into internal production use. This path focuses on protected builds, deployment packaging, operational support, and destination-specific readiness.

OEM / Embedded

For ISVs embedding StreamKernel into a product or appliance. It covers redistribution rights, plugin boundaries, private builds, and support expectations around customer-owned deployments.

Managed Service

For vendors operating StreamKernel-backed services on behalf of customers. The conversation centers on support, managed-service rights, isolation, upgrade cadence, and evidence handoff.

Government / Regulated

For defense, public-sector, healthcare, agentic AI, and regulated finance teams with air-gapped or compliance-heavy environments. This path emphasizes auditable inference, policy enforcement, private support, and controlled deployment.

Commercial boundary

Enough public evidence to evaluate. Direct engagement for production rights and protected IP.

The public path shows the runtime shape, benchmark evidence, and buyer demos. Direct engagement covers production builds, support, deployment posture, and protected implementation details.

Public evaluation

Architecture, SDK contracts, reproducible evidence, benchmark paths, use-case packages, and repo inspection.

Commercial coverage

Protected AI builds, production packaging, redistribution, OEM embedding, support, managed services, and negotiated patent rights. StreamKernel includes pending patent claims covering key AI enrichment and model governance methods.

Enterprise fit

Private support, air-gapped expectations, compliance-heavy environments, and buyer-specific runtime review.

Commercial path

Ready to discuss production, OEM, or managed-service use?

Send the deployment model, target destinations, AI path, and support expectations so the licensing conversation starts with real context.