BugHerd is a bug tracking solution designed for users of all technical backgrounds. By making it easy for anyone to report a bug, BugHerd aims to make resolution by technical teams easier and faster.
$39
per month
Sentry
Score 9.1 out of 10
N/A
Sentry provides engineering teams with tools to detect and solve user-impacting bugs and other issues.
$26
per month
Pricing
BugHerd
Sentry
Editions & Modules
Standard
$39.00
per month
Premium
$129
per month
Deluxe
$229
per month
Team
$26
per month
Business
$80
per month
Developer
Free
Enterprise
Contact sales team
Offerings
Pricing Offerings
BugHerd
Sentry
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
BugHerd gives a discount equivalent to the cost of two months for annual subscriptions.
BugHerd offers a 14-day free-trial of all plans.
Custom pricing is available for large enterprises.
BugHerd is more focused on web-based tools, which we needed, as opposed to app-based tools like Instabug. Jira has a much higher level of complexity and barrier to entry and didn't suit our use case.
BugHerd simply added more value overall than Usersnap. We felt like BugHerd was the kind of solution we would have built if we set out to build a bug tracking tool for our web development process. The cost is reasonable and it adds a lot of value for the investment. We just …
I didn't specifically choose Bugherd for this project, but when we do select a company bug tracker, this is the one I will choose. I've used Jira and Pivotal Tracker previously, both of which had a bigger learning curve than Bugherd, so it wasn't simple for our customer support …
We used rollbar but didn't like the configuration its not easy. And also doesn't support wide features like Sentry although its a cheaper option but doesn't have the dash-boarding like Sentry and its was not easy to integrate webhooks for different purposes. Somehow many people …
Both AppD and Instana are a superset of sentry the majority of the time. Sentry is specialised in error tracking does the best in it, but the other too mentioned does a similar job along with multiple other monitoring features. Also, sampling of data is best in Instana, and is …
We actually ended up using both because New Relic is a more robust overall IT infrastructure monitoring product. However, sentry is more developer oriented on the backend and more client friendly on the front end as far as showing results and the dashboard etc. It can provide …
Sentry was cheaper and lighter weight/easier to deal with. New Relic always felt like it was slowing the site down some. I don’t think either has had any major negative impact, but Sentry always seemed better/faster. Also, Sentry doesn’t have contracts like New Relic does …
Sentry is better suited for tracking and aggregating exceptions over New Relic. New Relic does report on exceptions that occur, but Sentry is better at rolling up similar exceptions and filtering out the noise. Sentry also does a great job at identifying when an exception first …
Sentry is really a tool to be used in combination with other things, like Pingdom and PagerDuty. For those applications, Sentry is a far more full-features offering that lets you see why errors happened, not just be alerted to their occurrence. We chose it over other error …
There are quite a few players in this space, but Rollbar and Sentry seem to be the top two. I can't remember why I chose Sentry over Rollbar, but they seem pretty close in terms of features.
Bugherd is well suited to our needs because it's an intuitive tool that doesn't require a ton of training, and we are working with a development agency to improve our backend and communicate issues to developers. From what I've seen, it does require you to use Chrome, which might not be perfect for other companies but it great for us. The tool has great functionality for tracking and allows you to move bugs into stages like "doing", "done" or "backlog". The screenshot tool has been super easy to use, and when we do have a bug that requires multiple screenshots, it's easy to open up a newly submitted ticket to attach a custom screenshot. It isn't easy to track down a specific bug you've logged if there are hundreds, so be prepared to dig quite a bit if you're using it for extensive testing and find yourself trying to go back
[Sentry] is honestly an amazing product. It allows us to detect errors in real time complete with stack traces and any extra accompanying information the developer wants to provide in the alert. With the alerting into Slack it has allowed us to quickly triage and tag in people who need eyes on a specific issue. It would be really useful in any Saas product environment.
BugHerd is an easy-to-use, highly intuitive tool that fits seamlessly into our web development process. It is easy for all users to use, web developers, project managers, testers and clients. Clients are able to easily pin bugs and provide explanatory feedback that allows our team to fix what is broken and incorporate client feedback.
Truthfully, we have had very little need for BugHerd support, as the tool is intuitive and does not have many bugs of its own. They have a pretty solid help/FAQ section and their support people have been reasonably responsive the few times we have needed to contact customer support. We have had our issues resolved and questions answered.
BugHerd is more focused on web-based tools, which we needed, as opposed to app-based tools like Instabug. Jira has a much higher level of complexity and barrier to entry and didn't suit our use case.
We actually ended up using both because New Relic is a more robust overall IT infrastructure monitoring product. However, sentry is more developer oriented on the backend and more client friendly on the front end as far as showing results and the dashboard etc. It can provide product level insights that New Relic does not.
Error tracking is a must in any modern dynamic website or app. By looking into the error notifications I'm able to fix errors before anyone even has a chance to complain about them!
Surprisingly, many website issues aren't showing up in Sentry, because they don't trigger exceptions. I'm interested in seeing if I can use Sentry to catch manually-triggered exceptions for "undesirable states" that my website can find itself in. Of course, that means I have to figure out how to have my client code recognize that it's in an undesirable state...