The AI agent platform for higher education

Build agents that answer from your own documents, call your own systems, and know when to hand off to a person. Publish them in Microsoft Teams, in Moodle or on the web — and keep every action on the record.

  • Grounded in your content
  • Tool calling & MCP
  • Human escalation
  • Hosted in Canada
Book a Demo
The Soria agent console

What is Soria?

Soria is a multi-tenant AI agent platform built by LS2 Innovation for higher education and the public sector. An organisation defines agents — their instructions, their model, the knowledge they may use, the tools they may call and the channels they appear on — and Soria runs them, versions them and logs everything they do. Agents come in three shapes: conversational (a person starts it), webhook (a system starts it) and scheduled (the clock starts it). The platform is model-agnostic, grounded by retrieval over your own documents, configurable per organisation, and deployable on infrastructure in Québec or Canada.

The product

Three kinds of agent, one platform

Same engine, same knowledge, same tools, same audit trail. What differs is what wakes the agent up.

01

Conversational

A chat agent in Teams, in your LMS or on the web. Answers in natural language from your grounded content, returns adaptive cards and suggested actions, and executes real operations mid-conversation.

02

Webhook

An inbound event from any system — a record created, a team provisioned, a meeting recorded — triggers an agent that runs its instructions and calls the tools it needs. Every run logged.

03

Scheduled

Recurring work from every thirty minutes to monthly, or on a cron expression: synchronisations, audits, digests and reminder campaigns, with run history and status per execution.

Explore the platform

Capabilities

What you actually configure

None of this is a custom build. It's the same product, configured — which is why the second agent costs a week, not a project.

Knowledge

Grounded on your own content

Vector stores built from your uploaded documents, from a SharePoint site or library, or from a connected system — several per agent, with file version history and optional learning from past conversations.

Actions

Tools, MCP servers and APIs

Declare a tool with a JSON schema, or attach an MCP server over OAuth. Group tools and grant them per organisation and per agent, so an agent can only reach what you allow.

Channels

Teams, web, your own app

Publish the same agent as a Microsoft Teams app, as embedded web chat, or behind your own interface through a scoped OAuth client. Multilingual from a single agent.

Lifecycle

Draft, publish, roll back

Agents publish as versions, with prompt history that shows what changed, who changed it, and lets you restore the previous version. Changing what an agent says never needs a release.

Governance

Multi-tenant roles & delegation

Granular feature permissions mapped to your directory groups, observer access for teams with no LMS account, and delegated content management under draft-review-publish.

Evidence

Four log streams

Audit log, user activity, task run logs and conversation history — timestamped, actor-tagged and exportable. Plus usage, themes, peak moments and the questions nobody could answer.

Soria connected to Microsoft 365, Moodle and institutional systems

Integrations

Connected to what you already run

An agent is only as useful as what it can reach. Soria sits beside your systems of record and links back to them rather than replacing them.

  • Microsoft 365 & TeamsTeams app, SharePoint indexing, Outlook and calendars, Entra ID single sign-on, and event subscriptions on teams and meetings.
  • Moodle & your LMSPublished inside the course environment as a web app, or standalone for people with no LMS account.
  • SIS / ERP / PGIRead-only context signals for conversational agents, plus extraction, matching and syncing for operational ones.
  • Ticketing & internal APIsNative service-desk integration so escalation lands in the queue your team works, and any HTTP endpoint becomes a tool.
See the integrations
Escalation from an agent to a human team

Responsible AI

Refuses rather than guesses

In a public institution, a confident wrong answer about a deadline or a regulation does real damage. Soria's guardrails are product features, not a policy page.

  • Grounded in your documents onlyRetrieval over content your teams publish and approve, with the source shown on every answer.
  • Defined escalation thresholdsLow confidence, a sensitive topic, a repeated request or a direct ask — any one hands the person to a human.
  • Strict, transparent, versioned parametersScope, tone, temperature, sources and refusal behaviour are configured per organisation and inspectable — no hidden prompt.
  • Model-agnostic and contractableProviders, models, processing regions and subcontractors are named per deployment. Your content never trains a third-party model.
Read our AI commitments

Use cases

What institutions build with it

Same platform, different configuration. These are the patterns we see most often in higher education.

Featured

Student self-assessment

Students self-assess, get a clear self-portrait, and are routed to the services their institution already offers — with a human one click away.

Read the use case →

Procedure assistant

Grade appeals, absences, extensions, accommodations — explained in plain language, always with the official source shown.

IT & internal help desk

Answered from your own knowledge base, escalating into your ticketing queue with the context already gathered.

Operational automation

Scheduled syncs, event-driven provisioning, audits and reminder campaigns — agents nobody has to talk to.

All use cases

Security, hosting and compliance controls

Security & hosting

Built for the rules public institutions live under

  • Hosting in Québec or CanadaManaged cloud, your own cloud tenant, or on-premise — with model inference inside the same perimeter.
  • Consent-gated retentionAnonymous use is a first-class mode. Consent is granular, revocable, and stated before anyone answers.
  • Documented data lifecycleRetention periods, backup handling, consent withdrawal, deletion and access requests — answerable without an engineering ticket.
  • Reversibility by designContent, configuration and data exportable in open formats at any time, with IP terms set in the contract.
Security & hosting

Who we work with

Higher education first, public sector too

Universities, CÉGEPs and colleges

Student-facing assistants and self-positioning tools, referral tools for support teams, faculty and IT agents, and automation across the SIS, Moodle and Microsoft 365 — configurable per establishment, per cycle, per program and per department, including for continuing education and professional training.

Government & public bodies

Citizen-facing support, internal help desks and routine back-office workflows, with the audit trail, access control and data-residency guarantees the public sector requires.

Thirty minutes inside the product

An agent configured, grounded on a document you bring, calling a tool, refusing a question it shouldn't answer, and publishing a version. No slides.

Book a Demo
Soria demo preview