Common base, local configuration
Agents, knowledge sources, tools, wording, branding, roles and AI scope are configuration — held per organisation, and for institutions also per cycle, per program and per department.
Where Soria runs, and what happens to your data
Hosting in Québec or Canada — AI inference included. Consent-gated retention, a documented data lifecycle, exportable audit logs, and reversibility written into the contract rather than promised.
Deployment models
A shared base, deployed on your terms
Soria is multi-tenant by construction, so a network gets one maintained codebase and every organisation still gets its own configuration, its own content and its own hosting decision.
Central updates propagate
A shared template or a corrected source is changed once and flows everywhere it is referenced, without touching each organisation by hand.
Export, import, reuse
Content and configuration move between organisations, so one institution's good work becomes the next one's starting point.
Versioning and rollback
Agents publish as versions, with prompt history and the previous version restorable — per organisation, with no network-wide release window to coordinate.
Progressive rollout
Join in waves. A pilot, then a faculty, then the campus — each at its own pace, on the same version of the platform.
Designed to keep evolving
Maintenance, upgrades and new capabilities land on the shared base. New systems are reached through tool definitions and MCP servers rather than forks.
Hosting & residency
Hosted in Québec or in Canada — including the AI
Data residency that stops at the application boundary is not residency. Every AI component the solution calls falls inside the same perimeter as the solution itself.
| Model | Where it runs | Who operates it |
|---|---|---|
| Managed cloud | Canadian cloud regions, operated for the institution. | LS2 Innovation, under the institution's contract. |
| Institution's cloud tenant | The establishment's own Canadian cloud subscription. | The institution, with LS2 as application operator. |
| On-premise | A server in the establishment's own data centre. | The institution's infrastructure team. |
| AI components | Model inference in Québec or Canadian regions, contracted explicitly per deployment. | Named providers and subcontractors, documented in writing. |
Certifications and audit reports
The underlying cloud infrastructure we deploy on carries the recognised information-security certifications for its Canadian regions. LS2 Innovation's own certification position, the scope of any external audit report, and the commitment to provide it annually are established contractually with each institution — we document them in full in a tender response rather than summarising them on a web page.
Data lifecycle & audit
Retention, withdrawal, deletion, proof
Public bodies in Québec answer for every record they hold. The platform is built so those answers are available without an engineering request.
Consent is the gate
No response is retained without explicit consent. Consent is granular, revocable, and the interface states plainly what will be kept before anyone answers.
Documented retention periods
Each data category carries a retention period agreed with the institution, applied automatically — including to backup copies on their own documented cycle.
Access and rectification requests
Administrators can locate, export, correct, anonymise or delete an individual's data to answer a rights request within statutory delays.
Audit logs that hold up
Sign-ins, permission changes, content edits, administrative actions and agent actions are timestamped, actor-tagged, retained per your policy and exportable.
Reversibility
Institutional content, configuration and data are exportable in open formats at any time, so an exit is a scheduled export rather than a negotiation.
Rights over what you build
Content, configurations and institution-specific developments produced under the mandate belong to the institution. The terms are set in the contract, not assumed.
Support & continuity
Service in French, by people who know the file
LS2 Innovation is a Québec company. Support is delivered in French during standard business hours by the team that builds the product — not a routed first line reading a script.
- French and English supportStandard business hours, with response and restoration targets set in the service agreement.
- Defined escalation pathA named route from first contact to engineering, with the thresholds written down.
- Training by audienceSeparate tracks for administrators, content owners, front-line teams and technical staff — with documentation kept current as the product moves.
- Business continuityDocumented detection, analysis and notification procedures for outages and security incidents, with agreed notice delays and joint handling with the institution.
- Change managementWe have run phased implementations across institutions before. The pilot, the rodage and the wave plan are part of the proposal, not an afterthought.
Planning a network-wide deployment?
Tell us how many establishments, which LMS, and what your hosting constraints are. We'll come back with an architecture and a phased plan.
Contact us