What is it
Robot-hour pricing is a billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
Where a cloud platform charges for the compute hours a GPU runs, a humanoid-robotics company charges for the operating hours a robot works. The meter bundles everything required to deliver that productive hour — the physical hardware, the software and AI stack, remote fleet management, and ongoing support — into a single time-denominated charge. From the buyer’s side, the robot-hour is the unit of physical labor delivered; from the vendor’s side, it is the cleanest proxy for value consumed and cost incurred.
The model emerges specifically in the Robots-as-a-Service (RaaS) segment, where vendors keep ownership of the hardware and customers pay recurring fees rather than buying robots outright. All three companies in this corpus — Agility Robotics, Apptronik, and 1X Technologies — describe a robot-hour or working-hour component in at least one of their commercial tracks, all aimed at logistics, warehousing, and manufacturing. Operators who already budget for GPU-hours of inference grasp the pay-for-what-you-use framing the moment it lands on physical labor. For how to pick a billing unit that tracks real value delivered, see the guide to choosing the right usage metric.
One caution runs through the whole category: the actual per-hour rate is almost never published. Agility Robotics routes Digit through a “Deploy Digit” sales funnel with no public figure — and the famous “$30/hour” everyone quotes is CEO Peggy Johnson’s human-labor benchmark for an under-two-year ROI, not Digit’s price. Apptronik quotes Apollo bespoke and has named only a future target of “under $50,000” per unit at scale, which it says it has not yet reached. Only 1X Technologies attaches real numbers to a product — but those ($20,000 or $499/month for NEO) are flat consumer prices, not a metered robot-hour rate; its enterprise EVE RaaS stays sales-led.
How it works
A robot-hour billing model has several configurable dimensions. In practice every company in this corpus keeps the rate private and negotiates bespoke contracts, but the structural mechanics are consistent across the category.
| Dimension | Description | Corpus example |
|---|---|---|
| Rate | The per-hour charge for managed robot operation | Agility Robotics quotes Digit RaaS via “Deploy Digit” — no public $/hr figure |
| Bundled components | What the rate covers beyond the robot frame | Agility bundles the Agility Arc cloud platform, software, support, and uptime into its RaaS fee |
| Utilization overhead | Robots must charge; the working-to-charging ratio drives effective cost per productive hour | Digit runs at roughly 2:1 today; Agility targets 4:1 then 10:1. Apollo runs ~4 hours per battery pack |
| Minimum commitment | Whether there is a floor on hours or a contract length | 1X’s NEO subscription carries a six-month minimum (~$2,994 floor); enterprise RaaS deals include deployment-length commitments |
| Purchase alternative | Whether an outright-purchase option sits alongside the per-hour track | Apptronik and Agility both offer direct purchase; 1X offers NEO at a one-time $20,000 |
Unit math. Effective cost per productive robot-hour = (monthly RaaS fee) ÷ (operational hours in the month). A robot subscribed at a hypothetical $4,000/month that works 160 hours has a nominal cost of $4,000 ÷ 160 = $25/hr — but because a Digit must rotate off-shift to charge (~2:1 working-to-charging), you must provision extra robots to keep one continuously productive, which multiplies the true fleet cost. Agility improving that ratio from 2:1 toward 4:1 roughly halves the effective per-productive-hour cost without ever changing the nominal rate.
The recurring design tension is between the simplicity of a flat per-hour rate and the hidden utilization overhead that makes the true cost per unit of productive work higher than the headline implies. 1X Technologies sidesteps metering entirely on the consumer side — NEO is a flat $499/month (or a $20,000 purchase), not a per-hour bill — while reserving true RaaS-style contracts for its enterprise EVE fleet. For the billing-infrastructure principles behind metered recurring compute, see the usage invoicing and billing cycles guide.
Companies using this
Three companies in the corpus use robot-hours as a billing unit, all humanoid-robotics vendors targeting logistics and manufacturing. The table below lists each with its pricing model, billing units, and verification date.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| 1X Technologies | NEO home humanoid robot & EVE enterprise robotics (RaaS) | No | 2026-07-23 | ||
| Agility Robotics | Digit humanoid robot + Agility Arc cloud platform (Robots-as-a-Service) | No | 2026-07-23 | ||
| Apptronik | Apollo general-purpose humanoid robot (RaaS + outright sale) | No | 2026-06-14 |
Explore this theme in the knowledge graph
FAQ
What is robot-hour pricing?
Robot-hour pricing is a billing unit where a customer is charged for each hour a robot or autonomous system actively operates, bundling the hardware, software, and support costs into a single time-based meter. It is the physical-world equivalent of a GPU-hour: you pay for productive robotic labor rather than buying the machine outright, and it is the natural meter for Robots-as-a-Service (RaaS) deployments.
Which companies use robot-hour pricing?
Three humanoid-robotics companies in the corpus bill on a robot-hours basis: Agility Robotics (Digit RaaS), Apptronik (Apollo RaaS, described in interviews as tied to working hours), and 1X Technologies (EVE enterprise RaaS, alongside its flat-fee NEO consumer subscription). All target logistics, warehousing, and manufacturing.
How much does a robot-hour cost?
None of the three companies publishes a per-hour RaaS rate. Agility Robotics quotes Digit RaaS via its 'Deploy Digit' sales funnel with no public figure — the widely-cited '$30/hour' is CEO Peggy Johnson's human-labor benchmark, not Digit's price. Apptronik quotes Apollo bespoke (CEO Jeff Cardenas has named a future target of 'under $50,000' per unit at scale, not a per-hour rate). 1X publishes NEO consumer prices ($20,000 outright or $499/month) but keeps its EVE enterprise RaaS rate sales-led.
How is robot-hour pricing different from buying a robot?
Buying a robot is a one-time capital purchase; robot-hour pricing converts that into a recurring operating expense tied to how much the robot works. Apptronik and Agility Robotics both offer an outright-purchase alternative alongside their RaaS tracks, while 1X lets consumers choose between a $20,000 NEO purchase and a $499/month subscription — the same own-or-subscribe split, at consumer scale.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.