Avea Robotics

Software letting humans remotely take over robots when autonomy fails.

Avea has real customers and real revenue in a market that big robot makers are trying to build for themselves instead of buying.

Avea Avea builds software that lets people control robots from far away, a useful tool in a real market worth $890 million that is just starting to grow. The problem is that the biggest robot companies, like Figure and 1X, are building their own remote control systems instead of buying from Avea because controlling robots gives them secret data they need to make robots smarter on their own. Avea competes against other companies like PickNik that already ship working products, and all of them face a deeper threat: as artificial intelligence gets better at making robots work without human help, the need for people to control robots from far away shrinks. The one thing that could save Avea is if it could own the special data that comes from all its customers using the software, and use that data to make robots smarter faster than anyone else, but it does not own that data yet.

• $18k monthly recurring revenue (June 2026)
• About 30 robots deployed on the platform (June 2026)
• Team size of 2 to 5 people (2026)

• No confirmed institutional funding; runway and backing unverified as of mid-2026. Severity: high
• Largest potential buyers (Figure, 1X, Genesis) build teleoperation in-house, shrinking Avea's addressable market. Severity: high
• Core category framed industry-wide as a bridge to autonomy, so improving VLA/world models could shrink demand. Severity: high
• Tiny team of 2 to 5 people with no jobs currently posted, limiting execution capacity. Severity: medium
• Crowded niche with funded peers (PickNik, Adamo, Proxy, TeleOperator AI) already shipping similar products. Severity: medium

Is Avea Robotics profitable?

No. Avea Robotics reported about $18k in monthly recurring revenue as of its June 2026 YC launch post, roughly $216k annualized, with a team of 2 to 5 people. No profitability figures have been disclosed, and the company has not confirmed any funding round.

How many robots has Avea Robotics deployed?

Avea Robotics states, in its own June 1, 2026 YC launch post, that it has helped deploy nearly 30 robots using its Sentinel teleoperation software. This figure is self-reported by the company and has not been independently verified by third parties.

Could AI replace Avea Robotics?

Possibly over time. Avea sells human-in-the-loop teleoperation, which the industry, including Avea's own August 2025 blog post, frames as a bridge until robot autonomy matures. As VLA and world models like Google's Genie improve, the intervention layer Avea sells could shrink.

Who are Avea Robotics' biggest competitors?

Direct peers include PickNik Robotics (MoveIt Pro, VR/haptic teleop), Adamo, Proxy Robotics, and TeleOperator AI. Bigger threats are humanoid makers like Figure AI and 1X Technologies, which build teleoperation in-house (1X's Expert Mode, referenced June 2026) rather than buying it.

Has Avea Robotics raised venture funding?

This is unconfirmed. As of mid-2026, no primary source verifies a priced funding round for Avea Robotics; aggregator claims about funding amounts conflict and are unreliable. The company is a Y Combinator Spring 2026 batch participant, per YC's own company page.

What does Avea Robotics actually sell?

Avea Robotics sells Sentinel, a low-latency teleoperation platform letting robotics companies control robots remotely via VR headsets with haptic feedback, supporting data collection and supervised autonomy, per its own site and its June 1, 2026 YC launch post.

• 2026-06-01Avea Robotics launches on YC with self-reported $18k MRR and nearly 30 robots deployed
• 2026-05-19Avea Robotics posts first YC Launch, pitched as human-in-the-loop uptime system for robots
• 2025-12-10Avea announces sub-10ms teleop integration with i2RT Robotics YAM arms and iREX Tokyo demo with TRON K.K.
• 2025-09Avea Robotics sponsors Actuate 2025 robotics developer conference in San Francisco
• 2025-08-05Avea publishes blog post arguing current remote teleoperation faces latency/network limits