As the IT Director, the main usage that we have is mostly IT related. We use it as a weekly tool for us, and it is one of the most important tools that we have. This is how we automate most of what we do in IT.

Our onboarding and offboarding processes are automated through Torq. Over time, we built a large and complex automation tree with many branches, and today most of the employee lifecycle actions are handled via Torq.

In addition, we use Torq for bots and just-in-time (JIT) access in several scenarios. One aspect is access to systems and credentials, and another is network-level access. From a network perspective, we integrated Torq with Zscaler’s Zero Trust solution, which allows us to fully control network access using automations and a request portal.

We use Torq together with Apono for permission requests. When a developer needs access, they request it through Apono, and Torq orchestrates everything behind the scenes. Torq dynamically opens access to the specific requested resource via Zscaler. Even if a user is entitled to a resource, they only receive actual access once it is explicitly requested and approved, and the access is granted automatically and temporarily.

This helped us get to a much more secure state and use just-in-time access very easily. We are very happy with this architecture.

It is hard to point to a single best feature because we have been using Torq for a long time and are very familiar with the platform. There was a learning curve at the beginning, and Torq was a bit different back then, but once we got used to it, it became very natural to work with.

What I appreciate the most is the flexibility. There are essentially endless possibilities with Torq, and you can do almost anything with it. The main limitation is not the platform itself, but the vision. If you do not have a clear idea of what you want to build, it can be hard to execute. However, if you know what you want to do, in most cases you can implement it with Torq. This is one of the things I value the most about the product.

Over the years, Torq significantly improved the user experience. The UI became much more comfortable to work with, and they added more triggers and forms that make building workflows easier. They also introduced the AI agent, which we use mainly to aggregate notifications, although it can be used for many other scenarios. In general, the platform offers a wide range of integrations, which makes it very convenient to use.

We work with them quite often, so we have a direct line regarding areas in Torq that have room for improvement. If we have a feature request, we can request it. I do not have anything in mind at the moment.

We were a design partner for a short while, so we feel that they listen and that users of the system have an impact on the way the system is designed for the better.

They have a new community, which is something that I personally suggested years ago. There are many people like me in different places and they might have already built the workflow that I need. Having the option to share workflows or to jump on a thread and say I have this need, did anyone ever build a workflow for it, is amazing. Someone would jump in and say yes, sure, here, take this workflow. I think this is an amazing thing and I really hope that the community will come alive because I think this is really powerful. This is something that I already suggested and it did happen eventually, and I am quite happy with it.

I do not have any specific feature in mind that I have a need for at the moment.

I have been using Torq for the third or fourth year.

We never had any issue with the system regarding stability. I would give it a definite 10.

In terms of scalability and the ability to grow within our environment, the answer is definitely yes. Torq scales very well and fits our business requirements, with plenty of room to grow.

I would rate its scalability a 10 out of 10, mainly because I honestly do not know what the upper limit is, and I am confident that we are not anywhere close to it. For our specific use cases, I highly doubt that we would ever reach any scalability limits.

We have not used them too much officially as support because we had a good relationship with Torq. We got a lot of help, especially at the start a few years back. We do not use support too much, but when we used support, it was good. I would say 10.

Before Torq, we used a limited amount of automation with other tools. These were mostly more consumer-grade solutions and were used on a relatively small scale. For example, we used tools like Zapier and Make to handle simple workflows, such as collecting information from a Google Form and pushing it into a Google Sheet.

Those tools worked fine for basic use cases, but we never took them much further than that. Once we started using Torq, we felt much more confident in the platform’s capabilities, especially from a security perspective. Torq made a much stronger impression on us and allowed us to unlock value much faster than with the tools we were using before.

I never tried to replicate what we did with Torq with Zapier. To be honest, even if I were to migrate tomorrow to Zapier, I am not sure that we can replicate what we are doing with Torq. There are other tools that we can probably do that, like N8N, for example, which I think is quite similar on the UI side of it. I do not know on the backend side of it, but i'm sure there are some tools that we have not explored that might be similar.

The ones that we used before, I do not think that we could have unlocked the same value.

There were no challenges regarding the deployment itself and it was easy.

The question here was how many users are using Torq in the organization

Initially, there were four users consisting of me and my IT team. We were the primary users and used Torq across the organization, supporting many departments through IT-owned automations.

IT team was the only group working directly with Torq, and we used it as a centralized automation platform for every use case we had that we were able to automate. More recently, around mid-2025, we started seeing increased interest in automation across the organization. This was partly driven by broader exposure to tools like n8n, which made more people curious about building automations themselves. As a result, we began running demonstrations for different departments and gradually adding more users to Torq so they could experiment with the platform. The goal is to enable teams to automate their own or their department-specific tasks without always going through IT.

At this point, we have approximately 20 users actively set up in Torq

Regarding pricing, it is a hard question.

Initially when we started with Torq, I was not the one who purchased it. Ever since then, we already unlocked value within Torq, and it has room in the budget, so we renew it every year. We renew it because we want to continue building on the work we have put into it and we are very happy with it.

I do not know because we have not checked different solutions at the moment. I cannot tell you if they are expensive or not. Are they more expensive than Zapier? Yes, but I do not think it is the same category.

Overall, I would rate Torq a 10.

When it comes to Torq’s approach to AI and SOC automation compared to other solutions in our security stack, it is hard for me to give a very strong opinion. Like most companies today, Torq is evolving its AI capabilities, and AI is being added across many areas. From what I can see, they are generally on par with other solutions at this stage.

It is worth noting that we mainly use Torq for its automation capabilities and workflow builder. We do not use their case management functionality. We do use some of their AI-related features, such as the AI agent. I am also aware of other AI components like Socrates for case management, but that is not something we currently use. Overall, AI in this space is still evolving everywhere, and it is difficult to clearly differentiate vendors at this point.

From a practical perspective, the safest and most valuable use of AI for us today is around information handling, aggregation, summarization, and notifications. These are areas where AI can reliably save time. There is still no way to guarantee fully consistent or deterministic outcomes from AI, so we are very cautious about where we use it. For example, I would never use AI in a critical workflow like offboarding a user, because I cannot fully guarantee the results. That applies to any AI model, not just Torq’s.

Where AI has been a real game-changer for us is in simplifying workflows. In the past, sending a Slack message based on multiple data points required many steps to collect, process, and format the information. With the Torq AI agent, we can sometimes replace five or ten steps with a single AI step that aggregates the data and acts on it. This has significantly reduced complexity and saved a lot of time.

From a security perspective, I found Torq is especially useful for large-scale manual remediation (Instead of writing and running scripts). For example, during a security incident where we needed to rotate keys or change settings at scale, such as in GitHub, Torq allowed us to do this efficiently through automation. This is not fully automatic remediation, but rather manual remediation executed at scale using automation. For fully automatic remediation, we rely more on specialized security tools but they are limited each one to it's own specialized field.

In terms of time to value, it took me some time to fully appreciate Torq. I was not the one who initially brought it into the organization; my manager did. At first, I was somewhat resistant, without a strong reason. There was also a learning curve, although Torq helped mitigate it. Once I started using the system seriously and understood its potential, it completely changed how we operate in IT.

Today, the entire IT team uses Torq. We may not use it daily, but on a weekly basis we are constantly looking for new things to automate. Torq is used even in production and is deeply integrated into how the IT department works. When we evaluate new tools or solutions, we always think about how Torq can be used to automate processes around them if native automation is missing.

Even though IT may not be Torq’s primary target audience, it has become a core platform for us. It significantly increased our capabilities and responsiveness, and it is something I believe should be a staple in IT departments. We are extremely happy with the system, which is why I give Torq an overall rating of 10.