Enterprise · Integrations & Delivery

Fit your environment, or become it.

Knowledge Foundry is built to integrate into the systems you already run, or to become the delivery environment itself. Structural integrity is preserved either way. The choice is deployment shape. It is not a trade off in integrity.

Hub-and-spoke architecture with a central foundry cube connected via pipe channels to peripheral systems, orange glow at each joint. Integrations illustration.
Why this matters

Two paths. Both preserve the structure that makes the program defensible.

Most organizations fall into one of two categories. Those with an established LMS that must not be disrupted, and those that need a complete, high integrity delivery environment of their own. Knowledge Foundry supports both, and the choice is genuinely a choice. Neither path compromises structure, provenance, or integrity.

Path one: integrate into your existing environment via SCORM, structured HTML, JSON, or API. No rebuilding. Path two: deploy the white label LMS. A complete structured learning stack on your domain, with your branding. Both paths route programs through the same authoring, review, and governance discipline behind them.

Six integration primitives

Exports, APIs, identity, tenancy. Shaped for enterprise by default.

SCORM 1.2 export

Structured programs export to SCORM 1.2 packages for deployment into any conformant enterprise LMS. No manual reconstruction required.

Delivery driven by API

The Foundry is API first and multi tenant. Programs, blocks, provenance, and integrity data are accessible programmatically for bespoke delivery layers.

Structured HTML and JSON

Full structured HTML packages and JSON structure with provenance exports preserve dependencies, validation points, and integrity in any environment.

White label LMS

Complete delivery environment on your domain, with your branding and access controls. Studio authoring, review queue, analytics, and role management included.

Identity and access

SAML, OIDC, and enterprise identity providers integrate cleanly. Access based on role, license management, and isolation across tenants are first class.

Sits alongside, does not replace

Existing LMS, HRIS, content stores, and identity providers remain. The Foundry is a source of truth for structure and integrity, not a demand to rip and replace.

Three deployment tempos

Generate. Review. Export. Choose the rhythm.

The same authoring and governance discipline supports fast, balanced, and flexible deployment shapes. Each of them uses the human review gates that make release deliberate.

STEP 01

Generate to deploy

Fastest path. Immediate structured deployment for rapid content needs. Suitable when the review gate lives elsewhere in your process.

STEP 02

Generate to review to deploy

Balanced path. Human in the loop review through the mandatory Review Queue prior to final release. The default operating model for most environments.

STEP 03

Generate to export to integrate

Flexible path. External delivery to third party ecosystems via SCORM, structured HTML, JSON, or API. Structural integrity travels with the export.

What you get out

Delivery that matches your environment, not the other way around.

Programs deploy in the format your environment expects. Version precision is guaranteed by immutable course hash identity. Structural integrity, meaning logic, dependencies, and validation points, remains functional in your chosen delivery surface without degradation. The Foundry is the source of truth. The delivery environment is the expression.

Your domain. Your branding. Your access controls. Or your existing LMS, unchanged, with structured programs deploying into it cleanly. Either way, the program that reaches learners is the program that was approved for release.

Common questions

How Integrations & Delivery work, in detail.

No. Knowledge Foundry integrates into your existing environment via SCORM 1.2, structured HTML, JSON, or API. Programs deploy in standardized formats aligned to enterprise LMS expectations. No rebuilding. No forklift. The Foundry becomes the source of truth for structure and integrity. The LMS remains the delivery surface.
Any LMS that conforms to SCORM 1.2, which covers the majority of enterprise deployments. Native LearnPress deployment is supported for organizations using the white label path. Custom LMS environments are supported via structured HTML and API integration.
Foundry Hash values travel with the exported program. Recipients (LMS platforms, downstream systems, auditors) can independently confirm that what they received matches what was released. Integrity does not degrade at the export boundary.
Yes. The white label LMS is a complete delivery environment: Studio authoring, review queue, compliance dashboard, standards manager, analytics and telemetry, learner enhancement tools, and role and license management. Deployed on your domain with your branding. Suitable when no incumbent LMS exists or when full control is a requirement.
Regeneration can occur at the course, module, lesson, or block level without affecting adjacent content. Revisions do not push live automatically. A manual sync is required after regeneration, so release remains controlled. Each deployed version is identified by immutable course hash.
Yes. The API is production grade, multi tenant, and covers program lifecycle operations, access at the block level, provenance retrieval, and integrity verification. It is the same interface the platform uses internally. Full documentation is available under a mutual non-disclosure agreement.
Tell us about your delivery environment

See integration on your own stack.

Whether you are integrating into an established LMS or launching a new branded delivery environment, we align structured generation to your release process. 45 minutes. Concrete recommendations. No obligation.

We reply within one business day.