Skip the Protocol
LTIAAS handles the OAuth2 flows, JWT signing and key rotation that LTI® 1.3 requires, on whichever side of the launch you sit.
One API for Every LMS
The same endpoints work whether a launch came from Canvas, Moodle, Blackboard, Brightspace or Schoology.
Help When You Want It
Self-serve on a free account, or bring in the engineers who built LTIAAS to work alongside your team.
Receive Your First LTI® Launch in Minutes
Register an LMS, point us at a URL, and LTIAAS performs the handshake and redirects the user to your application.
Our Products
LTIAAS Launch
LTIAAS Launch sits between your application and any LTI® 1.3 compliant LMS. It performs the protocol handshake, redirects the user to your tool, and gives you a REST API for the LTI® services, so you can support Canvas, Moodle, Blackboard, Brightspace and the rest without implementing LTI® yourself.
For learning tools
About LTIAAS Launch
LTIAAS Connect
LTIAAS Connect is the other side of the protocol: it lets a learning management system consume LTI® 1.3 tools. You register the tools you want to support, LTIAAS handles the launch and the signing, and webhooks let your LMS answer the service requests those tools make.
For learning management systems
About LTIAAS Connect
Ed-Tech Consulting
The team that built LTIAAS also builds with it. We write the integration code alongside your engineers, chase interoperability bugs down into the LMS itself, work in the other ed-tech standards including QTI, Common Cartridge and SCORM, and host test servers so you have somewhere real to try it all.
For teams who want help building
About Ed-Tech ConsultingNot Sure Where You Fit?
If learners are sent to your application, start with Launch. If your system is the one sending them, start with Connect. If you would rather have our engineers do the work with you, start with consulting.
