Pricing Tin Can in the Cloud

Several people have been asking us of late how we intend to charge for the Tin Can API/LRS component of SCORM Cloud. To be candid, we haven’t entirely figured out how we should charge for the standalone LRS capability found in SCORM Cloud. So, our thinking is this:

We’re going to wait a little while to figure that out, and during that time, externally-generated Tin Can statements will remain free. For example, statements that originate from our Tin Can bookmarklet will be stored at no cost.

At this point, we commit to keep externally generated Tin Can statements free of charge until the formal release of Tin Can from ADL (currently rumored for the end of Q1 2013).

One key distinction is that if you use SCORM Cloud to import a Tin Can package and then assign that course to a user via SCORM Cloud or one of its plugins, you will consume a registration, and registrations cost money. For pricing purposes, we treat Tin Can packages just like SCORM packages.

Our best guess is that as we move beyond the formal release of Tin Can next year, we will probably base our pricing around the number of users for whom you report statements on. We want you to collect a huge pile of statements this year. We want you to collect a huge pile of statements going into the future. More Tin Can statements will make Tin Can more effective, and it will allow us to better support our users. We will find a reasonable way to relate the utility of those statements to your costs. At this point, though, we still feel it’s too early to specify that pricing.


  • Gaurang Gautam

    Kindly provide the details of scorm or tin can plugin and its cost.

  • Yash Mohanty

    How could I send my SCORM Cloud statement to my Grassblade LRS

  • Ryan Donnelly

    Thanks for your comment. I have a ticket from Ashok that I just replied to.

  • Yash Mohanty

    Where have you replied?

  • Ryan Donnelly

    Via the ticket opened at support@scorm.com.

  • Yash Mohanty

    I have sent the Screenshots please check and help us to solve the issue.

  • Ryan Donnelly

    Thanks for the update. We’ll work this issue from the ticket. We’ll be in touch soon.