Continuous state
Maintain conversational, emotional and operational context across turns, interruptions and sessions.

Build stateful robot conversations with realtime voice, perception, persistent memory, personality, gaze coordination and actions in one cognitive runtime.
Traditional voice AI maps text to sound one response at a time. That is useful for narration, but a social robot needs a continuous operating state: who is present, what just happened, which relationship is active, where attention should move and what action is safe next.
IronHeart.AI treats voice as part of the cognitive loop. Perception, dialogue state, memory, personality, gaze and actions update one another during the interaction. The voice can therefore preserve identity and conversational direction instead of restarting with every generated message.
Robot OEMs and system integrators use this layer to create a governed interaction model for a specific body, environment and role. The result is not a generic chatbot mounted inside hardware. It is runtime infrastructure for embodied social behavior.
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.
Maintain conversational, emotional and operational context across turns, interruptions and sessions.
Coordinate who the robot listens to, looks at and addresses while the room keeps changing.
Connect speech to approved tools, workflows and robot actions with deterministic boundaries.
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.
Cameras, microphones and sensors update the current interaction state.
Dialogue, identity, memory and environment context are resolved together.
Voice, gaze, personality and action policy select a coherent response.
The robot speaks, directs attention or invokes an approved physical or digital action.
Primary buyer: Robot OEMs, social robotics teams, device manufacturers and system integrators building customer-facing embodied AI.
What to measure: Evaluate interruption recovery, turn-taking, identity continuity, attention shifts, response timing and safe action completion—not only transcript quality.
Required controls: Per-robot personality, memory policy, knowledge boundaries, voice identity, gaze behavior and action permissions.
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. Realtime voice is one coordinated module inside the wider cognitive runtime.
Yes. Hardware-specific perception and action adapters connect to a reusable cognitive layer.
No. Teams can combine managed API, edge and private-cloud components according to latency, privacy and hardware constraints.
Tell us about the embodiment, use case and deployment constraints. We will map the fastest evaluation path.