Best for
Procurement leads, founders, lab operators, and technical buyers who need a faster, better-framed hardware decision.
Compare robotics options around time-to-value, not just specs
Use this page when you are deciding what to buy, how quickly you can evaluate it, and whether leasing, support, or guided onboarding should be part of the decision.
What this page is: a buying-oriented route for teams that want to compare hardware, cost models, lead times, maintenance obligations, and support paths before making a robotics purchase.
Main question
Which platform gets your team to evaluation and useful output fastest — and what does ongoing ownership actually cost?
How to use it
Start with the hardware store, compare the support model and maintenance obligations, then contact SVRC to tighten the shortlist and quote path.
Recommended next links: Hardware Store, Repair & Maintenance, Leasing, Contact, and Industry Applications.
Academy vs Developer Wiki — what matters for buyers and owners?
The Robotics Academy (learn/robotics-library/) covers the ownership lifecycle in its Operations layer (layer E): care schedules, maintenance workflows, serviceability considerations, and how to evaluate operational readiness before a purchase. The Developer Wiki (wiki/) is the technical reference your operators will use post-purchase — SDK integration, hardware API docs, and platform-specific configuration for VLAI L1 and LinkerBot O6. Use Academy to evaluate ownership fit; use Wiki after the purchase to bring engineers up to speed on integration.
Hardware Evaluation
How to evaluate robotics hardware
Evaluating robot hardware is not the same as evaluating a software tool. The right framework considers task fit, time-to-evaluation, bringup complexity, support quality, and total cost of ownership — not just headline specs like DOF or payload. Here is a practical evaluation checklist:
Task fit before specs
Start with your task, not the datasheet. Define the workspace, object weight, manipulation complexity, and required precision before comparing platforms. A 7-DOF arm is useless if it can't reach your actual workspace geometry.
Time-to-first-run
How long does it take from unboxing to first powered teleoperation? For SO-101 and OpenArm, this is typically under one day with SVRC documentation. Longer bringup times compound into slower pilot timelines.
Documentation and community
Is the documentation public, searchable, and maintained? Does the platform have an active community with real troubleshooting threads? Proprietary support-only documentation creates a single point of failure when engineers leave.
Spare parts and repairability
Ask: what is the lead time for the most common failure component (servo, cable, gripper finger)? Can your team replace it, or does every fix require a service call? SVRC stocks spares for all platforms it sells and services.
Maintenance & Repair
Ongoing maintenance and repair planning
Robot hardware is not maintenance-free. A good ownership plan accounts for scheduled calibration, wear component replacement, software updates, and an escalation path when something breaks in the middle of a critical data collection session. SVRC provides repair and maintenance services for all hardware it sells.
Repair & Maintenance Services
SVRC provides diagnostics, repair, calibration, and preventive maintenance for SO-101, OpenArm, DK1, and other SVRC-sold platforms. Same-day assessment available in Palo Alto. Mail-in repair accepted for remote teams.
View repair services →Scheduled calibration
Servo-based manipulators like SO-101 and OpenArm require periodic joint calibration — typically every 50–100 operating hours or after any significant mechanical event. Calibration drift is the most common cause of data quality degradation in long-running pilots.
Wear component lifecycle
Common wear components: servo motors (1,000–3,000 hours), gripper fingers (200–500 cycles for soft grippers), cables (inspect every 3 months). Factor replacement cost and downtime into your total cost model before purchase.
Software update management
ROS 2 driver updates and firmware changes can affect calibration state and data format. Plan a quarterly software review cycle and test on a spare unit before rolling updates to your primary data collection setup.
Suggested Path
A simple buyer sequence
1. Compare hardware
Start with the systems you can actually evaluate, deploy, and support. Filter by task type, DOF, payload, and time-to-evaluation rather than browsing robotics categories abstractly.
Browse store →2. Decide buy vs lease
Leasing makes sense when you want to reduce upfront commitment, validate a workflow before scaling, or cover a fixed-term project without a capital purchase.
Explore leasing →3. Tie the purchase to a use case
Validate that the hardware decision matches a real workflow instead of buying a platform without an adoption plan. Industry application pages give use-case-specific hardware recommendations.
View industry applications →4. Request quote and support path
Use one conversation to cover pricing, lead time, deployment support, maintenance options, and whether your shortlist is actually right for your use case.
Request quote →
Good Next Steps
What buyers usually compare next
Platform-specific detail
Open product resource hubs when you need deeper technical detail — specifications, software requirements, and known integration constraints — before approving evaluation or purchase.
Open resources →SO-101 buyer's read-through
Walk through the SO-101 tutorials before buying to understand bringup complexity, documentation quality, and what your team will actually face in week one of ownership.
SO-101 tutorials →Local access and pickup
Use the Palo Alto location when you need a nearby team, same-day pickup, or an in-person demo and consultation before committing to a purchase decision.
View Palo Alto →Technical onboarding after purchase
Use Robotics Academy when the buying decision is done and the next question is setup, software, and bringing your team to operational confidence with the new hardware.
Open Academy →