Runtime Channel

The runtime channel describes the hosted execution environment for Vifu games. It is separate from npm package releases.

@vifu/cli and @vifu/hub help developers build, validate, and deploy games. The runtime channel controls how approved games are loaded by Vifu Web and Vifu Mobile.

backend service

Vifu Cloud

vifu-cloud

Managed backend services for auth, database, companion state, AI, release metadata, and runtime manifests.

Channel

public alpha

public runtime

Web Runtime

web-runtime

Iframe runtime for approved HTML, Canvas, Phaser, Pixi, Three.js, and Godot web-export games.

Channel

public alpha

runtime surface

Mobile Runtime (To be released)

mobile-runtime

Native runtime surface for approved browser-compatible games and Godot-powered game modules. To be released.

Channel

compatible alpha

Tools

@vifu/hub

Official utilities to use the Vifu Hub API.

@vifu/cli

CLI for building, testing, deploying, and publishing AI-native games.

Current Scope

• Web Runtime: public alpha for iframe-hosted browser games.
• Mobile Runtime: planned native loading path for approved browser-compatible games and Godot-powered game modules.
• Vifu Cloud: managed auth, AI services, save state, resources, token metering, release metadata, and runtime manifest services.
• Vifu Hub SDK bridge: use the @vifu/hub module namespace for host services.
• Security boundary: reviewed runtime artifact, Vifu Hub SDK bridge, restricted network, and category-specific CSP for static resources.

Games should treat the runtime channel as the contract for loading, isolation, bridge behavior, and backend services provided by Vifu.