Consulting services
Engineering Help from the People Who Built LTIAAS
We work as part of your team: writing integration code, debugging across vendor boundaries, and covering the standards beyond LTI®.
Talk to our teamWe Write the Code
Not slide decks. Our engineers work in your codebase, in your language, against the same API the guides document.
We Know the LMSes
We have found, filed and fixed bugs in the learning management systems themselves, and we know who to talk to at the vendors.
Beyond LTI®
QTI, Common Cartridge and SCORM come up constantly in ed-tech. We work in all of them, not just the protocol we sell.
Most of What We Are Asked for Starts with a Conversation
Tell us what you are building and where it is stuck, and we will come back with how we would approach it.
What It Is
LTIAAS exists because implementing LTI® from scratch is hard. Consulting exists for everything the API cannot do on your behalf: deciding how a launch should map onto your data model, working out why one LMS behaves differently from the rest, or handling the content standards that sit next to LTI® in a real ed-tech product.
Engagements are scoped to what you actually need. That might be a few days pairing with your engineers to get a first launch working, a longer piece of product development, or an open line to call when an integration misbehaves in the field.
Everything below is work we do regularly, and the examples under each are real engagements.
What We Do
Integration and Application Development
We write the code that connects your product to the LTIAAS API: the launch handling, the SSO mapping, the grade passback. We build ed-tech applications outright when that is what a customer needs. We work in your repository, your stack and your review process.
Scope a piece of workInteroperability Debugging with LMS Vendors
When a launch fails in one LMS and works everywhere else, the bug is often not in your code. We reproduce the problem, isolate which side is at fault, and take it to the vendor. We have filed and fixed defects in the learning management systems themselves rather than working around them.
Troubleshooting guidesThe Other Ed-Tech Standards
LTI® rarely arrives alone. We work in QTI for assessment items and item banks, Common Cartridge and Thin Common Cartridge for packaged course content, and SCORM for older courseware: importing it, exporting it, converting between formats, and making it behave inside a modern tool.
Ask about a standardHosted Test Servers
Testing an LTI® integration properly means launching from a real LMS, and standing one up is its own project. We host test servers for our customers so your team has somewhere to register a tool, run launches and reproduce a customer's setup without waiting on their IT department.
Request a test environmentTell Us What You Are Building
Send us the shape of the problem: the systems involved, the standards in play, and the deadline you are working to. We will come back with what an engagement would look like.
