There are a few things to consider when piloting or implementing Cogniti at your institution.
Cogniti is in active development by a team at the University of Sydney, and we welcome collaborators from other institutions in our journey.
Governance #
It’s important to ensure that you follow all relevant governance in place at your institution. For example, this may include checking with your IT department, or privacy office, or educational technology group.
Our Privacy Policy, Terms of Service, and other policies are available on this site.
Cogniti currently uses Microsoft Azure services for hosting the application, database, document embeddings, and AI models (such as from OpenAI and Anthropic). Cogniti can access AI models from OpenAI, Anthropic, Google, Mistral, and others, and these can be switched on/off for your organisation.
Adoption models #
The best approach for your institution will depend on a balance of the following factors. For example, your institution may prefer to fully own and control the underlying services (e.g. database, document embeddings, language models), or only some of these, or none of these. Or, your institution or jurisdiction may stipulate where data needs to be hosted.
These considerations lead to some adoption models.
| Managed application via Microsoft Marketplace | Software-as-a-Service (SaaS) | |
| Fee (received by the University of Sydney) | Tiered management fee. First 50 users free. | Tiered licence fee. Free limited pilots may be available. |
| Azure consumption charges | Separate, paid to Microsoft | Included in licence fee |
| Support and training | Purchasable | Included in licence fee |
| Maintenance and updates | Your internal team manages deployment and maintenance. Updates are automatic and managed. | Automatic and managed |
| Hosting environment | Your institution’s own Azure environment (you control the Azure region) | Azure environment managed by the University of Sydney (Australia region) |
| Recommended scenario | For institutions with very strict data residency and related requirements for generative AI applications, who wish to host Cogniti ‘internally’ in a dedicated environment. | For most institutions with strict data residency, security, safety, and related requirements for generative AI, who wish for a trusted third party to host Cogniti in a cloud environment. |
| Availability | Now available to private audiences. Please get in touch if you are interested in this option. | Now available to all institutions. Please get in touch if you are interested in this option. |
Free pilot on SaaS #
For small-scale pilots, it may be beneficial in terms of ease and efficiency, balancing risk, for us to host Cogniti and sponsor some light use. No service level agreement is available for free pilots.
Self-host (by invitation only) #
By invitation only, the University of Sydney can share the Cogniti codebase with your institution, under a licence agreement, so that your institution can deploy it on its own Azure infrastructure. In this case, your institution pays all costs (e.g. servers, AI inference, support, etc) and handles all support and maintenance. This is available to select institutions on a limited, invitation-only basis to institutions who have AI/software development expertise and/or are able to contribute to Cogniti development and advancement.
LMS integration #
LMS integration can be arranged on a per-organisation basis. Your institution’s LMS administrator will need to reach out to us and we can provide configuration guides.
Cogniti currently supports LTI 1.3 integration with Canvas, Moodle, Brightspace, and Schoolbox. Integration with Blackboard is under development. Integration with other LMS platforms can be discussed.
Cogniti supports API integration with Canvas.
