Viakoo

Name: Viakoo
Brand: Viakoo

Viakoo is an enterprise OT/IoT operational security platform that discovers agentless devices, assesses firmware/certificate/password posture, automates remediation actions with approval workflows, and maintains audit trails for compliance and operational assurance.

Est 2013|Valuation $45M|Raised $11.9M|17 Ref Customers

LinkedIn 1K|Web traffic 2K|FTEs 24

MarketsVulnerability Management IoT Device Management

Published Oct 15, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Overly complex or costly for small organizations with only a few hundred IoT devices and low vendor diversity. - Industries or use cases where competitors may be more suitable - Environments where the primary need is continuous OT network threat detection, protocol analytics, and SOC-focused incident response; monitoring/detection-first vendors are typically more focused on these capabilities. - Technical requirements that may not be met (require validation) - Organizations with strict requirements for publicly documented SSO/SAML/SCIM support, explicit data residency guarantees, FedRAMP, or other specific certifications should validate the vendor’s capabilities and request supporting documentation. - Budget constraints - Organizations that require transparent list pricing, self-service trials with published rates, or predictable procurement models may find the sales-led, quote-based approach creates procurement friction. - Specific workflows or integrations where the product may be constrained - Environments with many devices that cannot be safely firmware-updated remotely or that require vendor-specific update processes may limit the value of automation. - Red flags in the buying process - Limited independent third-party review presence in public sources; request references and run pilot tests. - Current limitations acknowledged or inferred from public materials - Vendor does not publish detailed public documentation on some enterprise features (for example, SSO/SAML/SCIM, audit-log retention specifics, and data residency options). - Features on the roadmap - Roadmap details were not publicly documented in the materials reviewed. - Scale limitations - The vendor markets support for large deployments, but independent benchmarking and large-scale operational references were not available in the public materials reviewed. - Security or compliance gaps - ISO 27001 is referenced but certificate details were not publicly available; SOC 2 Type II is claimed but the SOC 2 report is available only via vendor request in the materials reviewed. Organizations should request evidence during vendor selection. - API and integration constraints - Integrations are described at a partner/marketing level; technical details such as API rate limits, data schemas, and supported ticketing connectors were not publicly available.

Deal disqualifiers

Small environments with limited device diversity where manual management is feasible; organizations seeking a single platform that provides both deep OT detection and remediation without additional tooling; buyers requiring extensive public peer reviews and transparent pricing before engaging.

02Why they buy

- Observations supported by partner and vendor materials - Partner materials and vendor messaging position the product as a remediation component for device risk, which supports the vendor’s differentiation around remediation and operational execution. - Vendor materials emphasize application-based discovery and an operational model intended to coordinate device updates, certificate rotation, and password enforcement with governance and audit trails. - Areas where competitors have advantages - Some established OT security vendors provide broader public independent reviews, analyst coverage, and deeper OT protocol analytics and detection capabilities.

Why customers chose this product (vendor-published case studies)

Vendor-published case studies indicate customers selected the product for its ability to automate updates across distributed sites and to reduce manual operational effort. These claims are vendor-published and lack independent verification in the materials reviewed.

03Field reports

- Vendor-published examples - Vulnerability remediation case study: vendor materials claim a small team can manage firmware updates across multiple sites and report an associated reduction in maintenance costs. The methodology, baseline, and attribution are not disclosed in the case study. - Transportation/logistics case study: materials reference a pilot with a modest device count using the service assurance manager, but the customer identity and evaluation methodology were not presented in the excerpted materials. - Critical evaluation - Case-study metrics are vendor-published and lack independent verification, baseline definitions, and methodology details. Organizations should validate similar outcomes via pilot projects and reference checks. - Failed or mixed projects - No independent negative case studies were located in the accessible public material.

Availability of third-party review content

Major third-party review platforms showed limited or no accessible review volume for the product in the materials reviewed. Access restrictions or low review counts limited independent third-party sentiment analysis.

Vendor/partner testimonials (vendor-published)

A partner announcement includes a vendor-published customer quote from a customer describing the combined solution's effect on device visibility and security. This should be treated as a vendor-published testimonial rather than an independent review.

Common criticisms and complaints

Due to limited third-party review volume in accessible sources, there is insufficient independent public evidence to characterize recurring support or product complaints. Procurement should rely on reference calls, pilot evaluations, and integration partner feedback to surface product-specific issues.

Deal-breakers and reasons customers didn’t purchase

Not available in the accessible public sources. Organizations should collect buyer feedback during reference checks.

Specific outcomes customers achieved (with metrics when available)

A vendor-published case study includes operational metrics describing a limited staffing model managing firmware updates across distributed locations and a reported reduction in maintenance spending; the case study does not disclose methodology or baseline assumptions. Treat vendor metrics as illustrative until independently validated.

04Best fit

Company sizes

Likely fit: mid-market to large enterprises with distributed sites and large unmanaged device fleets.

Industries and verticals

Physical-security-intensive organizations (video surveillance/access control), critical infrastructure, healthcare (where HIPAA mapping is relevant), education, and other large distributed enterprises.

Roles and personas

Decision makers: CISO, head of security engineering, OT security leaders, physical security/facilities leadership.
End users: SecOps and vulnerability-management teams, OT engineers, IT operations teams handling certificates and network access.

Pain points addressed

Challenges performing patching, credential rotation, and certificate renewal at scale across unmanaged device fleets, and the operational cost of manual updates and audit-evidence generation.

Qualification criteria for good fit

Large unmanaged IoT/OT device fleet, existing discovery tools in place but limited remediation automation, and explicit compliance or audit requirements.

05The pitch

- What the product does (core value proposition in objective terms) - Viakoo offers an enterprise operational technology (OT) / Internet of Things (IoT) security and cyber-hygiene platform that focuses on remediation and operational assurance for unmanaged or agentless devices such as cameras, badge readers, building systems, and medical/OT endpoints. - The platform's stated capabilities include device discovery (including tightly coupled device ecosystems), assessment of configuration/firmware/certificate/password posture, and automation of remediation actions (often requiring human approval) while maintaining an audit trail for compliance and governance. Vendor materials describe these capabilities as agentless and note automated firmware updates, certificate management (for example, 802.1x/TLS), password enforcement, and service assurance/operational monitoring. - Target market and market positioning - Target buyers include enterprise security, IT, and OT teams as well as physical security and facilities groups that manage large, distributed fleets of IoT/OT devices across multiple vendors. - The vendor positions its platform as a remediation and orchestration layer that complements device discovery and visibility tools (for example, common integrations noted with other device visibility providers). Collateral emphasizes use cases in physical security (video/access control), critical infrastructure, healthcare, and distributed enterprises. - Company background (founding year, HQ, key leadership) - Headquarters: Mountain View, California, USA. - Founded: 2013. - CEO/Founder referenced in press materials: Bud Broomhead. - Funding and growth: investment rounds, acquisitions, estimated customer count/revenue if public - Publicly disclosed funding: the company announced a Series A funding round in 2021. - Employee size reported on public professional profiles is in the small-company range. - Customer count and revenue are not publicly disclosed in verifiable form in the materials reviewed. - Pricing model with specific tiers and costs where available - The vendor does not publish standard pricing tiers on public marketing pages; commercial engagement appears to be sales-led and quote-based. A commercial marketplace listing exists for the action platform, but the publicly accessible listing did not include explicit pricing details in the materials reviewed. - Total cost of ownership considerations (implementation, training, hidden costs) - Likely cost drivers (inferred from the category and peer vendor models): - Device- or asset-count licensing - Selection of modules or feature sets (for example, firmware, certificate, password, and service assurance capabilities) - Integration development and ongoing connector maintenance (for discovery platforms and ITSM systems) - Professional services for onboarding, validation of device/vendor compatibility, and change management - Implementation & operational constraints - In OT and physical security environments, remediation actions typically must align with maintenance windows and change control processes. Automated firmware updates and other automated actions may still require approvals, pilot testing, and rollback plans to avoid service disruption. - Contractual/terms review recommended - The vendor publishes subscription/service terms; organizations should review renewal terms, data handling, liability, and support-service-level agreements. - Key competitors in the space (list 4-6 direct alternatives) - Armis (visibility and device security; commonly integrated with remediation tools) - Forescout (device visibility/control; network access control capabilities) - Nozomi Networks (OT/IoT monitoring and detection) - Claroty (OT security) - Tenable OT Security (vulnerability management for OT) - Microsoft Defender for IoT (OT/IoT security)

Get a comprehensive analysis of Viakoo including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →