It provides dependency analysis without needing to install any agents individually on servers across the environment. Review collected by and hosted on G2.com.

It has dns issues which I have seen shows multiple vm with same name if at all vm is migrated to other platform or ip changed Review collected by and hosted on G2.com.

network tracing and the visualisation of network topologies Review collected by and hosted on G2.com.

multiple hostnames are displayed at time for a same device Review collected by and hosted on G2.com.

It has been very helpful for us when troubleshooting certain issues, and it also supported us in redesigning our infrastructure. Review collected by and hosted on G2.com.

If Faddom could add a few more networking-related features—such as log storage, analysis, and network diagram integration with Meraki and Juniper cloud-hosted environments—then it would feel like a complete product. Review collected by and hosted on G2.com.

detect the network traffic between multiple server which helps in Migration. Review collected by and hosted on G2.com.

Multiple hostname for single server at times Review collected by and hosted on G2.com.

Once I got it installed, I like the way it discovered my environment and gave me the capability to map application dependencies. The ROI certainly looks attractive. I would like to have had more time to use it, but the installation took longer than I'd allocated for the entire POC. Once I got a Faddom tech on the phone, we were able to iron out the last few challenges, but that took almost two weeks and put me past my deadline. Review collected by and hosted on G2.com.

The documentation was complicated and often conflicting. One document led me to believe I could use a Faddom-provided AWS CloudFormation template to roll it into a test AWS VPC I set up. Faddom Support later confirmed there is no such template and I had to go back and create the VPC flow logs manually. One set of documentation indicated I should use AWS Traffic Mirror to capture the netflow data needed for dependency mapping. Faddom Support and other documentation later confirmed Traffic Mirror is not supported by Faddom and that I should use VPC Flow Logs. I also ran into some permissions issues with accessing the VPC Flow Logs. I can't say if the delay was because of AWS or because of Faddom, but the changes I made to the permissions didn't seem to propagate to Faddom in a reasonable time period. Review collected by and hosted on G2.com.

Discovery of all network traffic and analysing of routes Review collected by and hosted on G2.com.

Sometimes it gives multiple entries for single server which confuses Review collected by and hosted on G2.com.

Our customer succFrom the moment I saw the product I knew it would be a game changing service for our company. It is unlike any network discovery solution that I have personally tried in my 30+ year career in IT. Maps are definitely a game changer in terms of efficiency. The interface is easy to manage and understand. Since the implementation, I have been able to use it multiple times a week to get details about connectivity to troubleshoot problems. Our customer success support rep (Tal) has been phenomenal in helping us implement the product. Review collected by and hosted on G2.com.

It is another tool that we have in our toolbox to learn and use. It will just take time and effort to be effective. Review collected by and hosted on G2.com.

I love the dependency mapping, I love the auto server classification, but 2 of the most useful tools are under the secure tab:

1. the SSL tracking.

2. External Network discovery.

The add data source feature allows you to quickly add different virtualizations and get a holistic view of everything.

The tool is so well layed out, and is easy to use and get familiar with.

Getting up and running is very quick, and completing intitial setup is very smooth.

Dealing with Amir and Alex from Customer support is always a pleasure, with extremely quick turn arounds.

I use Faddom every day for multiple customers. Review collected by and hosted on G2.com.

I don't like the exportable reports and the small working window for server names etc., especially when trying to export the External Network List. Review collected by and hosted on G2.com.

What I like best about Faddom is its ability to provide real-time, automatic visualization of my entire IT environment without installing agents. It gives me a clear, interactive map of applications, servers, and dependencies, which makes troubleshooting and planning so much faster and more accurate. The interface is intuitive, and it saves a lot of time compared to manual documentation. Review collected by and hosted on G2.com.

One thing I dislike about Faddom is that it can sometimes feel limited when dealing with very large or highly complex environments—especially if you need deep customization or integrations with certain niche tools. While it's agentless and easy to deploy, there are occasional gaps in visibility for non-standard systems or cloud-native resources, which may require manual adjustments or workarounds. Review collected by and hosted on G2.com.

Faddom is a lightweight, agentless platform that helps organizations gain real-time visibility into their IT environments by automatically discovering and mapping application dependencies across both on-premises and cloud infrastructure. One of the most helpful aspects of Faddom is how easy it is to deploy—there’s no need to install agents or make changes to the environment. Within an hour, you can start seeing detailed application communication paths, infrastructure dependencies, and network flows.

What sets Faddom apart is its ability to provide continuously updated, visual maps that make it much easier to understand how applications are interconnected. This is especially useful for planning cloud migrations, troubleshooting outages, or validating changes during IT transformations. It’s also extremely helpful for compliance, security reviews, and business continuity planning, where having an up-to-date understanding of system interdependencies is critical.

The main upsides of using Faddom are its simplicity, speed to value, and the clarity it brings to complex environments. Instead of relying on outdated documentation or tribal knowledge, teams can now access a real-time source of truth to make better, faster decisions. It’s a solid tool for any IT organization trying to reduce risk and improve operational awareness. Review collected by and hosted on G2.com.

While Faddom brings a lot of value in terms of visibility and ease of deployment, there are a few limitations to be aware of. First, because it’s agentless and relies heavily on network traffic and protocols like SNMP and flow data, it may not capture every application dependency with full granularity—especially in environments with encrypted traffic, limited network visibility, or tightly segmented zones.

Another consideration is that Faddom is a read-only tool. It’s great for mapping and observing, but it doesn’t offer native remediation or integration with automation workflows like some more robust IT operations platforms. That means while it’s helpful for discovery, it often requires teams to pivot into other systems to take action.

Scalability can also become a factor in very large or highly distributed environments. While it works well in mid-sized environments or targeted segments of infrastructure, some users have reported challenges when trying to maintain clean, navigable maps across thousands of services or across hybrid networks with inconsistent architecture.

For what it delivers, Faddom can be seen as a niche tool—excellent for mapping and visibility, but not a full replacement for broader CMDB or AIOps platforms. That makes it most valuable when used in combination with other tools, which may increase total cost of ownership. Review collected by and hosted on G2.com.