The auto discovery is really cool. I plugged it into my network and after about an hour it had already found and mapped all of the devices on my network and threw up some alerts. The buss is running behind schedule and I am just sitting here looking at it discover everything I knew I had on the network. The Layer 2 / 3 visual Map of your Network is awesome. Review collected by and hosted on G2.com.

Initial configuration is slow especially if you want to create custom reports. The custom reports are somewhat outdated looking. Also, the need for the server to run on windows is annoying and I do not know why they could not use linux. Review collected by and hosted on G2.com.

My team is in charge of the architecture that links our on-premise Hadoop clusters to AWS data lakes. I am a Cloud Data Engineer at a large company. Forward Enterprise is great for my everyday job because it shows us how our big hybrid network works. Before, when a data pipeline broke down, we would spend hours arguing with the NetOps team over whether it was a firewall block or an application timeout. I now use their Network Query Engine (NQE) to quickly see if there is a clear path between our on-premises Kafka brokers and our AWS Redshift servers in the cloud. The "digital twin" component of the math lets me identify exactly where traffic is dropping, whether it's a Cisco ASA firewall policy or an AWS Security Group misconfiguration, without having to enter in as an admin to those devices. It has turned our troubleshooting from a frustrating guessing game into concrete, undeniable proof. Review collected by and hosted on G2.com.

The technology is quite strong yet it can be frustrating for data engineers. To start, developing bespoke NQE queries is not easy. I had to read their instructions for days simply to develop a simple script that tests the connection between our ETL servers because it utilises its own data model and syntax. I wish it came with built-in query templates that were made for popular cloud data architectures. Also, when we added Forward Enterprise's REST API to our CI/CD pipelines (we use Jenkins and Terraform to automate network checks before setting up new data clusters), the API documentation seemed a little thin, and we sometimes had trouble with timeouts when pulling topology data for our biggest and most complicated network segments. Review collected by and hosted on G2.com.

Forward Enterprise offers unrivaled visibility of our network; it generates a complete, searchable model of our entire network state. I particularly like its path analysis feature which enables us to follow precise data paths over complicated infrastructure in real time, a key aspect of troubleshooting. Review collected by and hosted on G2.com.

The first stage of data collection and modeling could be computationally intensive and time consuming, particularly in very large and heterogeneous networks. Although the knowledge is potent, the steepness of the learning curve is quite high before new users can make use of all the advanced features. Review collected by and hosted on G2.com.

What stands out to me about Forward Enterprise is how it simplifies network visibility in one place. I rely on it often, so its frequency of use is consistent in my workflow. It connects well with tools like ServiceNow and our cloud setup, which makes integration valuable. The number of features allows me to simulate changes before rollout. Implementation went fairly well, and it helped me reduce mistakes when preparing network updates. Review collected by and hosted on G2.com.

What I don’t like is that it has a lot going on, and that can make it hard to grasp in the beginning. The implementation phase was longer than expected since we had to learn many functions. Because of the high number of features, some parts remain unused in daily work. This affects frequency of use for less experienced colleagues, and it sometimes slows down tasks when we need quick results. Review collected by and hosted on G2.com.

Conversation ownership is the thing that changed everything for our team. Before Forward Enterprise a message would land in the shared inbox and three people would see it and assume one of the others was handling it. That pattern generated more client complaints than anything else in our operation and it stopped almost immediately once every conversation had a clear owner attached to it. The visibility into who is handling what and where things stand has made our team leads significantly more confident in what they can commit to during client conversations. Review collected by and hosted on G2.com.

Search across archived conversations could be faster and more precise especially when trying to pull up older threads during a live client call. Review collected by and hosted on G2.com.

The universal login experience across our entire product suite has given our users a consistency that was impossible to achieve when authentication was handled differently across different parts of our application. Single sign on across multiple products now works seamlessly and the feedback from enterprise clients who require specific SSO configurations has shifted from a recurring support conversation to something that gets set up once and never mentioned again. The rules and actions framework has also let our team implement custom authentication logic without touching core application code which has kept our security layer clean and independently maintainable. Review collected by and hosted on G2.com.

The mobile experience lags behind the desktop in ways that matter for team members who need to stay across conversations while away from their desk. Review collected by and hosted on G2.com.

I used to have to chase three different people to figure out why traffic wasn't getting to a certain location. I am talking about full path analysis, policy validation, and reachability tests from one spot. The compliance part is very good as you can validate your actual network behavior against your intended policy and it will point out the gaps without you having to search for them. I'm sitting here with a cup of cold coffee and I keep thinking about all the hours this has saved my team with audit’s alone. Review collected by and hosted on G2.com.

If you want to get true value from the tool, you are going to have to write actual SQL queries. There is no click around and see what you need option for anything beyond the basic functions. The documentation provides the “what” but doesn’t provide much detail on the “how.” Yes I know exactly what the function does but where is an example of someone using it in a real world situation. The data in the results views also truncate at times and makes no logical sense. I’m straining to look at a device name that is being cut off in the middle. Review collected by and hosted on G2.com.

I like Forward Enterprise for its proactive network validation and change impact analysis, which help ensure SLA compliance and reduce MTTR by providing end-to-end path visibility. The ability to validate configurations before deployment, reducing outages, and the pre-change validation along with deterministic network behavior analysis significantly reduce change failure rates. I find the network digital twin and intent verification especially useful in enabling safe pre-change validation and reducing production risks. Its end-to-end path analysis and multi-vendor support work very well, improving troubleshooting efficiency and SLA compliance across multiple customer environments. Once integrated, Forward Enterprise automates network modeling and validation, improving ongoing service delivery efficiency. Review collected by and hosted on G2.com.

From a service delivery view, reporting, dashboards, and customer-facing insights could be more customizable to align better with SLA reporting and executive-level visibility. Reporting can improve SLA-driven dashboards and customer-specific views to better align with service delivery KPIs. Adding executive summaries with risk scoring and an easier API/BI integration (e.g, ServiceNow) would enhance customer-facing insights and automated reporting. The initial setup is complex especially in large environments with multiple customers and vendors, requiring device onboarding and access configuration. Review collected by and hosted on G2.com.

Being a Cloud Engineer who has to deal with a complex hybrid architecture, which includes AWS, Azure, plus the old, on-premise data centers, end-to-end visibility is the most significant problem I must tackle on a daily basis. This is masterfully handled by Forward Enterprise who constructs a mathematically precise digital twin of our complete network footprint.

The Network Query Engine (NQE) is the most useful one to my workflow. It basically considers our whole infrastructure; cloud routing tables, VPC security groups, loads balancers and physical firewalls as one unified relational database, which I can query. The hop-by-hop path analysis is superior. When an application team says that there is a connectivity time out between a cloud microservice and an on-premise database, I can immediately visualize the traffic flow across our cloud transit gateways to physical switches. It actually indicates which particular rule in the Access Control List (ACL) or security group is discarding the packets, so that it no longer requires hours to logically sort through the logs before it finds the correct rule. Review collected by and hosted on G2.com.

The first onboarding and exploration stage may be very vigorous. Since the platform will be configured with read-only access, to work efficiently, the coordination of collecting all the relevant API credentials, IAM roles, and SNMP strings across multiple cloud accounts and computed devices will need extensive interdepartmental collaboration with the Security and Netops teams.

Moreover, although the Network Query Engine (NQE) is so robust, it has a steep learning curve. Custom validation checks are very specific in syntax and need a good knowledge of their proprietary form. Last, the user interface is rich, but sometimes can be overwhelming and a bit slow to display huge, multi-cloud topology maps. Review collected by and hosted on G2.com.

The best thing about Forward Enterprise is that it will keep me organized with tasks and deadlines in various departments. The features make it easy to allocate duties, arrange approvals, and keep record of which duties are pending to be done or done. It also integrates effectively with our internal messages and email systems, hence, team communication remains stable. I use it very often as I base my day to day activities on it, and nothing gets left behind. Review collected by and hosted on G2.com.

A weakness that I have identified is that establishing multiple step workflow on large projects may be time consuming. Control is provided by the number of features, but detailed task sequences create an additional workload. The process of getting complex approvals across multiple departments may slow down the process, and this at times affects my rate of use in cases where I have to initiate multiple projects simultaneously. Review collected by and hosted on G2.com.