I appreciate a well written and thoughtful e-mail like this directly from the source, rather than apples to oranges comparisons and simplifications of people's budgets. Thanks for writing this, and the pricing seems extremely reasonable. The frustration in the past has been due in part by a lot of non-transparency. The reality was that we were being told we should pay a lot of money for a single-feature service, which I recognize is expensive for you all to run, but it's not a building, it's not a maintenance/support contract (and comparisons to those things are not helpful). A lot of use lobbied for using Wordpress in higher education with the promise of open source helping the bottom line. We were being told we should have no issues with paying 10-20k a year for spam filtering on the free software we fought for (and continue to believe in). Nothing else to add, other than thank you again for a clear, transparent post.<div>
<br clear="all">-Tim Owens</div><div>University of Mary Washington<br>
<br><br><div class="gmail_quote">On Mon, Nov 28, 2011 at 1:04 PM, D'Arcy Norman <span dir="ltr"><<a href="mailto:dlnorman@ucalgary.ca">dlnorman@ucalgary.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks for the update, Pete. That definitely sounds workable.<br>
<br>
I understand the frustration and confusion about the ability of edu-institutions to pay. In my case, I work at a billion-dollar-a-year institution, but have a budget of $0 for the blogging platform. It only exists because I snuck it onto a server and support it on my own. I'm working to have it more properly managed on campus, but that's how things like this happen, and why it's often difficult to find funding for tools and services to support the effort.<br>
<br>
- D<br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:wp-edu-bounces@lists.automattic.com">wp-edu-bounces@lists.automattic.com</a> [mailto:<a href="mailto:wp-edu-">wp-edu-</a><br>
> <a href="mailto:bounces@lists.automattic.com">bounces@lists.automattic.com</a>] On Behalf Of Pete Davies<br>
> Sent: Monday, November 28, 2011 10:59 AM<br>
> To: <a href="mailto:wp-edu@lists.automattic.com">wp-edu@lists.automattic.com</a><br>
> Subject: [wp-edu] Akismet pricing<br>
<div class="HOEnZb"><div class="h5">><br>
> Hi all,<br>
> I work with the Akismet team at Automattic, and given that the topic of<br>
> Akismet pricing came up earlier on a different thread, it reminded me that it's<br>
> long overdue that I let you know what we've tried to do for educational<br>
> institutions and pricing.<br>
> First, a little background: long before spammers started getting as<br>
> sophisticated as they are now (and Akismet didn't cost us much to run) Matt<br>
> and Toni would offer academic institutions free use of Akismet in return for a<br>
> link promoting Akismet in the footer of every page that it was used on. We<br>
> did this pretty much on trust, and we had no resources (or inclination) to<br>
> enforce it. But it's been clear that the informality of the arrangement hasn't<br>
> stood the test of time: API keys have been lent to non-academic projects, re-<br>
> designs have abandoned the footer and perhaps critically (for us) supporting<br>
> the weight of spam on .edu sites has become pretty expensive.<br>
> As we gave Akismet more resources, we also revisited the signup and<br>
> subscription processes. We tried to simplify and make clearer to those that<br>
> get real value from Akismet that they should actually pay for the service. We<br>
> had an Enterprise plan that was based around the number of sites, and an<br>
> API plan that was based around the number of API calls (basically the number<br>
> of comments submitted). Allowing users to pick between the two meant<br>
> that almost all of our users could find a price point at which they were able to<br>
> use Akismet, while contributing to the costs of running it. With one glaring<br>
> exception...<br>
> Academic WordPress installs do tend to be unique because they spawn huge<br>
> numbers of individual sites, many of which are used for specific projects and<br>
> are then abandoned (attracting lots of spam). This means that these installs<br>
> tend to have (a) a lot of sites and (b) a lot of API calls.. making Akismet<br>
> prohibitively expensive. But the misconception has been that we don't care<br>
> about this: it's really not true, we just struggled to figure out a good solution<br>
> for a while.<br>
> In fact, the Enterprise (site-based) pricing didn't seem to work as well as we'd<br>
> hoped for some companies too. Thinking about the edu/multisite problem<br>
> and also the issues that some companies were having, we decided to simplify<br>
> the plan altogether and said that for the Enterprise plan ($50/month)<br>
> customers could now use Akismet on as many sites as they liked, but with a<br>
> limit of 80,000 comments per month.<br>
> So here's the exception: for .edu domains (only) using Akismet, we're<br>
> waiving the comment limit restriction. So you can use one API key for a many<br>
> sites as you like on your TLD, for $50/mo or $550/yr. So you can have as many<br>
> sites using Akismet as you like, so long as they're hosted on either a<br>
> subdomain or directory of [yourdomain].edu. There's one small caveat: we<br>
> simply don't have the resources to manage invoicing, checks and Accounts<br>
> Payable departments for this kind of<br>
> price: so we ask that you/someone pays by credit card or electronic check.<br>
> (You could also help my closing comments on unused sites.) So -- that's the<br>
> situation as it is now, and hopefully goes some way to setting the record<br>
> straight. It saddens me when I hear that Akismet is unaffordable for<br>
> academic institutions and they've had to move to Typekit Antispam (if the<br>
> age of their homepage and that Arrington quote is anything to go by, it's not<br>
> getting a lot of love these days) or, worse, Captchas. Hopefully $50 a month<br>
> makes it considerably easier than it used to be. I know that it won't work for<br>
> everybody, but it might at least allow more of you to use the service.<br>
> Happy to answer any questions and hear your feedback.<br>
> Best,<br>
> Pete.<br>
> --<br>
> [ Pete Davies | Automattic Inc. | <a href="http://about.me/petedavies" target="_blank">http://about.me/petedavies</a> |<br>
> <a href="mailto:pete@automattic.com">pete@automattic.com</a> | <a href="tel:%28415%29%20475-8007" value="+14154758007">(415) 475-8007</a> ]<br>
> _______________________________________________<br>
> wp-edu mailing list<br>
> <a href="mailto:wp-edu@lists.automattic.com">wp-edu@lists.automattic.com</a><br>
> <a href="http://lists.automattic.com/mailman/listinfo/wp-edu" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-edu</a><br>
_______________________________________________<br>
wp-edu mailing list<br>
<a href="mailto:wp-edu@lists.automattic.com">wp-edu@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-edu" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-edu</a><br>
</div></div></blockquote></div><br></div>