Jellyfish is an intelligence platform for AI-Integrated Engineering. According to the vendor, the solution assists over 1,000 companies—including DraftKings, Box, and Blue Yonder—in utilizing Artificial Intelligence to manage software development lifecycles. By aggregating engineering data and contextual intelligence, Jellyfish is designed to help Research and Development (R&D) organizations measure impact, adopt industry practices, and support decision-making across AI adoption, project…
N/A
ServiceNow DevOps
Score 8.8 out of 10
N/A
ServiceNow DevOps is designed to reduce friction between IT operations and development. This DevOps tool allows businesses to minimize risk while scaling DevOps initiatives.
N/A
Pricing
Jellyfish
ServiceNow DevOps
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Jellyfish
ServiceNow DevOps
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Jellyfish
ServiceNow DevOps
Considered Both Products
Jellyfish
Verified User
Anonymous
Chose Jellyfish
GitHub provided a lot of issues for us from an end-user point of view. Overall, Jellyfish is more intuitive; although it does come with its struggles and downfalls, these are something that just takes time to figure out. GitHub was more focused on developing metrics ONLY, and a …
The really cool thing about Jellyfish is the integrations that it has with the other tools, which are also very common within the software development industry. Consolidating all this data and being able to see graphs, numbers, and percentages in one place gives you a better …
ServiceNow DevOps is easier to use and understand, and we can manage everything in comparatively less amount of time. It's very user-friendly. Tracking activities and ticket creation is a lot better in ServiceNow DevOps
I think both pieces of software have their positives and negatives. In some ways I preferred ATOS as it had a lot more complex options for selecting what you were looking for, however, I found it more difficult to navigate. ServiceNow DevOps has felt a lot cleaner to move …
As mentioned previously, not sure if ServiceNow DevOps can handle tickets in an agile methodology, where everything is setup based on Sprints, stories and the whole agile terminology. We use OpsGenie to setup shifts for Production support teams, OpsGenie alerts people through …
I really recommend using Jellyfish; if this is something that your company is looking for, definitely give it a try. The Jellyfish team is also very responsive and supportive while updating, changing, or modifying required data. Having metrics from different tools in one place is very useful, especially when you have several engineering teams.
Well suited to plan and apply any applications using the DevOps technology. The application keeps track of all the different stages of an application built and provides adequate support.
UI and navigation aren't very intuitive and require additional research before being able to use.
The individual developer metrics are not very useful and make the interface feel cluttered.
Overall, it takes time for the end-user to truly learn how to use the platform and navigate. There is so much information/data available that although the above is a con, we felt it still made sense, despite the learning curve.
I'd like to see more interaction with email. Once a ticket is closed I'd like to have an email come to me automatically and just be able to click on something to effectively close the ticket in ServiceNow DevOps after providing closing details
I'd like in certain exceptions to be able to open tickets with time in past.
GitHub provided a lot of issues for us from an end-user point of view. Overall, Jellyfish is more intuitive; although it does come with its struggles and downfalls, these are something that just takes time to figure out. GitHub was more focused on developing metrics ONLY, and a lot of these metrics were black and white, which resulted in a failure to analyze the bigger picture. GitHub's metrics were mostly unreliable. After using Jellyfish for the past 2ish years, we love it so much better. Despite the learning curve to understand how to use the interface, overall, this provides so much more insights and analytics in a way that allows us to be strategic with our business goals.
ServiceNow DevOps is easier to use and understand, and we can manage everything in comparatively less amount of time. It's very user-friendly. Tracking activities and ticket creation is a lot better in ServiceNow DevOps