OpsGenie is an IT monitoring and incident response platform for development and operations teams, providing alerts and schedule management escalations. OpsGenie is now part of Atlassian since the late 2018 acquisition.
$0
up to 5 users
Pricing
OpsGenie
Editions & Modules
Free
$0.00
up to 5 users
Essentials
$9.00
per user/per month
Standard
$19.00
per user/per month
Enterprise
$29.00
per user/per month
Offerings
Pricing Offerings
OpsGenie
Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
OpsGenie
Ask people about this product
Oswald Schmidt• 2nd
Legacy Response Consultant at Pagac - Flatley
Skilled at Licensed Concrete Soap
Haven Koelpin• 2nd
District Markets Director at Johns, Bruen and Haag
Skilled at Rustic Granite Tuna
Nash Pfannerstill• 2nd
Regional Implementation Planner at Langosh Inc
Skilled at Refined Metal Tuna
See helpful people who have experience with this product
similar functionality to pager duty - we were able to use OpsGenie instead because of better ROI because we were adding a larger number of users than we had previously used. It seemed to scale better with our growth - we also use a few other Atlassian tools so it was nice to …
We also looked at PagerDuty but decided to go with OpsGenie as it had more features on the plan we needed compared to PagerDuty which would have required us to spend a lot more for what we felt were non-premium features. Everything felt like an add-on - automation for an …
Much more pricing friendly than PagerDuty but I haven't done the comparison in years so not sure how pricing/features stack up nowadays. Been very happy with OpsGenie.
I didn't participate in the tool selection, and I don't know other similar tools. Although I think OpsGenie suits well in all the scenarios we have, so I would choose this tools again.
Have done a POC with PagerDuty in the past when evaluating OpsGenie and just liked the clean look and feel of OpsGenie better along with their already extensive list of integrations. The integrations was probably the key deciding factor in us not going with PagerDuty at the time.