One gateway.
One thing to review.
Every AI-connected plugin routes through the Connect Suite central hub into our central backend service — the same trusted, resilient backend that powers other mySleipnir ecosystem products, with multiple model and service providers and automatic fallback if one goes down. That shared pipeline means the Evidence-Based Learning Engine enforces quality and a pedagogical foundation on every AI interaction, across every plugin.
Stateless by design — nothing to leak
Our APIs are fully stateless. No customer content, learner data, prompts or responses are ever persisted on our side — requests are processed in memory and discarded. The only exception is usage logs, which are fully anonymised (no PII, no course content) and follow a strict retention policy for operational monitoring and billing only.
One connection, not many
IT configures one connection. Every plugin in the suite is live. There is one thing to audit, one credential to rotate — not a per-plugin sprawl.
Educator authoring, by design
Several plugins explicitly prohibit the learner role from authoring — not just omit it. The educator/learner boundary is preserved even when a role assignment is misclicked.
PII anonymised before every call
Anonymisation runs unconditionally at the top of every request — educator, learner, flashcards, translation, evaluation, accessibility adaptations, chat and code-help features all pass through the identical step.
Same backend as Owlia Designer
No per-product pipeline. Every feature Connect Suite plugins use runs through the same central backend service Owlia Designer uses.
Resilient model fallback chain
Multiple AI providers behind one gateway — with support for local models. If one provider goes down, the chain fails over automatically so teaching can continue.
Why architecture matters for IT.
A per-plugin AI story is a per-plugin security review. A dozen chatbot plugins on a Moodle site is a dozen threat models, a dozen key policies, a dozen answers to "where does learner data go?"
- One credential lifecycle to manage — rotate, revoke, replace.
- One cache policy applied suite-wide — no per-plugin surprises.
- One connection to review — auditable end-to-end.
- One backend to trust — the same one Owlia Designer customers already trust.
- One resilient provider chain — automatic failover, not a single point of failure.
Want the full trust statement?
Verified vs. still-to-confirm — no marketing fog.