Humanoid robotics.

ROBONEX is a Swiss integrator for humanoid robotics in B2B settings. The company combines robot selection, software, enterprise data, safe commissioning, monitoring, service and support into a controlled solution. The focus is not on show effects but on measurable use cases, clear operating boundaries and integration into the customer's existing processes.

ROBONEX delivers more than hardware: it plans, integrates and operates humanoid robotics solutions. That includes use-case analysis, data model, system adapters, safety concept, tablet UI, monitoring, service processes and clear escalation to people. A robot is only recommended when location, value, data readiness, operations team and risk align.

ROBONEX positions itself first as a Swiss Humanoid Robotics Integrator for Swiss companies and sites. Early market focus is on controllable environments such as reception, retail, events, campuses and showrooms in Switzerland. Projects with EU scope can be reviewed but need additional privacy, contractual and operating clarifications.

The ROBONEX AI Reception Desk V1 is a stationary humanoid reception solution with a separate tablet. The robot sits or stands at a fixed, approved workstation, speaks with visitors, uses vetted data sources, performs only approved gestures and directs attention to the screen. The tablet shows details, maps, route steps, QR codes and other confirmed information.

The AI Reception Desk should be treated as DEMO software with a prepared physical pilot deployment. Production status follows site review, safety approval, data sign-off, integration tests, operating process, support model and documented acceptance criteria. Public copy must not claim that every module already runs in production at customers.

No. Version 1 is intentionally stationary and does not move autonomously through the building. The robot works at a fixed, bounded position and shows at most the first legal segment of a route. Full wayfinding, including map, stages, QR code and accessibility options, is provided on the independent tablet.

The robot handles personal address, speech, confirmed gestures and simple directional cues. The tablet handles precise display: search results, maps, route steps, QR codes, forms, error states and longer information. This split is intentional so the screen stays useful when voice, gesture or robot connectivity is limited.

The initial focus is de-CH and English; further languages are approved per pilot. The website is already structured for de-CH, en-CH and fr-CH so Swiss audiences are addressed cleanly. For the robot, translation alone is not enough: data quality, pronunciation, terminology, fallback phrases and customer sign-off matter.

Operational facts come from approved databases or controlled APIs. The language model must not invent prices, opening hours, promotions, floors, routes, availability or booking confirmations. The final answer is composed from validated data; if data is missing, the system states this openly and offers contact, tablet information or human handoff.

Wayfinding uses a graph of permitted nodes and links, not a straight line. The system considers floors, public passages, lifts, stairs, accessible routes and temporary closures. The robot shows only the first legal direction segment while the tablet provides the full route with steps and QR code.

No. The language model does not directly control the physical robot. It does not generate joint positions, torque, speeds or free motion commands. The application interprets the request, fetches facts from data sources and produces validated speech, ScreenCommand for the tablet and at most one allowed RobotCommand action from the allowlist.

The robot may only execute approved actions from a closed allowlist. Examples include WELCOME, SHOW_TABLET, POINT_LEFT, POINT_RIGHT, POINT_FORWARD, CONFIRM, GOODBYE, REST and STOP. Free angles, untested gestures, simultaneous motions or AI-generated motion commands are not part of the public or technical V1 contract.

On errors the system does not trigger new movement. A model error, API error, data error or connectivity issue leads to a safe fallback: REST or STOP, a clear message on the tablet, a technical alert and handoff to human support. The robot must never pretend a missing fact is confirmed.

By default raw audio or raw video recordings are not stored. Face recognition is not planned for the MVP; a camera may at most provide an anonymous presence hint or read QR codes if approved in the site concept. Anonymous session data is kept briefly and deleted after departure or timeout.

Before a pilot we review privacy roles, transparency duties, data minimisation, retention, access, tenant separation, site approval, safety processes and human fallback. Swiss DSG applies for Swiss customers; GDPR may additionally apply with EU scope. CE duties, standards, e-stop and site-specific safety approvals are clarified with specialists per project.

No. Pinnex, RechNex and Prorum must be treated as CONCEPT adapter targets until documented API contracts, field mapping, privacy review and integration tests exist. Public copy must not present these systems as production-connected. Only after passed tests and sign-off can a single adapter receive a higher status.

ROBONEX integrates customer systems through separate, validated adapters rather than free model answers. An adapter needs API contract, authentication, field mapping, error behaviour, timeouts, retry rules, logging, privacy review, tests and traceable sign-off. Write actions such as bookings also need clear user confirmation and a controlled response from the target system.

Yes, ROBONEX can assess purchase, rental, event deployment and Robot-as-a-Service as distinct models. The right form depends on objective, duration, site, supervision needs, integration scope, service level and risk. A short trade-fair appearance, a multi-month pilot and a permanent reception system are therefore not priced the same way.

A project starts with a use-case workshop on site or remote. We then define site, audience, data sources, integrations, safety boundaries, pilot KPIs, supervision, support and acceptance criteria. Price is not taken from a public list but from hardware, software scope, integration, operation, service level and deployment duration.

ROBONEX suits controlled information, reception and advisory environments first. That includes shopping centres, hotels, events, corporate reception, campuses, premium retail and showrooms when site, data and safety fit. The separate AI briefing or finance presenter format is CONCEPT: curated sources, clear labelling, human approval and no investment advice.