Emerging Service And Speculative Robotics covers small public companies trying to put robots or robot software
into live service work: sidewalk delivery, restaurant and hospitality robots, security patrol and guarding,
facilities-management automation, defense-autonomy software, wearable or human-machine interfaces, and subsea remotely operated vehicles. The
stack sits in customer workflows rather than in a factory component catalog: a buyer pays for robots, fleet
hours, software, guarding, service labor, field operations, or autonomy tools, and the company has to turn that
activity into recognized revenue, gross margin, lower cash burn, and controlled share count. The current basket
keeps SERV first for live fleet evidence, RR and PDYN next for revenue or backlog conversion, and KSCP, SPPL,
WETO, and KITT as watch items where margin, disclosure, software attach, or financing still controls the setup.
What the stack is: early commercial robot fleets, robot-as-a-service deployments, autonomy software, managed security services, marine ROV operations, wearable-control demos, and service-support teams that make physical robots usable in customer locations.
What it does in the theme: this layer tests whether the broad robotics theme has reached paid work outside mature medical, warehouse, factory, and component suppliers.
Main pieces: delivery robots, hospitality robots, autonomous cleaning robots, facilities-management software, autonomous security robots, emergency communication devices, defense swarm software, engineering and precision-manufacturing capacity, ROV service fleets, ToolKITT-style autonomy software, customer support, field technicians, and monitoring centers.
Where it sits: on sidewalks, in restaurants, hospitals, commercial buildings, guarded facilities, defense test ranges, offshore work sites, and customer control rooms rather than inside upstream semiconductor or motion-control supply chains.
How Robotics uses it: this node is the speculative proof layer. It asks whether demos, pilots, acquired service revenue, or fleet activity become repeat usage, backlog, remaining performance obligations, revenue density, and better gross economics.
Terms used later: RaaS means robots-as-a-service; RPO means contracted revenue not yet recognized; revenue density means revenue per robot, route, site, fleet hour, or service team; gross loss means cost of revenue is higher than revenue; ATM means an at-the-market equity program that can fund operations but dilute holders.
Report boundary: this is a tactical node report. It summarizes and routes current evidence from
maintained knowledge lanes and read-only discovery data. Durable company research, raw source registries, and
claim IDs stay in the linked knowledge pages.
Current Setup
Paid robot-work gateFleet activity is useful only when revenue density and cash burn improve.
Serve has the clearest live service-robot operating growth; RR, PDYN, KSCP, SPPL, WETO, and KITT still need cleaner filing, customer, backlog, margin, software attach, or financing evidence before the node can be treated as more than a fragile watch screen.
Positive proofDeployment evidence is now better sourced.
All seven names have maintained knowledge lanes or official filing evidence, and discovery has local daily bars through 2026-06-26.
Conversion gateQ2 and Q3 filings must show operating leverage.
Watch revenue mix, RaaS/RPO, active robots, backlog, gross margin, cost of revenue, cash use, and share count.
Primary constraintMost names still depend on outside capital.
ATM use, PIPEs, conversion terms, reverse splits, late filings, and going-concern language can overwhelm revenue progress.
This node matters because early service robots, facilities robots, and autonomy software can attract capital before the customer economics are visible. The useful evidence is named customers, paid robot fleets, fleet hours, RaaS or service revenue, software attach, backlog or RPO, gross margin, cash runway, timely filings, and share-count discipline.
The source base improved since the old page: SERV, PDYN, KSCP, SPPL, and KITT now have maintained knowledge lanes, while RR and WETO already had filed lanes. SERV shows the clearest operating growth with Q1 2026 revenue, daily active robots, software services, and Diligent healthcare automation. PDYN has backlog and FY2026 guidance tied to defense autonomy and manufacturing. RR has cash and RaaS/RPO evidence, KSCP has acquisition-aided revenue scale, SPPL has FY2025 facilities robotics and software revenue, WETO has launch-window optionality, and KITT has subsea autonomy and ROV service evidence. The next positive proof is Q2/Q3 revenue conversion with narrower gross loss or cash burn.
The node is still financing-sensitive. SERV, PDYN, KSCP, SPPL, WETO, and KITT all carry dilution, burn, or runway questions, and RR has a delayed March 2026 filing gate in the maintained lane. SPPL is a foreign private issuer with no quarterly revenue in the inspected source set, FY2025 operating cash outflow, and March 2026 dilution. WETO has no disclosed Orchestra robotics revenue, and KITT remains distressed with going-concern and conversion-mechanics risk. Static setup levels from the old page are stale versus API-backed chart data now available through 2026-06-26, so price levels should be refreshed before use as current trading evidence.
Selected-security right-rail charts use the report API route /api/securities/{ticker}/chart?frequency=weekly&window=3y&as_of=latest. Static setup thresholds from the prior node package used daily_ohlc through 2026-05-29 and are stale versus local rows through 2026-06-26.
Basket
Ranking uses source-backed service-robotics economics first, then financing risk and chart timing. SERV ranks
first because its lane has the clearest paid fleet and software-services evidence. RR and PDYN follow because
they have direct robotics or autonomy revenue paths but still need filing, backlog, and margin proof. KSCP,
SPPL, WETO, and KITT remain higher-friction watch items because acquired services, foreign-private-issuer cadence, pre-revenue pivot risk, or
distressed financing can dominate the robotics story.
Outdoor delivery and healthcare automation fleet operator with the clearest current service-robot revenue evidence.
Market cap$464.7M
Next earningsAug 6, 2026 est.
Latest qtr revenue$2.984M
Role in stack
Serve sells robot delivery capacity, fleet services, software services, and early healthcare automation exposure. The customer gate is whether robot count, supply hours, and Diligent integration become revenue density and lower gross loss.
Revenue mix
Q1 2026 revenue was $1.958M fleet services and $1.026M software services. The mix is useful only if software and healthcare contribution improve gross economics.
Proof burden
Serve needs robot count, supply hours, and software or healthcare automation revenue to narrow gross loss and operating cash use instead of scaling field-support cost faster than revenue.
Cash-rich commercial and industrial robot platform attempting to convert hardware sales into RaaS and service economics.
Market cap$433.8M
Next earningsNot confirmed
Latest qtr revenue$1.147M
Role in stack
Richtech sells, leases, services, and deploys commercial and industrial robots. Theme pressure becomes economics only if RaaS deployments, leasing, RPO, and customer revenue absorb support and fleet costs.
Revenue mix
Q1 FY2026 revenue was product sales $357K, leasing/service/rental $405K, RaaS $319K, and other revenue $66K. The March 2026 quarter remains a filing gate in the maintained lane.
Proof burden
Richtech needs normalized filings, higher RaaS or lease contribution, RPO conversion, and support costs that do not absorb the recurring-revenue benefit.
Defense-autonomy software and precision-manufacturing transition with backlog visibility but unproven software attach.
Market cap$275.0M
Next earningsAug 5, 2026 est.
Latest qtr revenue$3.538M
Role in stack
Palladyne supplies autonomy software, engineering services, and precision-manufacturing capacity for defense and industrial robots. The gate is backlog conversion, first-article approvals, and named software or production economics.
Revenue mix
Q1 2026 revenue remained manufacturing and engineering-services-heavy. The lane says scaled software license revenue is not yet separately visible despite SwarmOS, BRAIN, Pilot, IQ, and IntelliSwarm optionality.
Proof burden
Palladyne needs backlog conversion, first-article acceptance, and visible software or production revenue that supports the FY2026 ramp without relying mainly on financing.
Security robot and managed-security platform attempt where Event Risk added revenue scale but not yet self-funding economics.
Market cap$32.6M
Next earningsNot confirmed
Latest qtr revenue$6.016M
Role in stack
Knightscope combines autonomous security robots, emergency communication devices, monitoring software, and acquired guarding services. The gate is whether full-quarter KSF revenue improves margin and cash burn.
Revenue mix
Q1 2026 revenue was Core Technology $3.665M and Acquired Security Force $2.351M. Consolidated gross margin was only about 8% of revenue, so the service revenue still needs quality proof.
Proof burden
Knightscope needs full-quarter KSF contribution, better Core Technology margin, lower operating cash burn, and share-count control before acquired revenue can count as stronger robot economics.
Facilities-management automation name where robotics revenue is real but software attach, cash burn, and dilution still decide the setup.
Market cap$38.4M
Next earningsNot confirmed
Latest revenueFY2025 S$5.91M
Role in stack
SIMPPLE sells autonomous cleaning robots, warranty and maintenance, facilities-management software, IoT, and SIMPPLE.AI workflow automation. The customer gate is whether Singapore facility deployments attach to higher-margin software and lower cash burn.
Revenue mix
FY2025 revenue was S$5.91M. Robotics supplied about three quarters of revenue at lower gross margin, while software supplied about one quarter, had higher gross margin, and declined year over year.
Proof burden
SPPL needs the next 6-K or interim update to show repeatable Singapore revenue, software reacceleration, stable gross margin, lower operating cash use, and no near-term financing that overwhelms the March 2026 raise.
Physical AI and wearable-robotics pivot where reported revenue is still legacy travel and mobility services.
Market cap$70.8M
Next earningsNot confirmed
Latest qtr revenueH1 RMB9.6M
Role in stack
Wetour is a watch item for human-machine interfaces and the Orchestra Physical AI platform. The gate is named paying customers, revenue, backlog, pricing, production, and funded runway after the launch window.
Revenue mix
The latest lane says disclosed revenue remains packaged tours, chartered bus service, and commuter shuttle service. No Orchestra robotics revenue, backlog, named customer, or product economics were found.
Proof burden
WETO needs official Orchestra customers, robot revenue, backlog, pricing, production plans, and funded runway before the humanoid or Physical AI pivot can carry the node economics.
Subsea autonomy and ROV services option where common-equity capture is controlled by liquidity and dilution mechanics.
Market cap$5.0M
Next earningsNot confirmed
Latest qtr revenue$0.160M
Role in stack
Nauticus supplies subsea ROV services, Aquanaut vehicles, ToolKITT autonomy software, Olympic Arm manipulation, defense work, and UAE/GCC optionality. The gate is contracted revenue before financing mechanics absorb the setup.
Revenue mix
One reported segment combines ROV services, autonomy software, hardware, and engineering. Q1 revenue was tiny and cost of revenue was far above revenue, so mix quality is not yet proven.
Proof burden
Nauticus needs contract revenue, ROV utilization, cost-of-revenue repair, and financing terms that leave common holders exposed to operating progress rather than conversion mechanics.
Market caps use read-only discovery latest close and weighted shares queried on 2026-06-28, with latest local closes through 2026-06-26. Nasdaq/Zacks provided estimated next earnings for SERV and PDYN; RR's prior Jun. 17, 2026 estimate is stale as of this page date, and no current vendor date was confirmed for RR, SPPL, WETO, KSCP, or KITT. Revenue figures use latest maintained security lanes and SEC companyfacts where available; SPPL and WETO are foreign private issuers without quarterly revenue in the inspected source set.
What Confirms Or Weakens
AreaWhat confirmsWhat weakens or invalidatesWatch next
01Node thesis
Robots do paid work
What confirms
Paid fleets, robot hours, service sites, backlog, RPO, named customers, and product revenue grow while gross loss and operating cash use narrow.
What weakens or invalidates
Demos, launch events, fleet counts, or acquired revenue arrive without customer economics, margin, cash conversion, or share-count discipline.
Watch next
Q2/Q3 filings
Revenue density
Gross margin
Cash use
02Economics mechanism
Revenue converts
What confirms
SERV improves revenue per robot and gross loss; RR grows RaaS and RPO; PDYN converts backlog; KSCP improves full-quarter KSF margin; SPPL lifts software attach and cash conversion; KITT rebounds with better cost of revenue.
What weakens or invalidates
Revenue grows mechanically from acquisitions, fleet count, or one-time projects while cost of revenue, support cost, or public-company expense absorbs the benefit.
Watch next
RaaS/RPO
Backlog conversion
Fleet economics
Segment margin
03Customer evidence
Demand is named
What confirms
Customers, sites, route partners, defense programs, healthcare deployments, facilities contracts, security contracts, or offshore projects are named and tied to recognized revenue or contracted backlog.
What weakens or invalidates
Customer concentration rises, partner economics change, launch releases lack customer names, SPPL does not disclose repeat facility deployments, or WETO and KITT remain mainly narrative without funded contract detail.
Watch next
Customer concentration
Named awards
RPO/backlog
Retention
04Funding
Runway versus dilution
What confirms
Cash runway extends while ATM, PIPE, conversion, and share-count growth slow relative to revenue and margin progress.
What weakens or invalidates
New shares, warrants, convertible terms, reverse splits, EPFA draws, or low-price financing become the main source of activity before operating proof improves.
Watch next
SERV ATM
PDYN ATM
KSCP going concern
SPPL dilution
KITT conversions
05Policy and filings
Disclosure stays clean
What confirms
Filings arrive on time, controls improve, Nasdaq/listing issues clear, and official releases reconcile with revenue, backlog, and customer disclosure.
What weakens or invalidates
RR filing delay persists, SPPL's foreign-private-issuer cadence leaves interim revenue and cash burn unclear, WETO product claims remain unreconciled with filings, KITT controls and listing mechanics worsen, or any company delays periodic reports.
Watch next
10-Q/6-K timing
Controls
Nasdaq notices
Product claim support
06Operating constraint
Field work is expensive
What confirms
Hardware cost, field service, labor, component, freight, offshore utilization, and integration costs fall as a percentage of revenue.
What weakens or invalidates
More robot deployments require more support labor, inventory, depreciation, customer acquisition cost, or working capital than the revenue can absorb.
Watch next
Cost of revenue
Support cost
Utilization
Working capital
07Stale condition
Refresh trigger
What confirms
Knowledge lanes, SEC filing facts, earnings calendars, and API chart data remain current with no material filing, customer, financing, or listing update since this page date.
What weakens or invalidates
Any Q2 filing, earnings date change, ATM filing, conversion filing, customer award, delayed filing, or API data change arrives before this node is refreshed.
Nasdaq analyst earnings-date API was last checked on 2026-06-13. It still supports SERV Aug. 6, 2026 and PDYN Aug. 5, 2026 as estimates. RR's prior Jun. 17, 2026 estimate is stale as of 2026-06-28; RR, SPPL, WETO, KSCP, and KITT therefore say Not confirmed.
SPPL and WETO are foreign private issuers in the inspected source set. SPPL's latest maintained operating source is FY2025 revenue of S$5.91M from the SPPL lane and FY2025 Form 20-F. WETO's latest maintained operating source is H1 FY2026 revenue of about RMB9.6M from the WETO lane and H1 FY2026 6-K.
Market-cap metrics use read-only discovery latest close and weighted shares queried on 2026-06-28: SERV $464.7M, RR $433.8M, PDYN $275.0M, KSCP $32.6M, SPPL $38.4M, WETO $70.8M, and KITT $5.0M.
Discovery And Chart Provenance
Read-only discovery commands used: discovery status SPPL --json, discovery status RR --json, discovery status WETO --json, representative discovery lineage-status --ticker RR|WETO|SERV|KITT|SPPL --dataset daily_ohlc --limit 10 --json, and read-only DuckDB queries against daily_ohlc and instruments.
Local daily_ohlc rows are available through 2026-06-26 for all seven tickers: KITT 950 rows, KSCP 1,107, PDYN 557, RR 652, SERV 549, SPPL 690, and WETO 332.
Lineage status for sampled tickers shows provider massive, adjusted daily bars, rows written in May 2026, and source freshness of 2026-05-08. Local tables contain later rows, so source-freshness and table freshness do not match.
Right-rail chart assumptions: report API route /api/securities/{ticker}/chart?frequency=weekly&window=3y&as_of=latest; source table daily_ohlc; weekly aggregation should use first open, max high, min low, last close, and summed volume; visible horizon three years; indicators include 20-week EMA, 100-week EMA where history permits, and weekly volume.
Representative API check for SPPL could not connect because the local report API was not running on 127.0.0.1:8765. The page still carries data-report-api="required" and ticker triggers for API-backed right-rail charts.
Known Gaps
Static setup labels and levels from the old node were removed from the article body and should be regenerated from current API or discovery data before being used as trading evidence.
SPPL and WETO quarterly revenue and next earnings dates were not confirmed from credible sources; the page labels those limitations plainly.
RR's prior Jun. 17, 2026 earnings estimate is stale as of this page date, and KSCP and KITT next earnings dates were not confirmed by Nasdaq/Zacks at the checked endpoint.
The parent theme and sitemap were updated for SPPL routing, but the broad parent return screen still uses a 2026-05-29 return window and should be regenerated before it is used as current tape evidence.