Jellyfish Software Engineering Intelligence Platform logo

    Jellyfish Software Engineering Intelligence Platform

    Sold by
    Jellyfish is the leading intelligence platform for AI-Integrated engineering, helping more than 1000 companies including DraftKings, Box and Blue Yonder, leverage AI to transform how they build software. By combining the deepest engineering dataset with context-rich intelligence, Jellyfish helps R&D organizations understand what is driving impact, adopt proven industry best practices, and make smarter decisions across AI adoption, planning, delivery, and engineering performance. Learn more at jellyfish.co

    Ratings and reviews

    4.5
    442 ratings
    69%
    28%
    2%
    1%
    0%
    2 AWS reviews
    |
    440 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (442)
    Anshuman K.

    High-Level CxO Reporting Powered by JIRA and Git Insights

    Reviewed on Nov 19, 2026
    Review provided by G2
    What do you like best about the product?
    A single, high-level view of reporting for CxOs, while also helping drive different Agile teams using facts pulled from JIRA and Git.
    What do you dislike about the product?
    This new AI Data Hub isn’t providing the same feature set and dashboards I had before. The AI controls and the correctness of the AI data feel questionable, especially with the AI tool–generated dashboards.
    What problems is the product solving and how is that benefiting you?
    Resource allocation, release status, and critical delivery tracking are all available with a single click, making it easy for anyone to access at any time.
    Alan Eduardo

    Portfolio visibility has improved with structured workflows, but custom metrics still need work

    Reviewed on Nov 18, 2026
    Review provided by PeerSpot

    What is our primary use case?

    I was in charge of a Jira migration, and I was also in charge of bringing a new work portfolio management process to the company at the same time. We migrated from Jira on-premise to Jira Cloud and took advantage of that moment to implement Flight Levels portfolio management. I created workflows for Flight Levels Three, Two, and One: strategic, coordination, and operational. At that moment, a colleague told me about Jellyfish. I found it really interesting, especially for the process and planning part, cycle time, and business alignment, because those were the core of what we were doing at that time. My colleague also looked at other aspects, such as DevEx.

    After the migration, once we had created the workflows and migrated all the teams, my colleague and I started to hydrate Jellyfish with information from Jira. This is mainly the reason I did not spend much time using Jellyfish: Jira was already delivering everything I was looking for. Other information I was looking forward to seeing was not easy to track in the company at that moment, because people were either not filling it in correctly or the information was mostly out of date. I do not think this is a flaw of Jellyfish. I think it reflects the moment the company was in. We were migrating services, and people were getting used to the new Jira and the new process, including connecting work inside the new structure. At that moment, Jira provided the portfolio management information, and it did so more properly because it was inside Jira. I had to tweak things more in Jellyfish and do some parsing. My colleague was really looking forward to the DevEx part and kept working towards it, but I never heard anything about it again.

    This is basically my story with Jellyfish. I think it is a great idea, and there are lots of cool features in the app, no doubt about that. However, I am talking about almost two years ago, so Jellyfish may be a little better now in some aspects, such as connecting with the teams or helping to connect things. At that moment, Jellyfish was a little expensive, not in price but in time, because Jira and Atlassian were providing all the information I was expecting to see. The whole Atlassian suite provided connections with Goals, Projects, priorities, strategy, and other things.

    My colleague integrated Jellyfish with GitHub, I think for PRs.

    What is most valuable?

    Predictive capabilities were the ones I tried to use, but we did not have enough data, or the data was not as up to date as it could have been.

    In terms of performance indicators, I saw a couple of them in Jellyfish, such as lead time, cycle time, and other metrics in that sense. They were helpful, but those are metrics that I could also extract from Jira. I think the UX in Jellyfish was visually better, especially the charts. We had almost 30 teams, and we could drill down into the metrics for each team, which is great. It was super helpful.

    For how long have I used the solution?

    I used Jellyfish for a short time. In my specific case, it was a month or two. However, I had a colleague who kept working with Jellyfish for longer afterwards.

    What do I think about the stability of the solution?

    I did not experience any stability issues with Jellyfish. The experience was always good. That is what left me a little heartbroken, because I saw really cool features and it was working well, but I could not manage to work with it.

    What do I think about the scalability of the solution?

    I do not know how Jellyfish is now, but at that moment, I felt that some of its features and metrics were market metrics, meaning they are very well known and widely spread in the market. I know there are ways to add new metrics, but I felt that if you want a custom metric, it was not easy. The UI/UX at that moment was a little bit like saying, "This is the market metrics. You can fill them in and look at them."

    I am raising this under scalability because a company with a specialized process could find this a little tricky. You need to make some concessions, and in terms of process, this tends to degrade a little over time. In our case, this was not much of an issue because we were tailoring a new process.

    In comparison with Jira, I think Jira is so broad that a person who does not understand the tool or its capabilities could be a little lost among the many possibilities. Jellyfish is a little more narrow, so there are pros and cons. My point about scalability is that the narrowness of Jellyfish could cause some degradation of the process over time. This is only my assumption, as I used it for just a month, but it is what I saw. Perhaps Jellyfish is more versatile than that, but this is my perception.

    How was the initial setup?

    My colleague was in charge of the installation and can tell you more about the initial deployment of Jellyfish. As far as I saw, it was not as tricky as it could have been.

    The maintenance I did was trying to figure out a way to keep the information up to date, which I mentioned earlier, but this is not really a Jellyfish issue. In terms of maintenance on Jellyfish itself, it was super straightforward.

    What's my experience with pricing, setup cost, and licensing?

    My colleague and I were using the Free version of Jellyfish.

    What other advice do I have?

    Putting information into Jellyfish and tracking it was easy, because I think the integrations worked really well. The problem was process-wise: keeping things updated in order to take more advantage of the features. For example, for DevEx, if you want to understand whether a capability is being used, such as Code Reviews or cycle times inside the Developer Experience, you need to be more granular and have specific metrics to feed Jellyfish. At that moment, we were not mature enough for this.

    My overall score for Jellyfish is a Seven out of 10. In my desire, it would be a Nine or even higher, but I gave a Seven because I could not manage to test and use all the features I wanted to. The ones I used were cool. I think a Seven is a good score for this.

    Rashmi Ranjan D.

    Great Cross-Platform Data Consolidation

    Reviewed on Nov 17, 2026
    Review provided by G2
    What do you like best about the product?
    I like the way it accumulates data across platforms.
    What do you dislike about the product?
    It doesn’t account for some internal factors. For example, certain teams may depend on other teams for reviews, which can extend the overall review lifecycle, and that isn’t considered.

    Secondly, in some weeks we’re more involved in refinement and architecture/design discussions rather than commits and coding, and it doesn’t consider that either.
    What problems is the product solving and how is that benefiting you?
    It provides clear performance metrics, and it helps me improve my own work by showing where I can do better.
    Hospital & Health Care

    Clean, Vibrant Visuals—But Needs More Sprint-Friendly Customization

    Reviewed on Nov 16, 2026
    Review provided by G2
    What do you like best about the product?
    I like how the data is visually represented in a clean and vibrant fashion, making it easy to see the information rather than having a bunch of numbers on a spreadsheet.
    What do you dislike about the product?
    I wish there was more customization options, for example being able to filter things by sprints. Also, the date picker forces a Monday to Friday system, which doesn't always align with sprints.
    What problems is the product solving and how is that benefiting you?
    They have been doing a lot with AI which helps to make custom dashboards, though its potential is limited
    Lorand L.

    Custom Dashboards Clarify Project Health, Though SQL Can Time Out

    Reviewed on Nov 13, 2026
    Review provided by G2
    What do you like best about the product?
    I like that Jellyfish is fully customizable. I can use the data to build the dashboards I want, access data from other features, and experiment. I also like the delivery functionality. My team looks at it at the beginning of each week to discuss project status, and I can see in one place whether projects are on track or at risk, or if I need to step in. The initial setup was quite simple. I’ve been using Jellyfish for a long time, and I think it’s a really great tool.
    What do you dislike about the product?
    When I run SQL queries in Data Hub, I suspect the data isn’t indexed. Complex queries across multiple tables sometimes time out, so I have to be very conscious about writing effective queries, which can be hard because of how the data is structured.
    What problems is the product solving and how is that benefiting you?
    I can create a single dashboard with all the information I need about my team’s health and delivery.
    Higher Education

    Great for Tracking Jira Tickets and Comparing Team Performance

    Reviewed on Nov 11, 2026
    Review provided by G2
    What do you like best about the product?
    Tracks Jira tickets, completion times, comparison across teams
    What do you dislike about the product?
    number of clicks needed to view self summary, delay in updating PR changes/comments stats
    What problems is the product solving and how is that benefiting you?
    metric goals are useful to benchmark myself
    Computer Software

    Great Data Integrations, but Dashboard Creation Feels Restrictive

    Reviewed on Nov 03, 2026
    Review provided by G2
    What do you like best about the product?
    I like that it integrates with various data platforms (Jira, IncidentIO, Gitlab), makes sense of the data and combines the data well behind the scenes.
    What do you dislike about the product?
    Dashboard creation is very restricted. Even with latest custom metrics, there is still a long way to go.
    What problems is the product solving and how is that benefiting you?
    One dashboard to rule them all. Gentle guidance towards industry metrics without being very prescriptive.
    Pawan V.

    Great Graphs and Visualizations for Tracking Progress

    Reviewed on Nov 03, 2026
    Review provided by G2
    What do you like best about the product?
    graphs and representations good way to see progress
    What do you dislike about the product?
    navigation sometimes confusing, but not overall its good
    What problems is the product solving and how is that benefiting you?
    to track our daily progress, it helps improving skills
    Michael B.

    Excellent Insights for PR & Issue Cycle Time and Team Performance Reporting

    Reviewed on Nov 02, 2026
    Review provided by G2
    What do you like best about the product?
    Insights on PR Cycle time, Issue cycles time, CapX, and Team performance in general are my favorite features I use on a regular basis. I love the MCP so I incorporate this data into my own reporting and presentations.
    What do you dislike about the product?
    I wish I had QA cycle aspects involved, since some of it is QA engineering and it would be nice to have KPIs here.
    What problems is the product solving and how is that benefiting you?
    I want to get us to a place where we are comparable to industry standard benchmarks - this helps gauge where we need to go.
    Karthiga S.

    Actionable Engineering Insights with Powerful Drill-Down Visibility

    Reviewed on Nov 02, 2026
    Review provided by G2
    What do you like best about the product?
    What I like best about Jellyfish is its ability to bring engineering data together in one place and turn it into meaningful, actionable insights. The visibility into engineering capacity, investment allocation, delivery performance, and team productivity makes it easier for Product and Engineering leaders to make informed decisions. I also appreciate the ability to drill down from high-level executive metrics to team-level details, identify bottlenecks, and have data-driven conversations around continuous improvement and business outcomes.
    What do you dislike about the product?
    While Jellyfish provides valuable insights, there are opportunities to improve the user experience. Some dashboards and reports could be more intuitive and easier to customize, particularly when trying to get specific views for different leadership audiences. At times, interpreting metrics requires additional context to ensure they are not viewed in isolation. I would also like to see more flexibility in reporting, easier drill-down capabilities, and stronger integration with Product metrics to better connect engineering activity with customer and business outcomes.
    What problems is the product solving and how is that benefiting you?
    Jellyfish helps solve the challenge of having engineering data spread across multiple tools without a consolidated view of team performance, capacity, investment, and delivery outcomes. It provides a centralized, data-driven view of how Engineering teams spend their time, where investments are going, how effectively work is flowing, and where potential bottlenecks exist.