Not terribly shocking, since you probably just created more apps than their entire customer base this week. From their perspective it looks like a huge resourc

Not terribly shocking, since you probably just created more apps than their entire customer base this week. From their perspective it looks like a huge resource hit from a very, very costly action by an account which has not given them many reason$ to trust with anomalous behavior yet. Count yourself lucky: a less hacker friendly company would ban first and email later. I'd suggest apologizing for a somewhat poor architecture choice, turning off that button temporarily, and then round-robinning folks into 10 demo instances which are reset daily with a big Do Not Put Student Data In Here warning at top in red. This may be easier than rearchitecturing the demo to be multi-tenant, though that is a good idea long-term.