OEM and embedded licensing

Add capabilities your customers can buy. Without building the whole stack yourself.

Embed one or both independently licensable OntoGuard runtimes in your data, AI, workflow or cybersecurity platform. Keep your customer experience, distribution and integrations. Evaluate the economics of licensing the underlying semantic or action-authorization infrastructure.

License either one or both

Two independent OEM opportunities

01 · Data & knowledge infrastructure

OntoGuard Semantic Intelligence Runtime OEM

Make enterprise data understandable, trustworthy and reusable.

No LLM. Fully offline.
  • Turn existing glossaries, dictionaries, policies and schemas into one governed ontology.
  • Keep every concept tied to its evidence; expose gaps and disagreements.
  • Detect changes in business meaning with native semantic contracts.
  • 27 qualified ingest profiles · 17 output formats · 157 documented API paths.

02 · AI & cyber control infrastructure

OntoGuard Headless Decision Authorization Runtime

Keep the right action moving. Stop the wrong one before it takes effect.

Permission to act, checked at execution.
  • Protect money movement, record changes, case dispositions and privileged tools.
  • Respect existing human or policy approvals; check again if anything changes.
  • Refuse altered or unauthorized actions at the protected execution route.
  • Prove the exact authorization and separately recorded outcome.

Build versus license

What you would otherwise need to build and maintain

Engineering investmentSemantic IntelligenceDecision Authorization
Core capabilityHeterogeneous input construction, exact evidence and semantic identity.Typed action binding, trusted authority and revalidation.
Hard casesConflicting definitions, unknowns, obligations and temporal lineage.Stale approvals, changed action, refusal, retries and unknown outcome.
Reusable outputSealed ontology, graph, native contracts, 17 formats and 157 API paths.Correlated decision, anchored consume, execution receipt and standalone proof.
Ongoing assuranceVersioning, strict validation, cross-format consistency and release qualification.Trust integration, recovery, conformance, evidence durability and verification.

Licensing shifts the responsibility for maintaining the reusable core toward OntoGuard. Your platform still owns the application, source/authority access and integration quality. Compare actual total cost, time-to-market and maintenance; no guaranteed savings.

Commercial model

A practical commercial path

01

Choose an existing product surface

For SI: catalog, data platform, semantic layer, knowledge graph or data quality product. For DA: agentic workflow, financial crime, security, privileged automation or AI platform.

02

Scope a paid technical evaluation

Agree an existing customer problem, buyer-owned sources or one protected action, success metrics and integration owner. Do not require both runtimes.

03

License what proves valuable

Negotiate enterprise, embedded OEM or field-of-use terms after technical and commercial acceptance. No published pricing or implied customer commitments.

Evidence for product and engineering leadership

Review the proof before committing

Actual controlled output

A conflicting definition stays visible

Two synthetic workbooks define Payment Settlement differently: final funds transfer versus acknowledgement before finality. The controlled ontology preserves the two senses for review instead of forcing a false consensus.

Inspect the actual 22-concept ontology · See obligations and lineage

Actual native contracts

Same INTEGER. Different business meaning.

“Principal Amount” changes from excluding interest and charges to including capitalized interest while still excluding other charges. Both assets retain INTEGER. Native comparison reports DEFINITION_DRIFT as a breaking change.

Read the business case · Inspect native receipts and revisions

Controlled synthetic-source output, separate from commercial production qualification; disclosure approval pending. No guarantee of perfect semantic accuracy or legal authority.

Reviewed integration · October 6, 2026

97 refused attempts. Four exact actions executed.

An independent review exercised negative wrapper and direct-executor paths in a bounded software harness. All 97 negative probes were refused without a protected effect; four positive probes executed the validated action.

Read PR #236 and independent review · Read the case study

Public proof covers the reviewed adapter and bounded executor—not the entire proprietary runtime, a bank deployment, hardware attestation or production-wide non-bypassability. v1.5.2 controlled mock-target evidence is separately available in the Proof Explorer.

Integration responsibilities, evaluation and technical evidence

Build versus license

01 · Data & knowledge infrastructure

OntoGuard Semantic Intelligence Runtime OEM

Make enterprise data understandable, trustworthy and reusable.

No LLM. Fully offline.
  • Turn existing glossaries, dictionaries, policies and schemas into one governed ontology.
  • Keep every concept tied to its evidence; expose gaps and disagreements.
  • Detect changes in business meaning with native semantic contracts.
  • 27 qualified ingest profiles · 17 output formats · 157 documented API paths.

02 · AI & cyber control infrastructure

OntoGuard Headless Decision Authorization Runtime

Keep the right action moving. Stop the wrong one before it takes effect.

Permission to act, checked at execution.
  • Protect money movement, record changes, case dispositions and privileged tools.
  • Respect existing human or policy approvals; check again if anything changes.
  • Refuse altered or unauthorized actions at the protected execution route.
  • Prove the exact authorization and separately recorded outcome.
ResponsibilitySI runtimeDA runtime
OntoGuardNative ingestion, evidence, concept construction, graph, contracts, assurance, exportsBinding, trusted state, revalidation, consume, recovery, proof and verifier
OEM platformSource and export adapters; UX and workflowTyped action, protected route and executor integration
Enterprise ownerSource rights and semantic reviewAuthoritative approval/policy/state; target credentials
Independent operatorAs applicable to evidence disclosureIndependent log when required by trust mode

Integration effort depends on existing architecture. Enterprise, OEM/embedded and field-of-use licensing subject to negotiation; no published pricing or unsupported SLA.

Technical integration checklist

  • SI: representative sources, authorized access, target exports/API, revision and data contract needs, offline requirements
  • DA: exact typed action, authority/state owner, protected execution seam, outcome observations, independent trust deployment where required
  • Both: security/privacy boundary, versioning, integration acceptance, maintenance and commercial owner

Public DA integration proof

PR #201 · TRACE adapter

Independently reviewed bounded integration

Merged September 20, 2026. Independent maintainer reproduction: 27 adapter tests. Authorized $250,000 path committed once with TRACE; altered $260,000 path refused, pending, zero commits and no TRACE.

Read PR #201 and review

PR #236 · Pre-commit enforcement

Independently reviewed bounded integration

Merged October 6, 2026; October 3 review by Carlos (carloshvp): 36 integration tests, 97 negative wrapper/direct-executor probes refused with zero commits and no protected effect, four positive probes executed the validated exact action. Imran Siddique approved and merged.

Read PR #236 and review

Bounded adapter and software harness, not independent validation of the complete runtime, SI, customer deployment or universal non-bypassability. Source: linked PRs; launch recheck required.

Inspect current reference evidence

Semantic Intelligence

Actual controlled synthetic v332 run: 22 constituted concepts, 20 graph edges and two Needs Review rows, with exact source-cell projection; native artifact approval and demo production qualification remain pending.

Open controlled SI Explorer · Download projection

Decision Authorization

Fresh v1.5.2 reference packets and a separate controlled local mock-target execution, with test keys and recorded offline checks; not production deployment.

Inspect packets · Release evidence

Build versus license: engineering acceptance

SI platform teams integrate source access, ingestion and asset lifecycle, schema and export mapping, evidence-linked UI and review. Measure existing ontology preparation and reconciliation against comparable representative inputs. DA platform teams own trusted authority and state, typed action binding, target enforcement seam, outcome observation, key rotation and independent-log operation where required. Measure refusal accuracy, latency, escalation handling and audit effort in the actual target environment. Version acceptance, security responsibilities and support terms belong in the licensing agreement.

Download buyer-owned evaluation worksheet (no assumed ROI or pricing).

Versioned OEM integration — what your platform gets

Both headless runtimes are deployed inside the buyer's approved environment. The public website is a read-only demonstration, not an execution endpoint. Detailed API contracts, request schemas, implementation guidance and release-specific integration diagnostics are available through private technical diligence under appropriate terms.

Semantic Intelligence

  1. Submit representative approved sources to the privately deployed runtime.
  2. Retrieve evidence-qualified concepts, relationships and a sealed semantic asset.
  3. Inspect eligible native Semantic Data Contracts and validate records.
  4. Compare revisions and export the governed meaning into your existing platform.

The controlled demonstration shows genuine PASS and FAIL validation receipts and changes in business meaning. Review the native contract workbench.

Decision Authorization

  1. Present an exact proposed action and trusted current authority.
  2. Receive a decision and respect human or policy review.
  3. Recheck current conditions at the integrated protected execution boundary.
  4. Record the separate outcome and preserve verifiable evidence.

Explore the controlled public proof. Deployment-specific enforcement, trust configuration and version-specific conformance are evaluated privately.

Actual native contracts and sealed revision evidence

v1.89.332 generated a contract with two eligible properties. Recorded native validation, sealed revisions A/B/C, structural and semantic identity drift, stale receipt assessment, and downstream impact are available. A separate source-edited asset demonstrates definition drift with unchanged INTEGER type. Synthetic data; disclosure review pending; no action authority.

Inspect actual contract evidence · Download native-record projection

Recorded native validation outcomes

A controlled record with a correctly typed principal amount passed native validation. Providing the same amount as a string failed strict type validation. After a sealed revision changed, the prior contract was flagged for reassessment. See the recorded native workbench. These scoped results are not a blanket API conformance assertion; version-specific schema and integration acceptance are evaluated during private diligence.

Evidence and buyer questions

Can I license SI separately?

Either runtime can be licensed independently for OEM embedding or evaluated separately by enterprises. Commercial and deployment terms are agreed with the buyer; no combined purchase or fabricated pricing is required.

Inspect source or product evidence

Can DA be embedded separately?

Yes. The headless runtime is independently licensable. The OEM owns the trusted context, target-side executor, credentials, protected routes and independent log deployment choices; integration determines enforcement scope.

Inspect source or product evidence