One improvement I would suggest for JupiterOne is to make the platform's remediation workflow more tightly integrated with DevOps pipelines. For example, when JupiterOne identifies a critical misconfiguration, it could automatically create a Jira ticket or trigger a Terraform or IaC pipeline with the required remediation while maintaining approval controls for sensitive changes. This would reduce the gap between security detection and actual remediation. I can implement better real-time notifications for critical asset changes, more customizable dashboards for DevOps, security, and management separately, and deeper Terraform and IaC integration to detect issues before infrastructure is deployed.
Regarding performance and speed scenarios for JupiterOne, queries sometimes take too long, especially when dealing with large datasets or complex graph relationships that can slow down significantly. There is also a steep learning curve, as J1QL, their query language, is powerful but requires time to learn. New users struggle initially, and better onboarding tutorials are needed. Rate limiting issues can be frustrating, as API rate limits sometimes cause problems. Price transparency for JupiterOne is an area for improvement. The price is not publicly listed, so you have to contact sales for smaller teams or startups, which becomes a barrier. Another issue is alert noise, as sometimes too many alerts are generated. Better filtering and prioritization are needed so that critical issues do not get lost. JupiterOne is very good when compared to other cloud asset platforms overall.
Security Analyst at a outsourcing company with 501-1,000 employees
Real User
Top 20
Feb 16, 2026
There are some features that I have shared with our customer service manager. One of them that is relevant to us at this time is the need for better determination of unified devices. Currently, JupiterOne uses hostname weights, MAC addresses, or IP addresses to tie devices together, but we have actually requested a way for us to make those determinations ourselves. For example, when externally scanning a device using Qualys, internally it gives an IP address or FQDN, while externally it might be different. We want to be able to decide ourselves that these two devices are the same device even when they have different names and IP addresses for external and internal use. The unified devices feature is valuable and did not used to exist, and it has been fantastic. However, I believe more can be done regarding unified devices, and giving users the privilege to tie them together would be a good addition to the platform. One of the other things that interest us in JupiterOne and why we really wanted to use the tool is the compliance feature. We wanted to use it to track our compliance since we are ISO 27001 certified. However, the compliance module has not worked well, and we have had to continue tracking our compliance manually with the tools we use. Although there are some works in progress to improve the compliance part of the tool, I think if they can get it up to speed, that would be a really good improvement.
IT Specialist at a tech services company with 10,001+ employees
Real User
Sep 13, 2023
There should be more integration or an update to the visualization part of the charts or other graphs we plot. Currently, it integrates from your local directive with your local PC. If it is integrated into other platforms, that would be great. You can only write Python queries in Jupiter, not other languages, like, SQL or PySpark. Databricks is a software that provides writing queries in different languages. Jupiter should allow us to write in different languages.
JupiterOne provides automated asset management, AI-assisted queries, and graph-based visualizations to enhance security incident response and compliance mapping. It integrates with AWS, GitHub, and other tools for centralized inventory, continuous monitoring, and effective risk management.JupiterOne is recognized for its robust capabilities in asset cataloging and management, leveraging platforms such as AWS, Azure, and Microsoft M365. It facilitates automated cloud asset discovery, security...
One improvement I would suggest for JupiterOne is to make the platform's remediation workflow more tightly integrated with DevOps pipelines. For example, when JupiterOne identifies a critical misconfiguration, it could automatically create a Jira ticket or trigger a Terraform or IaC pipeline with the required remediation while maintaining approval controls for sensitive changes. This would reduce the gap between security detection and actual remediation. I can implement better real-time notifications for critical asset changes, more customizable dashboards for DevOps, security, and management separately, and deeper Terraform and IaC integration to detect issues before infrastructure is deployed.
Regarding performance and speed scenarios for JupiterOne, queries sometimes take too long, especially when dealing with large datasets or complex graph relationships that can slow down significantly. There is also a steep learning curve, as J1QL, their query language, is powerful but requires time to learn. New users struggle initially, and better onboarding tutorials are needed. Rate limiting issues can be frustrating, as API rate limits sometimes cause problems. Price transparency for JupiterOne is an area for improvement. The price is not publicly listed, so you have to contact sales for smaller teams or startups, which becomes a barrier. Another issue is alert noise, as sometimes too many alerts are generated. Better filtering and prioritization are needed so that critical issues do not get lost. JupiterOne is very good when compared to other cloud asset platforms overall.
There are some features that I have shared with our customer service manager. One of them that is relevant to us at this time is the need for better determination of unified devices. Currently, JupiterOne uses hostname weights, MAC addresses, or IP addresses to tie devices together, but we have actually requested a way for us to make those determinations ourselves. For example, when externally scanning a device using Qualys, internally it gives an IP address or FQDN, while externally it might be different. We want to be able to decide ourselves that these two devices are the same device even when they have different names and IP addresses for external and internal use. The unified devices feature is valuable and did not used to exist, and it has been fantastic. However, I believe more can be done regarding unified devices, and giving users the privilege to tie them together would be a good addition to the platform. One of the other things that interest us in JupiterOne and why we really wanted to use the tool is the compliance feature. We wanted to use it to track our compliance since we are ISO 27001 certified. However, the compliance module has not worked well, and we have had to continue tracking our compliance manually with the tools we use. Although there are some works in progress to improve the compliance part of the tool, I think if they can get it up to speed, that would be a really good improvement.
There should be more integration or an update to the visualization part of the charts or other graphs we plot. Currently, it integrates from your local directive with your local PC. If it is integrated into other platforms, that would be great. You can only write Python queries in Jupiter, not other languages, like, SQL or PySpark. Databricks is a software that provides writing queries in different languages. Jupiter should allow us to write in different languages.