Vifu Runtime
Vifu Runtime lets games and interactive apps connect to a persistent AI companion during each user session. Vifu Cloud keeps the companion identity, memory, session history, AI interpretation, and personalization layer. Runtime surfaces load the experience and provide the bridge that lets the companion understand safe context and react through app-owned actions.
Platform model
| Layer | What Vifu provides | What the game owns |
|---|---|---|
| Vifu Cloud | Auth, database, companion identity, companion memory, AI interpretation, release hosting, and runtime manifests. | Player-facing product data and metadata submitted through the release workflow. |
| Web Runtime | Browser iframe host, static asset loading, companion bridge, lifecycle events, and runtime isolation. | HTML, JavaScript, assets, rendering, input, and session rules. |
| Mobile Runtime (To be released) | Native app runtime surface for approved browser-compatible experiences and Godot-powered modules. | Browser-compatible assets, Godot modules, shared metadata, and companion-safe state/actions. |
| Companion SDK | Typed browser API for safe context, events, commands, signals, and host connection status. | Which state is safe to expose and which actions the companion may request. |
| Vifu CLI | Local create, run, test, build, generate, and publish workflows. | Source code, test expectations, and release intent. |
How they work together
- Build the game or interactive experience as browser-compatible assets or a supported Godot module.
- Use the Companion SDK only for safe session context, events, and actions the companion may use.
- Use the Vifu CLI to run, test, build, and publish the experience.
- Vifu Cloud stores release metadata, session history, companion memory, and AI interpretation.
- The Web Runtime or Mobile Runtime (To be released) loads the experience through the matching browser or Godot surface and connects it to the companion bridge.
Naming
Use Vifu Platform when talking about the whole product. Use Vifu Cloud for hosted backend services. Use Vifu Runtime for the web, mobile browser, and Godot-capable mobile surfaces that execute games. Use Companion SDK for the in-game browser API. Use Vifu CLI for local development and publishing.