Jellyfish
JellyfishExternal reviews
425 reviews
from
External reviews are not included in the AWS star rating for the product.
Must-have engineering intelligence platform
What do you like best about the product?
It's an invaluable tool for engineering leaders seeking to understand the environment in which their teams work. It enables tracking of trends across various investment types, such as Growth, Support, and Technical, while also providing analysis of SDLC bottlenecks and overall efficiency metrics. This helps leaders determine the right moments and areas for intervention.
What do you dislike about the product?
There’s nothing I dislike about it. I do think there are a few additional features that could be added to save time, but overall, it’s a comprehensive and useful tool when used for the right purposes.
What problems is the product solving and how is that benefiting you?
Understand and visualise with data my teams pressure points and bottlenecks. Visualising trends across quarters
Clear visibility into engineering work and priorities
What do you like best about the product?
I really like being able to check team metrics such as velocity and cycle time, which helps me identify trends early and adapt quickly. Jellyfish gives our team a clear, data-driven view of engineering investments and progress. It makes it much easier to align engineering work with company priorities and to communicate impact with leadership. I also appreciate the intuitive dashboards, which make complex development analytics easy to understand, and the Jira integration that saves time on manual reporting.
What do you dislike about the product?
While Jellyfish is powerful, there can be a learning curve at the beginning, especially when setting up integrations and customizing views. Some of the reports could offer more flexibility in filtering or drilling down into details. That said, the support team is responsive and actively improves the product based on feedback.
What problems is the product solving and how is that benefiting you?
Jellyfish is helping us track and analyze engineering team performance in real time. By monitoring metrics such as velocity, cycle time, and work distribution, I'm able to identify trends early, detect potential bottlenecks, and adapt quickly. This visibility ensures that engineering work stays aligned with business priorities and makes it easier to communicate impact to leadership. The tool reduces the need for manual reporting and provides a single source of truth for data-driven decisions.
Easy to use tool, offers great insight into how the organization and each team is performing
What do you like best about the product?
Love the visibility the tool provides and how easy it is to use!!! We are able to look at each team more objectively. Each team has the same metrics, with some variance based on the way the teams work (scum, scrumban, kanban, etc) . I love that the tool keeps improving at a pretty rapid pace, and they are so welcoming of ideas and feedback to make Jellyfish even better! The support team is super helpful, and communicates well as they work to resolve issues.
What do you dislike about the product?
Sometimes the teams don't like the visibility.... Also, managers have a lot on their plate and may not be leveraging the tool as effectively as they can so I wonder if we are getting as much value as we could be (but that is on us, not JF).
What problems is the product solving and how is that benefiting you?
helping teams with accountability. We have great baseline data so when teams want to change up how they work, they have lots of flexibility as long as they are improving metrics and not going backward. Also, giving us insight into how well our AI tools are working for us (or not), giving us better insight to make decisions.
When we aren't actively looking at Jellyfish data sometimes the teams aren't as diligent about delivering upon their commitments. Jellyfish has helped us to improve our predictability with the level of visibility/transparency
When we aren't actively looking at Jellyfish data sometimes the teams aren't as diligent about delivering upon their commitments. Jellyfish has helped us to improve our predictability with the level of visibility/transparency
Jellyfish enhances strategic decision-making with insightful engineering metrics.
What do you like best about the product?
What I like about Jellyfish is how its engineering metrics surface trends that help us spot issues and opportunities early. It enables more targeted conversations that drive real improvements in operational outcomes. The new DevEx features are especially valuable—they highlight areas of stress or overload, which helps us boost both productivity and developer well-being.
What do you dislike about the product?
What I dislike about Jellyfish has mostly been around user administration. Progress has been made to address those concerns, though some work still remains.
What problems is the product solving and how is that benefiting you?
Jellyfish helps solve the problem of visibility into engineering work. It surfaces trends and metrics that make it easier to identify bottlenecks, stress points, or misalignment early. This benefits me by enabling more targeted conversations with teams, improving operational outcomes, and supporting both productivity and developer well-being.
Versatile tool for both engineering and strategy product planning
What do you like best about the product?
Jellyfish has become an essential part of my workflow not only to understand engingeering operations but also as help to shaping early product strategy. Its core lies in surfacing engineering metrics but I found immense value using it to estimate new product concepts and MVP efforts as well.
We can set more realistic expectations and improve cross-functional alignment early in concept phase.
The interface is easy to use and various academy courses are helpful if you just starting to use it.
As we work in a product portfolio (over 12 products) the tool helps to bridge the gap between product and engineering in a data-driven, actionable way and allow us to validate whether teams cant take on MVPs without disrupting core roadmap items.
We can set more realistic expectations and improve cross-functional alignment early in concept phase.
The interface is easy to use and various academy courses are helpful if you just starting to use it.
As we work in a product portfolio (over 12 products) the tool helps to bridge the gap between product and engineering in a data-driven, actionable way and allow us to validate whether teams cant take on MVPs without disrupting core roadmap items.
What do you dislike about the product?
Occsionally some learning curve in advanced custom views, but nothing much
What problems is the product solving and how is that benefiting you?
- helping to anwser critical questions about visibility gap: can we deliver this MVP without derailing core roadmap items, are we investigating in the right areas
-for me specifically early-stage estiamtion and scopting of new product concept using real data on past initatives and current capacity
- accurate MVP planning, stronger alignment and in general less friction between teams and leadership
- apart from this of course resource allocation, reducing delivery risk and overall driving better product outcomes
-for me specifically early-stage estiamtion and scopting of new product concept using real data on past initatives and current capacity
- accurate MVP planning, stronger alignment and in general less friction between teams and leadership
- apart from this of course resource allocation, reducing delivery risk and overall driving better product outcomes
Very useful to track several engineering metrics and performance
What do you like best about the product?
It's easy to see metrics for the whole team but also individual.
What do you dislike about the product?
Sometimes the UI gets confusing to find the right information.
What problems is the product solving and how is that benefiting you?
Visibility on DORA metrics, and how engineers are working in general (PR merge time, etc)
Great functionality with simple yet powerful design
What do you like best about the product?
There is a good selection of various metrics and dashboards, which helps me identify areas where our work can be improved. The platform offers great functionalities within a fairly intuitive interface.
What do you dislike about the product?
It's difficult to say for sure, but I think improved integration with Intellij Junie, if that's possible, would be a great addition.
What problems is the product solving and how is that benefiting you?
It is helping me in unblocking my team members in their daily challenges but also helps me to find places where we are stuck or what is our bottleneck which we should analyse during Retros.
Great tool for managing engineering performance and visibility
What do you like best about the product?
Jellyfish provides a holistic view of my team’s work across PRs, issues, and KPIs. I especially like how it helps track AI usage, unlinked PRs, and resolved issues all in one place. It makes it easier to manage productivity, identify gaps, and have data-driven conversations with my team.
What do you dislike about the product?
Some dashboards can feel a bit rigid, and it takes time to configure reports exactly the way I want.
What problems is the product solving and how is that benefiting you?
Jellyfish centralizes engineering metrics like PRs, issues, and AI usage, saving me time and giving a clear view of team performance. It helps me spot bottlenecks, celebrate wins, and make data-driven decisions faster.
Efficient engineering visibility with minor learning curve
What do you like best about the product?
Jellyfish offers excellent visibility into engineering operations by providing clear metrics around resource allocation, delivery performance, and team alignment with strategic initiatives. Its integrations with tools like Jira and GitHub make it easy to pull in data without any manual effort. The visual dashboards are intuitive and help stakeholders understand engineering productivity in a language that makes sense to both technical and non-technical teams. It’s especially useful for engineering leaders aiming to improve planning, track investments, and justify priorities across business units.
What do you dislike about the product?
While the platform is powerful, there’s a learning curve involved especially during the initial setup and dashboard configuration. Some customization options can feel limited unless you’re working closely with their support team. Additionally, depending on how your team structures Jira projects, data hygiene and tagging become crucial, which might require some internal process changes. That said, once set up correctly, the value becomes apparent.
What problems is the product solving and how is that benefiting you?
Jellyfish helps us bring transparency and alignment between engineering efforts and business objectives. Before Jellyfish, it was difficult to quantify how much time was being spent on innovation vs. maintenance or support. Now, with integrated dashboards pulling from Jira and GitHub, we can clearly identify team allocations, delivery bottlenecks, and investment areas. This has improved decision-making for sprint planning, hiring needs, and communicating progress to stakeholders in a language they understand.
The best DORA metrics tool out there
What do you like best about the product?
As an engineering manager Jellyfish helps me enable the correct conversations with other engineering managers and executives. It's not like "oh your issue cycle time so low, your performance is low" but more like "what's making your issue cycle time be low compared to other teams?" Plug in Jira and GitLab. Make it work seamlessly. It works like a charm and we use it every week.
I haven't had to contact customer support yet because I haven't faced bugs. Maybe the only little thing is that some synchronizations take up to 24 hours to be reflected.
I haven't had to contact customer support yet because I haven't faced bugs. Maybe the only little thing is that some synchronizations take up to 24 hours to be reflected.
What do you dislike about the product?
Some syncrhonizations take up to 24 hours to be reflected, but that's just something minor given our use is weekly.
What problems is the product solving and how is that benefiting you?
Setting up a good dashboard to standardize DORA metrics measurement across teams is very hard.
showing 91 - 100