No integration required.
The default for every ArthurAI™ deployment is browser-deployable, no LMS / SIS / HRIS / SMS dependency. That is a feature, not a limitation — it is what makes pilots possible at institutions where procurement integration would take a year. Where an institution wants federated SSO or a sync with a system of record, we support it as a custom engagement.
Browser-deployable. Day one. An institution provisions user accounts through their ArthurAI institution portal, branded for the institution, on a subdomain assigned at onboarding. Learners log in via credentials provisioned by the institution administrator. Educators create courses, generate lessons, and run cohorts — all without touching the institution's existing learning systems.
This is the same equalization logic that runs across the MindHYVE family. ChironAI™ ships browser-deployable for healthcare without forcing an EHR integration. ArthurAI™ ships browser-deployable for education without forcing an LMS / SIS / HRIS / SMS integration. The bet is that a pilot you can stand up in a week is worth a hundred procurement RFPs you never finish.
- Federated identity
Microsoft Entra ID SSO
Federation with the institution's Microsoft Entra ID (formerly Azure AD) tenant. Conditional-access policies, MFA enforcement, and group-based provisioning inherit through the federation. Standard at institutional scale; no custom engagement required.
- LMS-adjacent
Canvas / Moodle / Blackboard / D2L
LTI 1.3 integration available as a custom engagement for institutions that want ArthurAI launchable from inside the LMS. The integration carries cohort + roster + grade-passback. The LTI tool is the bridge; the platform itself remains browser-deployable on its own subdomain.
- SIS-adjacent (K-12)
PowerSchool / Skyward / Infinite Campus
One-way SIS integration available as a custom engagement: roster sync from the SIS into ArthurAI, with periodic refresh. Grades stay inside ArthurAI's gradebook unless the district explicitly wants grade-passback (which adds a custom integration scope).
- HRIS-adjacent (CLE)
Workday / SuccessFactors / UKG / BambooHR
One-way HRIS integration for the corporate edition: employee roster sync, manager hierarchy, role and department metadata. Available as a custom engagement when the corporate L&D buyer needs it; the default ships without.
- Certification body
Pakistan Engineering Council / NAVTTC / equivalents
Integration with regional certification bodies for VLE deployments. Submission of attestation events, competency frameworks, and credentialing artifacts per the certification body's technical specification. Custom engagement per certification body.
- Identity providers
Beyond Entra: Okta / Auth0 / Shibboleth
Other SAML 2.0 / OpenID Connect providers integrate as custom engagements. Higher-ed institutions on Shibboleth / InCommon can federate with the same SAML pattern. Smaller institutions often prefer the Microsoft Entra ID default.
Why ‘no integration required’ is the right default
- Time-to-pilot collapses. An institution that wants to pilot ArthurAI™ can be in production with a cohort in a week, not a quarter. That changes which institutions can even consider the platform.
- Procurement gates fewer. Integration with a system of record involves the security team, the integration team, and the system of record vendor. Browser-deployable involves none of those teams. The decision moves faster.
- Pilot to scale is honest. A pilot that succeeds without integration tells the institution something true: their educators can use this, their learners can use this, the platform delivers on its capability story. If the institution then wants to scale with integration, the integration scope is informed by what they learned in the pilot.
- The platform is the platform. The integration layer is optional, not load-bearing. If the integration vendor goes away, your ArthurAI™ deployment doesn't.
See also: multi-tenant isolation · CLE HRIS posture · Eve-Grid substrate.