When you are evaluating a robotics development platform for your organisation, the funding history and investor confidence behind the software can tell you a great deal about its long-term viability. The March 2025 Series C round secured by Viam is a useful case study in what to examine before committing your engineering resources to a particular ecosystem.
First, look at the total capital raised since the company’s founding. Viam has now accumulated $117 million in total equity funding since it was established in 2020. That figure matters because robotics software development is a long game. Platforms that promise to simplify machine building, monitoring, and management require sustained investment in cloud infrastructure, security hardening, and developer tooling. A company that has only raised a seed round may not have the runway to support you through a multi-year deployment. In Viam’s case, the $30 million Series C led by Union Square Ventures, with participation from Battery Ventures and the Italian investment group Neurone, signals that existing and new investors see value in the platform’s direction.
Second, pay attention to who is leading the round. Union Square Ventures is an existing investor in Viam, and their decision to lead the Series C is a signal of continued confidence. When an early-stage investor doubles down, it often indicates that the company has met or exceeded internal milestones. Battery Ventures and Neurone joining the round adds fresh perspectives and potentially new market access, particularly in Europe given Neurone’s Italian roots. For a European robotics firm, having an investor with continental connections can be relevant if you plan to expand operations across EU member states.
Third, examine the founding team’s background. Viam was founded by Eliot Horowitz, who previously built enterprise-scale cloud services. This is not a trivial detail. The source material notes that Viam’s roots are in enterprise cloud development and that the company was among the first to integrate cloud services with an open-source robotics development environment. When you are selecting a platform, you want to know whether the people behind it understand the demands of production-grade software. Horowitz reportedly spent a year investigating why better programming platforms for physical-world tools did not exist before launching Viam. That kind of domain exploration is worth noting because it suggests the platform was designed to address a specific gap rather than being a hobby project that grew out of control.
Fourth, consider the open-source nature of the platform. Viam’s architecture is open source, and the company was recognised as a 2023 RBR50 honoree for developing an open-source robot architecture with an integrated cloud service. Open-source software gives you the ability to inspect the code, modify it for your own use cases, and avoid vendor lock-in at the code level. However, open source does not mean free cloud services. You still need to evaluate the commercial terms for the cloud management layer. The source material does not disclose pricing, so you will need to request that information directly from the vendor.
Fifth, look at the scope of what the platform claims to do. Viam lets users build, monitor, and manage smart machines via cloud-based management. That is a broad statement. In practice, you should ask whether the platform supports the specific hardware you use, whether it integrates with your existing sensor stack, and whether the monitoring capabilities include real-time telemetry, logging, and alerting. The source material does not enumerate specific hardware compatibility lists, so you must verify that against your own requirements.
Finally, note what is not disclosed. The source material states that Horowitz declined to share the valuation for the Series C round. That is a red flag for some buyers and a non-issue for others. If you are a startup yourself, you may care about the financial health of your technology partners. If you are an enterprise, you may care more about the platform’s feature set and support quality. Either way, you should ask for financial stability information during your vendor due diligence process.
Practical steps
If you are considering Viam or a similar robotics development platform for your next project, here is a step-by-step approach grounded in what the source material tells us about the company’s trajectory and positioning.
**Step 1: Map your hardware and software requirements.** Before you evaluate any platform, write down exactly what machines you need to build, monitor, and manage. The source material describes Viam as a platform for smart machines, but that is a broad category. Do you need to control a robotic arm on a smart production line? Do you need to manage a fleet of autonomous mobile robots? Do you need to integrate vision systems for quality inspection? The source material mentions a robotic arm operating at a smart production line as an illustrative example, but it does not state that Viam supports every possible robot configuration. Your first practical step is to list your specific hardware models, communication protocols, and data requirements.
**Step 2: Verify the open-source licensing terms.** Viam’s platform is open source, which is a significant advantage for transparency and customisation. However, open-source licences vary. Some allow unrestricted commercial use, while others impose copyleft obligations. The source material does not specify the exact licence, so you should request a copy of the licence agreement from Viam or review the repository directly. If the licence is permissive, you can integrate the code into your own products with fewer legal constraints. If it is copyleft, you may need to open-source any derivative works. This is a legal decision that your engineering and legal teams should make together.
**Step 3: Assess the cloud integration depth.** The source material emphasises that Viam integrates cloud services with the robotics development environment. That means you should evaluate not just the robot-side software but also the cloud dashboard, data storage, and API access. Ask for a demonstration of how you would monitor a deployed machine from the cloud. Can you view live sensor data? Can you push configuration changes remotely? Can you set up automated alerts? The source material does not describe these features in detail, so you must ask the vendor for a feature walkthrough.
**Step 4: Check the security posture.** The source material includes an illustration of Viam cloud security and states that Viam maintains high levels of security for customers, their machines, and data stored in the cloud. That is a general claim. In practice, you should request their security documentation, including any SOC 2 reports, encryption standards, and access control mechanisms. The source material does not provide specific security certifications, so you should not assume any particular compliance level. Ask directly about data residency options, especially if you operate in the EU and need to comply with GDPR.
**Step 5: Evaluate the funding runway.** Viam has raised $117 million in total since 2020, including the $30 million Series C in March 2025. That gives the company a solid financial base to continue developing the platform. However, the source material does not disclose the company’s burn rate or profitability. For your own planning, you should ask Viam about their product roadmap and how the new funding will be allocated. The source material states the round is intended to scale the platform, but it does not specify whether that means more engineers, more cloud infrastructure, or more sales and marketing. Understanding the allocation can help you predict how quickly new features will arrive.
**Step 6: Test with a proof of concept.** The most reliable way to evaluate any robotics platform is to build a small prototype. The source material does not provide any benchmarks or performance metrics, so you cannot rely on third-party testing. Instead, design a proof of concept that exercises the core features you need: connecting a robot, sending commands, collecting telemetry, and managing the machine from the cloud. Time-box the exercise to two to four weeks. If the platform cannot handle your basic use case in that timeframe, it is unlikely to handle your production workload.
**Step 7: Review the investor syndicate for strategic alignment.** Union Square Ventures leading the round is notable because they were an early backer. Battery Ventures and Neurone joining suggests the company is broadening its investor base. For your procurement decision, this matters because investors often provide more than capital. They can open doors to enterprise customers, provide strategic guidance, and help with international expansion. If you are a European company, Neurone’s involvement might indicate that Viam is looking to strengthen its presence in the EU market. You can ask Viam about their European go-to-market plans during your vendor meetings.
**Step 8: Plan for long-term support.** The source material notes that Viam was founded in 2020 and has been operating for roughly five years. That is a relatively short track record compared to established industrial automation vendors. You should ask about their support lifecycle, including how long they guarantee backward compatibility for APIs and whether they offer long-term support releases. The source material does not mention any support terms, so you must obtain those in writing before signing a contract.
Common mistakes to avoid
When evaluating a platform like Viam, based on what the source material reveals, there are several pitfalls that can derail your project. Here are the most common ones, grounded in the facts we have.
**Mistake 1: Assuming the platform supports your specific hardware.** The source material describes Viam as a platform for building, monitoring, and managing smart machines. It also mentions a robotic arm on a smart production line as an example. But that does not mean every robot model is supported out of the box. Many robotics platforms rely on community-contributed drivers or vendor partnerships. If you assume compatibility without checking, you may discover mid-project that your robot requires custom driver development. Always verify hardware compatibility against your actual bill of materials before committing.
**Mistake 2: Ignoring the cloud dependency.** Viam’s value proposition is the integration of cloud services with the robotics development environment. That means your robots may depend on cloud connectivity for certain management functions. If you operate in a facility with unreliable internet access or strict network security policies, you need to understand how the platform handles offline operation. The source material does not describe offline capabilities, so you must ask. Some platforms allow local operation with deferred cloud synchronisation; others require a persistent connection. Do not assume the platform will work the same way offline as it does online.
**Mistake 3: Overlooking the total cost of ownership.** The source material does not disclose pricing for Viam’s cloud services. Open-source code is free, but the cloud management layer is likely a commercial product. You should calculate the total cost of ownership over a three-year period, including per-device fees, data storage costs, API call charges, and support contracts. If you only evaluate the open-source component, you may be surprised by the cloud bill later. Ask the vendor for a pricing sheet and model your expected usage against it.
**Mistake 4: Treating the funding round as a guarantee of stability.** Viam’s $30 million Series C and $117 million total funding are positive signals, but they are not guarantees. The source material notes that Horowitz declined to share the valuation, which means you do not know the terms of the round. A company can raise a large round and still struggle with product-market fit. Do not let the funding news substitute for your own technical due diligence. A platform with ample funding but poor documentation will still cost you engineering time.
**Mistake 5: Skipping the security review.** The source material states that Viam maintains high levels of security, but it does not provide specifics. If you are deploying robots that control physical machinery, a security breach could have real-world consequences. You should request Viam’s security whitepaper, penetration test results, and any compliance certifications. If the vendor cannot provide these, that is a significant concern. Do not rely on a marketing illustration of cloud security; ask for the actual documentation.
**Mistake 6: Assuming the open-source community is active.** Viam was an RBR50 honoree in 2023 for its open-source architecture, but the source material does not provide metrics on community activity, such as the number of contributors, GitHub stars, or monthly downloads. An open-source project can be open-source in name only, with a small team doing most of the work. Before you build your product on top of it, check the repository for recent commits, open issues, and response times. A healthy community is a good indicator of long-term maintenance.
**Mistake 7: Neglecting to ask about the founding team’s operational experience.** Eliot Horowitz’s background in enterprise cloud services is a positive indicator, according to the source material. However, the source material does not describe the broader team’s experience in robotics hardware. Building a robot is different from building a cloud service. You should ask about the team’s experience with real-world deployments, including any case studies or reference customers. The source material does not list any named customers, so you will need to request references from the vendor.
**Mistake 8: Failing to plan for migration.** If you are already using another robotics platform, you need to consider how you will migrate your existing code, configurations, and data to Viam. The source material does not describe any migration tools or importers. In practice, you may need to rewrite significant portions of your robot control logic. Budget for this migration effort in your project plan. Do not assume that switching platforms is a plug-and-play exercise.
**Mistake 9: Overestimating the maturity of the platform.** Viam was founded in 2020, which means it has been around for about five years as of the Series C announcement. That is enough time to build a solid product, but it is not the same as a decade-old industrial automation suite. The source material does not describe any large-scale enterprise deployments, so you should ask about the largest fleets currently running on the platform. If the answer is small pilot projects, you may be taking on more risk than you realise.
**Mistake 10: Ignoring the geographic implications of the investor syndicate.** Neurone is described as an Italian investment group. That could be positive for European customers, as it may indicate a strategic interest in the EU market. However, it could also mean that the company is still building its European presence. If you are based in the EU, ask about local support, data residency, and compliance with EU regulations. The source material does not address these topics, so you must raise them in your vendor discussions.
**Mistake 11: Making decisions based on the funding announcement alone.** The March 2025 Series C is news, but it is not a product specification. The source material tells you about the round size, the lead investor, and the total capital raised. It does not tell you about the platform’s performance, reliability, or ease of use. Use the funding news as a reason to investigate further, not as a reason to skip your evaluation process. A well-funded platform can still be the wrong choice for your specific use case.
**Mistake 12: Assuming that "open source" means "no vendor lock-in."** While the code may be open source, the cloud services are likely proprietary. If you build your entire monitoring and management workflow around Viam’s cloud, you may find it difficult to switch to another provider later. The source material does not describe any data export tools or API compatibility with other platforms. Before you commit, ask about your ability to export your data and migrate to another system if needed.
Sources
Published by Vigla Media OÜ (Estonia).