SUPPORTED HARDWARE MODULES

HARDWARE THAT FITS THE EXPERIENCE

AquaMind is designed to extend beyond chat windows into physical devices, ambient touchpoints, and deployment-ready modules that make your AI mascot visible, useful, and context-aware in the real world.

Companion Mascot Module
COMPANION
Ambient Environment Node
AMBIENT
Wearable Safety And Tracking Module
WEARABLE
Kiosk And Service Module
KIOSK

Interaction-Ready Form Factors

Support for expressive companion devices, tabletop nodes, wearables, and service endpoints without forcing a single hardware mold.

Sensor-Aware Intelligence

Modules can be matched to motion, proximity, environment, identity, or check-in flows depending on the experience you need to ship.

Governed At The Edge

Persona rules, approved behaviors, and safety boundaries can be aligned with each physical deployment so the brand behaves consistently.

Cloud-Orchestrated Rollout

The same AquaMind control layer can coordinate multiple device types, keeping content, prompts, and reporting aligned across locations.

DEPLOYMENT TYPES

A practical hardware layer for different environments

Rather than one generic box, AquaMind can be mapped to different module categories depending on audience, context, and interaction style.

Companion Mascot Module
COMPANION

Best-Fit Use Cases

  • Bedside or home companion experiences
  • Hospitality gifting, loyalty, and premium membership programs
  • Retail and brand storytelling moments that benefit from emotional attachment

Emotional Presence

Companion Mascot Module

AquaBox I

A soft, character-led endpoint for brands that want warmth, memory, and daily interaction. This format is suited to mascots that need to feel personal, expressive, and visibly alive rather than purely utilitarian.

AquaMind Layer

  • Persona-specific voice, mood, and conversational behavior
  • Scheduled routines, nudges, and lightweight memory callbacks
  • Character-driven responses synced with brand tone and campaign logic
Ambient Environment Node
AMBIENT

Best-Fit Use Cases

  • Desktop or room-based assistance in homes, studios, and offices
  • Ambient notification, sensing, or light interaction scenarios
  • Branded smart-space experiences for hospitality or premium retail

Always-On Presence

Ambient Environment Node

AquaBox M

A minimal hardware endpoint for desks, rooms, stores, or smart spaces where the intelligence should blend into the environment. It works well when the brand should feel present, responsive, and contextually aware without demanding full-screen interaction.

AquaMind Layer

  • Environment-aware triggers based on presence or local conditions
  • Quiet brand moments through audio, light, or subtle prompt flows
  • Centralized orchestration across multiple distributed nodes
Wearable Safety And Tracking Module
WEARABLE

Best-Fit Use Cases

  • School, campus, or family-oriented safety experiences
  • Location-aware routines and guardian alerts
  • Portable identity or check-in workflows for controlled environments

Portable Context

Wearable Safety And Tracking Module

AquaBox E

A portable module category for experiences that move with the user. It is appropriate when identity, location, or safety context matters and the AI layer needs to respond to movement, presence, or routine in a lightweight form.

AquaMind Layer

  • Policy-aware notifications tied to time, zone, or routine
  • Lightweight user state and movement context for AI behavior
  • Connection to parent, operator, or back-office dashboards
Kiosk And Service Module
KIOSK

Best-Fit Use Cases

  • Clinic, venue, or front-desk self-service experiences
  • Retail onboarding and guided product discovery
  • Reception, registration, and wayfinding workflows

Service Endpoint

Kiosk And Service Module

AquaBox K

A public-facing endpoint for registration, check-in, information access, or branded self-service. This is the right format when the mascot needs to guide, greet, or assist in semi-structured physical environments.

AquaMind Layer

  • Persona-guided check-in and structured service conversations
  • Queue, workflow, or handoff support inside physical operations
  • A consistent branded interaction layer across multiple kiosk locations
MODEL COMPARISON

Choose the right AquaBox starting point

The hardware family shares the AquaMind intelligence layer, but each model is tuned for a different physical context, power profile, and deployment shape.

ModelBest ForModule SizePowerForm
AquaBox I
Companion
Character-led companion experiences with a larger emotional and visual presence.75 × 55 × 20 mm3000mAh onboard batteryPCB module, enclosure designed per product
AquaBox M
Ambient
Compact room or desk nodes where quiet presence matters more than screen-led interaction.50 × 35 × 16 mm800mAh onboard batteryPCB module, enclosure designed per product
AquaBox E
Wearable
Portable and safety-oriented experiences that move with the user.45 × 45 × 18 mm2000mAh onboard batteryPCB module, enclosure designed per product
AquaBox K
Kiosk
Public-facing service or registration endpoints with stable wired deployment.85 × 55 × 20 mmWired power, no batteryPCB module, enclosure designed per product

DEPLOYMENT APPROACH

Designed to fit the physical setting

Each hardware category can be matched to a different interaction model instead of forcing the same behavior everywhere.

  • Use companion formats where emotional connection and repeat engagement matter most.
  • Use ambient nodes where the AI should be present without becoming visually dominant.
  • Use portable modules where safety, identity, or mobility creates the core value.
  • Use kiosk endpoints where the brand needs to guide users through a structured service flow.

AQUAMIND CONTROL LAYER

One brand system across multiple modules

The value is not only the device. It is the shared orchestration layer that keeps the mascot coherent across hardware, channels, and locations.

Shared persona, prompt, and guardrail management
Consistent multilingual responses across device categories
Campaign, content, and seasonal behavior updates from one control surface
Operational visibility across physical deployments and software touchpoints

NEXT STEP

Need help choosing the right module mix?

We can map the hardware layer to your brand goals, operating environment, and interaction model, then recommend the right starting point for pilot deployment.