Skip to content
    IT Service, Operations & Asset ManagementNicheCMDB+DCIM

    Device42 (Freshworks)

    Automated CMDB and data center infrastructure management

    Mkt Cap / ValDiv. of Freshworks
    Auto-discovery + dependency mapping bridges CMDB-to-ops execution within unified ITSM/ITAM/ITOM stack.
    Analyst take · Competitive edge

    SWOT Analysis

    Strengths
    • Agentless discovery across hybrid infrastructure (physical, cloud, container) feeds continuously accurate CMDB.
    • Native dependency mapping reveals service-to-infrastructure relationships critical for incident response.
    • Integrated with Freshworks ITSM/Freshservice; eliminates manual CI maintenance via continuous sync.
    • Strong customer support and active product development under Freshworks investment.
    Opportunities
    • Expand automated remediation workflows triggered by discovery findings and dependency analysis.
    • Integrate with Freshworks Copilot (AI) for autonomous incident triage via real-time asset context.
    • Cloud FinOps bundling: tag discovered cloud resources and surface usage/cost trends.
    Weaknesses
    • Performance degradation at scale with high-volume asset or large multi-tenant deployments reported.
    • Complex initial discovery setup and tuning requires IT ops expertise; steep onboarding.
    • Physical infrastructure visualization limited; connectivity diagrams need richer topology views.
    • Lack of AI-driven anomaly detection or predictive maintenance vs. modern AIOps competitors.
    Threats
    • Pure-play CMDB vendors (ServiceNow, Atlassian) deepening discovery integrations; ITSM suites bundling CMDB.
    • Open-source and lightweight discovery tools (Nautobot, netbox, CloudMapper) eroding DCIM + asset niches.
    • Agentless discovery arms race; competitors commoditizing auto-discovery; pressure on pricing.

    User Sentiment

    Synthesized from G2, Gartner Peer Insights, and analyst review data.

    What users love
    • Automatic discovery + dependency mapping eliminates manual CMDB maintenance and keeps data fresh.
    • Seamless ITSM integration; CI context surfaces in Freshservice tickets, speeds troubleshooting.
    • Multi-cloud + hybrid visibility; scales from small data centers to complex hybrid environments.
    Common complaints
    • Slow query performance under large-scale asset loads; reporting times unacceptable in 10k+ device estates.
    • Complex initial setup; agentless discovery rules and credential management steep learning curve.
    • Physical wiring/rack topology views too basic; real data center ops teams need richer visualization.

    Customer Profile

    Who buys this

    Typical segments

    Mid-market enterprise ITSM teams (500–5k devices) using Freshservice for ticketing + operations.Hybrid cloud / multi-data-center ops teams requiring unified asset visibility across on-prem + cloud.Service-delivery organizations bridging IT operations and business service management.

    Typical buyer

    IT Operations Manager or ITSM Lead accountable for CMDB accuracy and incident resolution speed.

    Top use cases
    1. 1Auto-discovery + dependency mapping for faster MTTR in incident management.
    2. 2Unified CI tracking across multi-cloud and hybrid infrastructure to feed ITSM workflows.
    3. 3ITAM + DCIM consolidation (assets + datacenter capacity) on single platform.

    Future Focus Areas

    1

    AI-powered anomaly detection on asset patterns and dependency changes to flag risky configurations.

    2

    Cloud cost attribution via discovered resource tagging and usage correlation.

    3

    Autonomous remediation playbooks triggered by discovery findings.