Jellyfish Software Engineering Intelligence Platform

My main use case for Jellyfish revolves around the visibility it provides for my organization and how it supports better planning and leadership conversations. As I continue using Jellyfish, I have found its biggest value is how it brings engineering delivery, team allocation, capacity, and investment priorities into one place by connecting data from tools such as Jira and GitHub, which I have been using in my organization. The dashboard makes it very easy to identify delivery risks, understand where teams are spending their time, and discuss trade-offs without manually consolidating information from multiple sources. It is especially useful for creating a shared view between engineering, product, PMO, and the leadership team in my organization.

Jellyfish helps us by bridging the gap between the engineering teams and the business teams, which has aligned our technical work with the business goals strategically. It has been very helpful because it enables us to make data-driven decisions on estimations.

Jellyfish also provides visibility into our information in a way we could not get anywhere else, as it shows where developers are actually spending their time, not just where they plan to spend it. The signals Jellyfish captures give us a clearer view of reality than our other planning tools. It enables us capital tracking without forcing us to rely on time tracking of our work.

Jellyfish positively impacts my organization by enhancing team collaboration, providing visibility, and facilitating effective communication within engineering teams. I love it because we can track time and enhance team efficiency through the fantastic metrics in Jellyfish. It allows us to make data-driven decisions more easily. I appreciate it because Jellyfish helps identify issues that hinder effectiveness, calling for more flexible dashboards and improved data accuracy.

Jellyfish has been helpful, especially in my engineering team, in improving productivity by giving us better visibility into development work and helping us identify bottlenecks. I estimate that it has reduced time spent on manual reporting and progress tracking by around twenty percent, allowing my fellow engineers and managers to focus more on development priorities and deliver projects more efficiently.

The best features Jellyfish offers include fantastic metrics, enhanced team collaboration, robust metrics analysis, valuable insights, and an intuitive user interface. I love its very flexible dashboards.

The metrics analysis in Jellyfish facilitates effective tracking and optimization of team performance, which helps us. Valuable insights and an intuitive user interface enhance visibility and performance tracking in our engineering department. I find Jellyfish extremely easy to use and appreciate its intuitive user interface and effortless tracking features.

Jellyfish has been able to handle our data privacy and security very well; its governance and security are excellent.

Jellyfish's AI capabilities are generally reliable and provide useful insights into engineering productivity, resource allocation, and workflow efficiency.

I find the custom dashboarding challenging, although I acknowledge that the team is moving in the right direction.

Sometimes I need to engage support to fix data pulls from GitHub and Jira, but they resolve these issues very quickly.

More customizable or role-focused views will make it easier to surface what is most relevant without extra filtering.

I have been using Jellyfish for two years.

Jellyfish is very stable and reliable in our day-to-day use. The dashboard and engineering analytics work well for tracking productivity, project progress, and resource allocation, and we have experienced minimal disruptions; therefore, the platform provides consistent insights for decision-making.

The scalability of Jellyfish is top-notch because it has been able to scale well with our team's growing engineering activities and reporting needs.

Customer support has been very influential and helpful, as the team provided useful guidance during setup and configuration, and also helped address questions about integration and reporting very well. I would rate customer support nine out of ten.

We did not use another solution, as we did not switch from any.

Deploying Jellyfish is relatively easy with a straightforward setup process and useful integration with our existing engineering tools.

As IT personnel and software engineer, my experience with the configuration process was generally straightforward. Connecting Jellyfish to our existing development tools and setting up dashboards is manageable, and the platform provides useful visibility into our engineering metrics.

Jellyfish integrates reasonably well with our engineering tools and AWS-based environment, helping us gain better visibility into development activities and engineering performance.

Having Jellyfish in our organization has shown us more positive returns than negative; we have seen a positive return on investment mainly through improved engineering visibility and reduced manual reporting. We estimate that it saves around twenty percent of the time previously spent on reporting and progress tracking, allowing engineers and managers to focus more on development work, which has been very helpful in identifying bottlenecks and allocating resources more effectively.

The procurement process for Jellyfish was relatively straightforward. Jellyfish's billing experience is generally straightforward, and the pricing and licensing are manageable once the plan and contract terms are understood. My experience with pricing, setup cost, and licensing is that everything was very manageable, although the overall cost required careful evaluation against expected business value. The setup cost was reasonable, and the implementation did not require significant additional resources, hence everything was straightforward and fell into place within a short period.

We evaluated tools such as Linear B and GitLab Analytics before choosing Jellyfish.

I would rate Jellyfish nine out of ten or five out of five. Jellyfish has been really helpful, especially in my engineering department, by tracking where QA and automation work is going, identifying bottlenecks in the development workflow, and solving the lack of visibility between testing work and broader engineering priorities. I recommend Jellyfish to any organization looking to improve engineering visibility, productivity, and resource allocation. Before adopting it, make sure you identify your key performance metrics, ensure your development tools are properly integrated, and involve engineering managers in the setup process. Take time to customize your dashboards and review the insights regularly. Also, evaluate the pricing against your team's needs and expected return on investment to ensure you get the most value from the platform. My overall rating for Jellyfish is nine out of ten.

Amazon Web Services (AWS)

What do you like best about the product?

The AI insights built within the product takes the heavy lifting of evaluating the data off of the user. The UI is fairly straightforward with pleasing visuals throughout the product. Pulling data from our disparate systems and present a full picture across our engineering organization in one place is a big win. When I do have to deal with the support team, they have been prompt and helpful in resolving my issues.

What do you dislike about the product?

The biggest issue I have with Jellyfish is how it attributes work done by engineers as AI assisted work. It's really making a guess based on if there are AI signals the day that they do a PR which isn't really a great determination in my opinion. Not having the ability to designate static teams has also been a problem when we have teams that are support teams who's work spans multiple JIRA projects.

What problems is the product solving and how is that benefiting you?

Before I had to go to disparate systems such as JIRA, GitLab, Github, and Linear to get data to understand our engineering team's performance. Now I can go to Jellyfish to have those data and metrics aggregated under one platform to understand the teams and organization's performance.

What do you like best about the product?

Jellyfish helps me know where I stand in AI usage and lets me see the usage of my teammates as well. It's useful for understanding how much I depend on AI. I find all the features good, and the initial setup with SSO login was easy.

What do you dislike about the product?

Nothing

What problems is the product solving and how is that benefiting you?

I use Jellyfish to track AI usage, helping me understand my dependency and where I stand. It also lets me see my team's usage, which is useful.

What do you like best about the product?

the ability to quickly view my team's progress in metrics we are tracking.

What do you dislike about the product?

sometimes the interface can be clunky and dificult to navigate. I have to know where I am going to get what I need.

What problems is the product solving and how is that benefiting you?

it is giving me visibility into how my teams are performing

What do you like best about the product?

The effort-based allocation model is the standout. Jellyfish translates raw development activity into an FTE-equivalent split across investment categories (Growth, KTLO, Support) based on actual effort signals rather than ticket counts — which is critical, because counting issues badly misrepresents real work. This is what made my monthly CEO and board reporting credible: leadership could trust an "X FTE went to Growth this month" figure because it reflected effort, not just Jira volume. The mapping of investment categories to our own strategy taxonomy and the month-over-month trend views also let me show direction over time with minimal manual assembly, and the delivery and AI-assisted PR metrics fed our AI-adoption reporting well.

What do you dislike about the product?

The biggest frustration is the newer AI impact reports: there's no way to export the underlying data to CSV. The reports render fine in the UI, but if you need the numbers for your own analysis — cohort breakdowns, month-over-month trends, feeding an executive deck — you're stuck. You can look at the data but you can't take it with you, so getting it into a usable format means manual extraction rather than a simple download. For a metrics platform whose whole value is helping you report, locking the data inside the dashboard defeats the purpose.
On top of that, I've seen the per-tool detail figures and their aggregate rollups diverge by around 10 percentage points, which is a real problem when the aggregate is the number going in front of the board. Both issues are workable, but they add reconciliation and extraction steps to what should be a clean pull.

What problems is the product solving and how is that benefiting you?

It answers the core question my leadership asks every month: where is engineering effort actually going, and is it aligned to strategy? The FTE allocation across Growth/KTLO/Support gives me a defensible, repeatable way to report that, plus the delivery and AI-assisted-development metrics I need to show whether our tooling investment is moving velocity. The benefit is a monthly executive narrative grounded in effort data rather than anecdote or raw counts.