Ahoy vs Keen: What are the differences?
Ahoy and Keen can be primarily classified as "Custom Analytics" tools.
Ahoy is an open source tool with 2.71K GitHub stars and 267 GitHub forks. Here's a link to Ahoy's open source repository on GitHub.
What is Ahoy?
What is Keen?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Ahoy?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
The service is incredibly easy to use, both from a data collection standpoint and a visualization perspective. I ran into a few snags with the documentation lagging behind the actual code, but I got pretty near real-time support from one of the founders emailing me from 30,000 ft over Thanksgiving weekend.
The only reason I know about any reliability issues is because Keen emails me whenever anything is degraded or problematic, even if it only lasts a few minutes. They could be a whole lot less transparent and get away with it, but they don't take that short cut.
We use Keen to analyze transfer logs over at Mover (https://mover.io). Each time a user performs a transfer of files we give Keen a summary of their transfer. At any time, technical and non-technical users on our team can easily pull information out of the datasets we've presented.
Keen makes it extremely easy to feed data and then ask for useful graphs and formatted information. We wrote a larger review on our blog at https://blog.mover.io/2014/03/15/why-we-chose-keen-io/
I’ve known the Keen IO team since I started working on Leanstack and they’ve been super helpful. Leanstack didn’t have too much use for something like Keen early on. But recently we started talking to vendors that wanted access to basic analytics for their pages (views and clicks). So we started thinking about how we could provide customer-facing dashboards. That’s when Josh over at Keen suggested Keen, and it seemed like a great fit. Not only could we use Keen for external dashboards, but we could use it to get insight into usage for our own purposes.
At the same time they were working on an open source library called CommonWeb that helps you track everything happening on your site with little-to-no configuration. So we signed up and agreed to be a guinea pig for their new library to see how CommonWeb could help us. It’s been super useful so far. We now know who’s logging in to StackShare, how long they were on the site, and which content they contribute; we have much better insight into funnels, and we’ll soon have dashboards. The Keen team has been great as far as support (thanks Alex!). I think we’re really going to be able to improve the site once we start using the data we’re collecting, super excited about that. We’re definitely going to be using their new open source dashboards.
Having watched the Keen.IO guys grow their company since it's inception, I think we can safely say that they are one of the best out there in terms of general analytics and storage.
I used Keen because it was an extension that could be added through Heroku. It was very easy to set up application metrics and dashboards with them.