Optional by design
Deploy voice-only, voice plus vision or a broader sensor stack without changing the product model.

Connect voice, cameras, VLMs and external sensors to a shared cognitive state for context-aware robot interaction.
Voice alone cannot explain who is speaking, where attention moved or whether the physical situation changed. Embodied systems need a shared state that can combine dialogue with vision and external sensor events.
IronHeart.AI is designed to accept perception from cameras, VLMs, microphones, proximity sensors and product-specific modules. These inputs do not automatically grant authority to act; they update context that remains subject to runtime policy.
The product can therefore start voice-only and add vision or sensors when the hardware and use case justify them, without rebuilding the conversational stack.
A configurable cognitive runtime—not a one-size-fits-all robot personality. Partners purchase managed Cloud API access or scope edge, offline, private-cloud and OEM production licensing with integration support.
Deploy voice-only, voice plus vision or a broader sensor stack without changing the product model.
Resolve perception events and conversation inside the same interaction timeline.
Treat perception as evidence and apply confidence, consent and action rules before execution.
A useful embodied system cannot treat voice, memory and action as unrelated calls. IronHeart coordinates the modules around the live person, environment, role and task.
Each module can be configured per robot or product while published versions preserve a reproducible operational state.
Receive audio, video, proximity or product-specific events.
Convert heterogeneous inputs into timestamped runtime signals.
Relate signals to dialogue, identity, memory and the active task.
Coordinate voice, gaze and allowed actions with traceable context.
Primary buyer: Teams building social, service, education, healthcare and hospitality robots that need situational interaction.
What to measure: Evaluate attention accuracy, false perception handling, consent, latency and whether the robot explains uncertainty appropriately.
Required controls: Sensor enablement, confidence thresholds, identity rules, retention policy and action consequences.
Prototype and launch with managed realtime runtime services and the published API plans.
Review pricing →Scope interaction-critical components for supported device or nearby edge hardware.
Discuss edge deployment →Run inside customer-controlled infrastructure with an enterprise integration agreement.
Request enterprise scope →| Foundation model for | Social interaction across perception, voice, memory, personality, gaze and actions. |
|---|---|
| Partner retains | Hardware, customer experience, business rules, data policy, safety authority and go-to-market. |
| IronHeart provides | Runtime configuration, cognitive modules, adapter contract, versioned publication and deployment support. |
| Commercial path | Cloud API subscription for evaluation; custom scope for edge, offline, private cloud and OEM production. |
No. Multimodality is optional and can use external perception modules selected by the partner.
Storage and retention depend on the configured deployment and data policy; unnecessary raw data does not need to be retained.
Yes, where hardware and model choices support device-local or private inference.
Tell us about the embodiment, use case and deployment constraints. We will map the fastest evaluation path.