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.




Support for expressive companion devices, tabletop nodes, wearables, and service endpoints without forcing a single hardware mold.
Modules can be matched to motion, proximity, environment, identity, or check-in flows depending on the experience you need to ship.
Persona rules, approved behaviors, and safety boundaries can be aligned with each physical deployment so the brand behaves consistently.
The same AquaMind control layer can coordinate multiple device types, keeping content, prompts, and reporting aligned across locations.
Rather than one generic box, AquaMind can be mapped to different module categories depending on audience, context, and interaction style.

Best-Fit Use Cases
Emotional Presence
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

Best-Fit Use Cases
Always-On Presence
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

Best-Fit Use Cases
Portable Context
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

Best-Fit Use Cases
Service Endpoint
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
The hardware family shares the AquaMind intelligence layer, but each model is tuned for a different physical context, power profile, and deployment shape.
| Model | Best For | Module Size | Power | Form |
|---|---|---|---|---|
AquaBox I Companion | Character-led companion experiences with a larger emotional and visual presence. | 75 × 55 × 20 mm | 3000mAh onboard battery | PCB 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 mm | 800mAh onboard battery | PCB module, enclosure designed per product |
AquaBox E Wearable | Portable and safety-oriented experiences that move with the user. | 45 × 45 × 18 mm | 2000mAh onboard battery | PCB module, enclosure designed per product |
AquaBox K Kiosk | Public-facing service or registration endpoints with stable wired deployment. | 85 × 55 × 20 mm | Wired power, no battery | PCB module, enclosure designed per product |
DEPLOYMENT APPROACH
Each hardware category can be matched to a different interaction model instead of forcing the same behavior everywhere.
AQUAMIND CONTROL LAYER
The value is not only the device. It is the shared orchestration layer that keeps the mascot coherent across hardware, channels, and locations.
NEXT STEP
We can map the hardware layer to your brand goals, operating environment, and interaction model, then recommend the right starting point for pilot deployment.