Pepper

Height

120 cm

Weight

29.6 kg

Battery

~12 h

Speed

~2 km/h

Commercial Available

Pepper

Aldebaran Robotics' semi-humanoid robot designed to read emotions and interact with people. Introduced by SoftBank in Tokyo in June 2014, Pepper became one of the most recognized social robots in the world — approximately 27,000 units were manufactured before production was paused in June 2021 due to weak demand. The first batch of 1,000 units sold out in 60 seconds in June 2015. Pepper was deployed in SoftBank stores, banks, hospitals, airports, and restaurants across Japan, Europe, and North America. Features a 10.1-inch touch display, emotion recognition via facial expression and voice tone analysis, and a wheeled omnidirectional base. In June 2025, Aldebaran Robotics went into receivership. In July 2025, Shenzhen-based Maxvision Technology Corp. acquired Aldebaran's core assets, including the Pepper and NAO intellectual property.

Listed price

See pricing details

Current official sales are region/partner-based with no public MSRP on official pages; legacy Japan launch pricing was about ¥198,000 (~$1,800).

Release window

Jun 1, 2014

Current status

Available

Aldebaran Robotics

Last verified

Apr 17, 2026

Share this robot

Open a plain share composer on X or Bluesky for this robot profile.

Technical overview

Core specifications and system stack

A fast read on the mechanical profile, sensing package, and listed platform details for Pepper.

Technical Specifications

Height

120 cm

Weight

29.6 kg

Battery Life

~12 h

Charging Time

~8 hours 20 minutes

Max Speed

~2 km/h

Operational profile

How this robot is configured

Capabilities

10

Connectivity

2

Key capabilities

Emotion RecognitionFacial Expression AnalysisNatural Conversation20 Degrees of Freedom10.1-inch Touch DisplayOmnidirectional Wheeled BaseAutonomous NavigationRetail & Reception Use

Listed platforms & ecosystem

NAOqi SDKChoregrapheAndroid SDK

About the Pepper

2Protocols10Capabilities

The Pepper is a Commercial robot built by Aldebaran Robotics. Aldebaran Robotics' semi-humanoid robot designed to read emotions and interact with people. Introduced by SoftBank in Tokyo in June 2014, Pepper became one of the most recognized social robots in the world — approximately 27,000 units were manufactured before production was paused in June 2021 due to weak demand. The first batch of 1,000 units sold out in 60 seconds in June 2015. Pepper was deployed in SoftBank stores, banks, hospitals, airports, and restaurants across Japan, Europe, and North America. Features a 10.1-inch touch display, emotion recognition via facial expression and voice tone analysis, and a wheeled omnidirectional base. In June 2025, Aldebaran Robotics went into receivership. In July 2025, Shenzhen-based Maxvision Technology Corp. acquired Aldebaran's core assets, including the Pepper and NAO intellectual property.

Current official sales are region/partner-based with no public MSRP on official pages; legacy Japan launch pricing was about ¥198,000 (~$1,800). See all Aldebaran Robotics robots on the Aldebaran Robotics page.

Spec Breakdown

Detailed specifications for the Pepper

Height

120cm

The listed height is 120cm. Height alone does not establish working reach or clearance under furniture; check the documented operating configuration and required space.

Weight

29.6 kg

The listed weight is 29.6 kg. Weight alone does not establish locomotion, stability or safety around people. Check handling requirements and the model’s documented operating limits.

Battery Life

~12 hours (shop use)

This is the recorded runtime entry. Test conditions and independent verification are not established by this field. Confirm workload, operating mode and environmental conditions before comparing runtimes.

Charging Time

~8 hours 20 minutes

A charging time of ~8 hours 20 minutes means the ratio of operation to downtime is an important consideration for applications requiring near-continuous availability. Some deployments use multiple robots in rotation to maintain uninterrupted service.

Maximum Speed

~2 km/h (1.2 mph)

The recorded maximum-speed entry is ~2 km/h (1.2 mph). It does not establish sustained travel speed, terrain handling, or safe speed around people. Check the source's gait, operating mode, surface and load conditions before planning movement through a shared space.

Read this recorded AI entry alongside the model description and source notes for announcement or deployment context. A platform name alone does not establish implemented features, autonomy, or performance.

Pepper Sensor Suite

The profile lists the sensor descriptions below. These entries do not establish physical sensor counts, sensor fusion, redundancy, or performance.

Consult the linked profile sources for hardware configuration and tested behavior. A technology label alone does not verify an operating capability.

Explore sensor technologies: components glossary · full components directory

Pepper Use Cases & Applications

Commercial robots handle tasks in business environments — delivering food in restaurants, guiding visitors in hotels, transporting supplies in hospitals, and moving inventory in warehouses. Their value is measured in operational efficiency, labor cost savings, and improved service consistency.

Recorded Capabilities

The Pepper record lists 10 capabilities. Keep any announcement or demonstration qualifiers attached to these entries; the count alone does not establish practical performance.

Emotion Recognition
Facial Expression Analysis
Natural Conversation
20 Degrees of Freedom
10.1-inch Touch Display
Omnidirectional Wheeled Base
Autonomous Navigation
Retail & Reception Use
Education & Research Platform
Elder Care Assistance

These are the capabilities listed in the profile. Hardware configuration and demonstrated performance should be checked against the linked sources.

Listed Platforms & Ecosystem

These are the platforms, communities, or ecosystem relationships listed in the profile. A listed name or protocol alone does not confirm home-device interoperability or automation support.

NAOqi SDK Choregraphe Android SDK

Pepper Capabilities

10

Capabilities

AI

NAOqi OS (Linux-based)

Natural Conversation

General context · confirm model-specific support

Conversational quality depends on language, noise, turn-taking, context and response delays. Try a realistic exchange with interruptions, corrections and an unfamiliar question, and establish any network or operator dependency. Supported languages, dialogue memory, speech processing and language-model integrations should come from explicit documentation rather than being inferred from a conversation label or an expressive appearance.

Autonomous Navigation

General context · confirm model-specific support

Autonomous navigation concerns movement toward a goal within defined operating conditions. Useful evidence includes the mapped area, localization method, obstacle tests, permitted surfaces and recovery process when a route is blocked. Establish when a person must intervene and whether remote assistance is involved; the label alone does not identify SLAM, particular sensors or an unattended operating envelope.

Additional Capabilities

Emotion Recognition
Facial Expression Analysis
20 Degrees of Freedom
10.1-inch Touch Display
Omnidirectional Wheeled Base
Retail & Reception Use
Education & Research Platform
Elder Care Assistance

Listed Connectivity & Voice Systems

The Pepper profile lists the following communication and voice-system descriptions.

Network & Communication Details

Listed network interfaces do not by themselves identify supported services, integrations, or device-control functions.

Listed Voice Systems

Supported commands and device controls require product-specific documentation.

Pepper Technology Stack Overview

The Pepper by Aldebaran Robotics has the following technology descriptions in its profile. The physical platform features a height of 120cm, a weight of 29.6 kg, a top speed of ~2 km/h (1.2 mph), providing the foundation on which this technology stack operates.

Reported sensing

The profile lists RGB Camera ×2 (forehead + mouth), 3D Depth Sensor, Microphone ×4, Gyroscope ×2 (torso + base), Touch Sensors (head, hands), Sonar ×2 (base), Laser Sensor ×6 (base), Bumper ×3 (base). Hardware quantities, integration, and tested behavior require separate source evidence.

Listed connectivity

The connectivity descriptions listed for the Pepper are Wi-Fi 802.11 a/b/g/n (2.4/5 GHz), Ethernet. Specific services and device interoperability require separate documentation.

Reported AI or behavior system

Recorded AI description: NAOqi OS (Linux-based)

Voice — Multilingual Speech Recognition & Synthesis

The profile lists these voice systems: Multilingual Speech Recognition & Synthesis. This listing does not establish control of other devices or support for particular automation routines.

Who Should Consider the Pepper?

Target Audience

Commercial robots are acquired by businesses including restaurants, hotels, hospitals, retail stores, and logistics facilities. Purchasing decisions typically involve operations managers and IT departments evaluating ROI against human labor costs.

Key Considerations

Reliability and uptime, navigation in crowded dynamic environments, payload capacity, integration with business systems (POS, inventory management), ease of deployment and maintenance, and total cost of ownership (including service contracts) are the primary factors.

Listed pricing

Current official sales are region/partner-based with no public MSRP on official pages; legacy Japan launch pricing was about ¥198,000 (~$1,800).

Availability

Available

The Pepper is listed as Available, indicating an ordering listing. The label does not confirm current stock, regional access, or shipping dates. Check Aldebaran Robotics's current ordering terms and the recorded sales notes for details.

Pepper: Strengths & Trade-offs

Recorded features and considerations to assess

Recorded features to assess for the Pepper

Recorded capability range

The Pepper record lists 10 capabilities. Review their qualifiers and supporting evidence for the tasks you need. The number of entries does not establish workflow coverage, reliability, or the ability to replace other robots.

Recorded battery life

The battery-life entry is ~12 hours (shop use). Check the source conditions and operating mode before using this figure to plan a session. It does not establish task completion, area coverage, or continuous-use runtime.

Listed Available

The Pepper is listed as Available, indicating an ordering listing. The label does not confirm current stock, regional access, or shipping dates. Check Aldebaran Robotics's current ordering terms and the recorded sales notes for details.

What to consider carefully

See pricing details

Current official sales are region/partner-based with no public MSRP on official pages; legacy Japan launch pricing was about ¥198,000 (~$1,800).

Note: This strengths and trade-offs assessment is based on the Pepper's documented specifications as tracked in the ui44 database. Real-world performance depends on deployment conditions, firmware maturity, and environmental factors. For the most current information, check the Aldebaran Robotics manufacturer page or visit the official source. Use the comparison tool to evaluate these trade-offs against competing robots in the same category.

How Commercial Robot Technology Works

Understanding the engineering behind this category

Commercial robots operate in the demanding intersection of technology and business operations. From restaurant servers to warehouse movers, these robots must perform reliably in dynamic, crowded environments while delivering measurable return on investment. The technology behind commercial robots emphasizes reliability, integration with business systems, and graceful handling of the unpredictable situations that characterize human-occupied commercial spaces.

Navigation & Mobility

Commercial robots navigate environments that are significantly more challenging than typical homes — crowded restaurant floors, busy hotel lobbies, and dense warehouse aisles all present unique navigation challenges. These robots typically use LiDAR combined with depth cameras for robust obstacle detection, with special attention to detecting low-height obstacles (children, pets, dropped items) and moving obstacles (people walking unpredictably). Commercial-grade navigation includes fleet coordination — multiple robots sharing maps and position data to avoid congestion and optimize collective efficiency. Elevator integration allows robots to serve multiple floors autonomously.

The Role of AI

AI in commercial robots focuses on operational efficiency and customer interaction. Route optimization minimizes delivery times in restaurants. Task prioritization ensures urgent orders are handled first. Customer-facing AI must handle natural language interaction in noisy environments, provide useful information, and maintain a professional and brand-appropriate demeanor. Back-end AI integrates with business systems — restaurant POS (Point of Sale), hotel PMS (Property Management System), warehouse WMS (Warehouse Management System) — to receive tasks and report completions automatically. Predictive AI anticipates demand patterns, pre-positioning robots where they will be needed based on historical data.

Sensor Fusion & Perception

Commercial robots combine navigation sensors (LiDAR, cameras, ultrasonic) with application-specific sensors. Restaurant delivery robots use weight sensors to confirm payload presence and tilt sensors to maintain tray stability. Warehouse robots use barcode or RFID readers for inventory tracking. Hotel robots may include temperature sensors for room-service food. All commercial robots share the need for robust human detection — they must navigate safely around unpredictable human movement while maintaining efficient operation. Edge-case handling is critical: a restaurant robot must correctly respond to a child running into its path, a guest stepping backward without looking, or a server carrying a full tray through a narrow aisle.

Power & Battery Management

Commercial operations demand high uptime, making power management a business-critical concern. Robots serving during peak hours cannot afford lengthy charging breaks. Solutions include fast-charging docks positioned at strategic locations, hot-swappable battery packs for zero-downtime operation, and intelligent charging schedules that top up during naturally low-demand periods. Fleet management systems monitor battery levels across all robots and redistribute tasks to ensure no single robot runs critically low during service. Power consumption monitoring also feeds into TCO (Total Cost of Ownership) calculations that businesses use to evaluate robot deployment ROI.

Safety by Design

Commercial robots operate in regulated business environments with specific safety requirements. Food-handling robots must meet hygiene standards. Robots in public spaces must comply with accessibility requirements, avoiding blocking wheelchair paths or emergency exits. Speed limits are typically set below walking pace in pedestrian areas. Visual and audio signals indicate the robot's presence and intent — lights, gentle sounds, or voice announcements warn nearby people. Payload security ensures items being transported cannot fall. In warehouse environments, safety zones around humans trigger automatic speed reduction or stopping. Integration with building fire alarm and evacuation systems ensures robots do not obstruct emergency procedures.

What's Next for Commercial Robots

Commercial robotics is moving toward greater specialization and deeper business system integration. Rather than general-purpose commercial platforms, expect more robots designed specifically for restaurant table service, hotel room delivery, warehouse aisle picking, or retail shelf scanning. Fleet orchestration — coordinating dozens of robots across a large facility — will become more sophisticated. The business model is also evolving, with Robotics-as-a-Service (RaaS) subscriptions replacing upfront purchases, lowering the barrier to adoption for small and medium businesses.

These are category-level technology examples; they do not establish the capabilities of the Pepper. For its recorded hardware details, see the sensor analysis and connectivity sections above. Check model-specific documentation from Aldebaran Robotics for supported behavior, or use the components glossary to look up terminology.

Pepper in the Commercial Market

How this robot compares in the commercial landscape

Current official sales are region/partner-based with no public MSRP on official pages; legacy Japan launch pricing was about ¥198,000 (~$1,800).

The Pepper is listed as Available, indicating an ordering listing. The label does not confirm current stock, regional access, or shipping dates. Check Aldebaran Robotics's current ordering terms and the recorded sales notes for details.

Head-to-Head Comparisons

Side-by-side specs, capability overlap analysis, and key differentiators.

For the full picture of Aldebaran Robotics's portfolio and market strategy, visit the Aldebaran Robotics manufacturer page.

Deployment Readiness and Procurement Signals for Pepper

What the public profile tells you, and what still needs direct vendor confirmation

From a buying and rollout perspective, the Pepper should be read as a commercial platform aimed at service operations that need predictable task throughput. ui44 currently tracks 10 capability signals and a last verification date of 2026-04-17. That mix gives buyers a useful first-pass picture, but it is still only the public layer of due diligence, especially when procurement, uptime, and support commitments are decided directly with Aldebaran Robotics.

Commercial model

See pricing details

Current official sales are region/partner-based with no public MSRP on official pages; legacy Japan launch pricing was about ¥198,000 (~$1,800).

Integration posture

2 connectivity options

The profile lists Wi-Fi 802.11 a/b/g/n (2.4/5 GHz), Ethernet. These labels do not establish APIs, fleet-management features, or workflow integration. These are the platforms, communities, or ecosystem relationships listed in the profile. A listed name or protocol alone does not confirm home-device interoperability or automation support.Recorded AI description: NAOqi OS (Linux-based)

Spec disclosure

5/7 core specs public

ui44 currently has 5 of 7 core physical and operating specs filled in for this model, leaving 2 gaps that matter for deployment planning. Missing runtime, charge, speed, or payload details can materially change staffing and site-readiness assumptions.

The current profile is detailed enough to support early comparison work, shortlist creation, and cross-checking against other commercial robots. It is still worth validating the final deployment package, because integration services, support coverage, software entitlements, and site-preparation requirements often sit outside the raw hardware spec sheet.

If you want a faster apples-to-apples read, compare the Pepper against nearby alternatives in ui44's compare view, then cross-check the underlying AI, sensor, and subsystem terms in the components glossary. For manufacturer-level context, the Aldebaran Robotics profile helps anchor this robot inside the wider product lineup.

Before you sign off on a pilot, confirm these points

  • Clarify usable payload or tool-load limits before planning material handling or mounted accessories.
  • Check what safety, electrical, or deployment certifications exist for the region and task you care about.

Owning the Pepper: Setup, Maintenance & Tips

Practical guide from day one through years of ownership

Initial Setup

Commercial robot deployment is a project, not just a setup. Begin with a site assessment covering floor plans, traffic patterns, integration requirements, and staff training needs. Map the operating environment with the robot, marking restricted areas, service points, and charging stations. Integrate with business systems — POS for restaurants, PMS for hotels, WMS for warehouses. Train staff on robot interaction, troubleshooting, and emergency procedures. Run a supervised pilot period before transitioning to full autonomous operation. Gather and address staff and customer feedback during the pilot to optimize the deployment before scaling.

Ongoing Maintenance

Commercial robots earn their keep through consistent operation, making maintenance an operational priority rather than an afterthought. Establish daily visual inspection routines for operations staff. Schedule weekly maintenance windows for thorough cleaning, sensor calibration, and software updates. Track key performance indicators — delivery times, task completion rates, customer feedback — to detect performance degradation before it becomes noticeable. For food-handling robots, follow strict hygiene protocols including regular sanitization of tray surfaces and contact points. Multi-robot deployments benefit from staggered maintenance schedules to maintain coverage.

Software Updates & Long-Term Support

Commercial robot updates can add new capabilities, improve navigation in your specific environment, and fix operational edge cases. The manufacturer may release updates based on fleet-wide learning — improvements discovered at one deployment benefiting all customers. Test significant updates during low-traffic periods before deploying to your full fleet. Keep communication channels open with your robot vendor's support team to provide feedback that can drive improvement in future updates.

Maximizing Longevity

Commercial robots in daily operation can last three to five years or more with proper care. The primary wear items are wheels, motors, and batteries. Maintain a spare parts inventory for consumables to minimize downtime. Track operating hours and correlate with maintenance needs to develop predictive maintenance schedules specific to your deployment conditions. Consider the total cost of ownership over the deployment lifetime when evaluating robot vendors — the cheapest robot up front may cost more over five years if parts are expensive or support is limited.

Find product and source links on the Aldebaran Robotics page on ui44 or open Aldebaran Robotics's official source. Use model-specific manufacturer documentation for setup, cleaning, and service instructions.

Frequently Asked Questions

What is the Pepper?
The Pepper is a Commercial robot made by Aldebaran Robotics. Aldebaran Robotics' semi-humanoid robot designed to read emotions and interact with people. Introduced by SoftBank in Tokyo in June 2014, Pepper became one of the most recognized social robots in the world — approximately 27,000 units were manufactured before production was paused in June 2021 due to weak demand. The first batch of 1,000 units sold out in 60 seconds in June 2015. Pepper was deployed in SoftBank stores, banks, hospitals, airports, and restaurants across Japan, Europe, and North America. Features a 10.1-inch touch display, emotion recognition via facial expression and voice tone analysis, and a wheeled omnidirectional base. In June 2025, Aldebaran Robotics went into receivership. In July 2025, Shenzhen-based Maxvision Technology Corp. acquired Aldebaran's core assets, including the Pepper and NAO intellectual property.
How much does the Pepper cost?
Current official sales are region/partner-based with no public MSRP on official pages; legacy Japan launch pricing was about ¥198,000 (~$1,800).
Is the Pepper available to buy?
The Pepper is listed as Available, indicating an ordering listing. The label does not confirm current stock, regional access, or shipping dates. Check Aldebaran Robotics's current ordering terms and the recorded sales notes for details.
What sensors are reported for the Pepper?
The profile lists the sensor descriptions below. These entries do not establish physical sensor counts, sensor fusion, redundancy, or performance. RGB Camera ×2 (forehead + mouth), 3D Depth Sensor, Microphone ×4, Gyroscope ×2 (torso + base), Touch Sensors (head, hands), Sonar ×2 (base), Laser Sensor ×6 (base), Bumper ×3 (base) See the sensor information section for details.
How long does the Pepper battery last?
Test conditions and independent verification are not established by these fields. Confirm workload, operating mode and environmental conditions before comparing runtimes. Recorded runtime: ~12 hours (shop use) Recorded charging entry: ~8 hours 20 minutes
What AI does the Pepper use?
The recorded AI description for Pepper is: NAOqi OS (Linux-based)
How does the Pepper compare to the HMND 01 Alpha Wheeled?
The Pepper and HMND 01 Alpha Wheeled are both commercial robots, but they differ in key specifications, pricing, and manufacturer approach. Use the side-by-side comparison tool to see detailed differences in specs, sensors, and capabilities. You can also browse other similar robots.
What platforms or ecosystem relationships are listed for the Pepper?
These are the platforms, communities, or ecosystem relationships listed in the profile. A listed name or protocol alone does not confirm home-device interoperability or automation support. NAOqi SDK, Choregraphe, Android SDK
How current is the Pepper data on ui44?
The Pepper record has a last-checked date of 2026-04-17. Consult the model description, source links, and attribution notes for the basis of individual claims. This date does not mean every claim is manufacturer-confirmed or independently tested. If you notice outdated information, please let us know.

Data Integrity

The Pepper record brings together the listed specifications and attributed claims. Consult the model description and source notes to distinguish manufacturer announcements, reported information, and unknowns. A source link or review date does not establish independent testing or manufacturer confirmation of every claim. Record last checked: 2026-04-17. Official source: Aldebaran Robotics official source. If you find outdated or incorrect information, please let us know — accuracy is our top priority.

Explore More on ui44

Explore more commercial robots

See how the Pepper stacks up — compare specs, browse the commercial category, or search the full database.