Overview
Nexthink Infinity - the market's first automation and remediation platform - delivers unparalleled visibility across all environments so all IT teams can continuously improve the digital workplace to optimize productivity and cost.
Highlights
- See; Diagnose; Fix
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/36 months |
|---|---|---|
Workplace Experience | See, diagnose, and fix digital workplace issues | $2,400.00 |
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
No refunds
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Proactive endpoint insights have improved digital employee experience and reduced downtime
What is our primary use case?
My main use case for Nexthink is supporting the digital employee experience and proactively identifying and resolving endpoint issues. I use it to investigate device performance, troubleshoot issues affecting end users, and analyze endpoint data using Investigations and NQL. I also work with Remote Actions and campaigns to help automate remediation and communicate with users when needed. Overall, Nexthink gives us better visibility into what's happening on the endpoint side, so we can identify problems and resolve them more efficiently, sometimes before the end user even reports an issue.
One example would be identifying an endpoint performance issue through Nexthink before it resulted in a larger number of support incidents. We were able to use Nexthink to look at the endpoint data and identify devices that were showing performance degradation and other indicators that something wasn't functioning as expected. From there, I used the Investigation capabilities to narrow down the affected devices and understand what was happening. We were then able to take corrective action and validate the results through Nexthink. I have also been involved in testing and providing feedback on Remote Actions and automated remediation developed by our engineering teams. What I really value about Nexthink in situations like that is that we don't always have to wait for an end user to submit a ticket or visit the Tech Cafe where I work. The telemetry can help us identify a developing problem, investigate it, and take action before it becomes a much larger user-impacting issue that could affect their productivity and cause significant downtime.
What is most valuable?
Nexthink has made a positive difference by giving our IT teams much better visibility into the health and performance of our endpoints. Instead of always waiting for an end user to report a problem, we can use the data to identify issues and trends early on and determine whether something is affecting one device or potentially a larger group of users. It has also helped make troubleshooting more efficient. With Investigations, NQL, and Remote Actions, we can gather information and take certain corrective actions remotely, which can reduce the amount of manual troubleshooting required and minimize disruption for the end user.
Another benefit that I have noticed is that it helps us move forward in a more proactive support model. We can use endpoint data to make better decisions, validate whether remediation was successful, and identify recurring issues that may need a broader solution. This is usually done quite quickly. From my perspective as someone supporting the environment, I have definitely seen Nexthink improve our ability to identify, troubleshoot, and respond to end-user endpoint issues more efficiently.
What saves me the most time is being able to utilize the Remote Actions, depending on what the issue is. We recently used Remote Actions to push an update and to sync a software that we use to keep our devices compliant in the system. We often use that with their Remote Action to get that done expeditiously because on its own, the device can take some time. However, if you are able to push that update or that synchronization through Nexthink, it takes off a lot of time and downtime for the user and also keeps our process moving forward.
What needs improvement?
Nexthink has a very strong feature set, and I am still continuing to expand my experience with some of its more advanced capabilities. One area I would like to explore more deeply is Flow and the more advanced automation capabilities, particularly how different workflows and Remote Actions can be combined to create more proactive or end-to-end remediation. I also would like to continue expanding my knowledge of NQL and the analytics capabilities because there is a lot you can do with the data once you really start digging into it.
As far as something I wish it had, I don't think I have encountered a major missing feature in my day-to-day use that I would specifically call out. For me, it is more about continuing to learn and take advantage of the capabilities that are already there. The only thing I can think of is that whenever you are doing the Remote Actions when you have more than one that you are pushing out, I would like to be able to see each one of those listed versus having to go back to the main page and then list them that way. It just makes it easier to see them and determine whether or not the results were successful.
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
I haven't had a lot of direct interaction with Nexthink's customer support team because my role is primarily on the practitioner and endpoint support side. We have other team members who handle vendor support and escalation when necessary.
Which solution did I use previously and why did I switch?
What other advice do I have?
My advice would be to first have a clear understanding of what problems you are trying to solve and what you will want to accomplish with Nexthink. It is a very powerful platform, but I think you get the most value from it when you go beyond simply monitoring endpoints and really take advantage of the proactive capabilities. I would definitely recommend investing time in learning NQL, Investigations, Remote Actions, campaigns, and the automation capabilities. Those features can really help you move from a reactive support model to a more proactive one. I give Nexthink a rating of 10 out of 10.
Nexthink Workflows and AI Dashboards Deliver Huge ROI Through Fast, Hands-Off Automation
A big part of the ROI is the visual builder itself. Composing a workflow - chaining Remote Actions, branching on outputs, looping over affected machines, wiring in API calls - through the UI is dramatically faster than hand-building the same orchestration and glue code manually. What would otherwise be a scripting project becomes a drag-and-connect exercise, which means we stand up new automations in a fraction of the time and hand off maintenance far more easily than a pile of bespoke scripts.
The integration story compounds that. Being able to make external API calls mid-workflow means Nexthink isn't a silo - it becomes the automation hub tying our endpoint data to the rest of our tooling. Rather than exporting data and stitching systems together elsewhere, we reach out to external systems inline, which cuts development time and keeps the whole process in one place. Combined with branching logic and loops, we build workflows that adapt to what they find rather than running a fixed script blindly.
The AI capabilities have been a genuine accelerator too. One of the most valuable things I've done is craft a prompt for use with Workspace AI that produces complete, import-ready dashboards - rather than assembling widgets and queries by hand, I can generate a full working dashboard from a well-structured prompt and refine from there. That's taken dashboard creation from a tedious manual build to a matter of minutes, and it means less time starting from a blank page and more time on the analysis that actually matters.
Put together, the return has been concrete, automations that previously took an engineer hours of manual investigation and remediation now run automatically and consistently across our entire Windows estate, physical and virtual workstations alike. The visual builder, the integrations, and the AI assistance each cut development time, and together they let a small team punch well above its weight.
That said, none of these have been dealbreakers, and the reason they don't bother me much is Nexthink's responsiveness. When I hit a repeatable issue or a genuine gap, I report it and it either gets fixed or lands on the dev backlog as a feature request. That feedback loop matters more to me than any individual rough edge. Knowing the product is actively evolving, and that real customer pain points make it into the roadmap, counts for a lot. I'd rather use a platform that's improving in the directions its users actually need than one that's polished but static.
Concretely, we've used it to automate things that used to be painful manual jobs. We deregister retired devices from Autopilot automatically instead of clicking through the portal. We keep application packages current on our AVD session hosts by having workflows download, verify, and swap them in on login, with integrity checks and rollback so a bad download never leaves a machine broken. We check connectivity and agent state, validate configuration, flatten group membership for access management through Graph API calls, and remediate drift, all as automated workflows rather than one-off scripts. Because a workflow can chain Remote Actions, branch on their output, loop, and call external APIs, we can build a process that adapts to what it finds and acts on it end to end.
The benefit shows up in a few ways. The obvious one is time. Jobs that took an engineer hours of investigation and hands-on remediation now run on their own and finish consistently. The less obvious one is reliability. Automated workflows do the same thing every time, so we've cut out the human error that creeps in when you're doing repetitive fleet work manually. And the real-time endpoint visibility means we can catch and diagnose intermittent problems that would otherwise be gone by the time a user files a ticket. For a small team, that combination lets us cover a lot more ground than our headcount would normally allow, and it's shifted us from reacting to problems one machine at a time to solving them across the fleet in a single, repeatable process.