Skip to content

Overview

Vifu helps creators deploy AI-native games and interactive entertainment with minds across device runtimes.

Use Vifu when your game needs minds, hosted AI, save state, companion actions, runtime resources, preview links, or a path to publish on vifu.ai without building a custom backend first.

What Vifu Provides

PartWhat it does
Vifu CLIBuilds, validates, deploys, and publishes local game projects.
Vifu SDKBrowser API for AI, tools, resources, and save state.
Vifu RuntimeControlled iframe host that loads deployed static web games.
Vifu CloudAuth, AI provider routing, quota, game state, runtime assets, and publish APIs.
manifest.jsonCreator-facing file that declares the game entry, build output, and platform features.

Vifu does not replace your engine. You can use Vite, Angular, Phaser, Pixi, Three.js, plain HTML, or another static web stack. The requirement is that the deployed game builds to browser files with an HTML entry point.

The Developer Loop

bash
npm create @vifu/vifu my-game -- --template vanilla --no-interactive
cd my-game
vifu deploy

For existing projects:

bash
cd path/to/game
vifu deploy

vifu deploy checks the manifest, builds the project, checks the built output, uploads it, and prints a playable URL.

What Makes A Game AI-native

AI-native means AI is part of play, not only part of development.

Examples:

  • an NPC that responds through Vifu AI
  • a mystery game that interprets player commands
  • a quiz game that gives personalized feedback
  • a speaking game that uses speech input or TTS
  • a companion game that observes gameplay and triggers game-owned actions
  • a utility app that uses AI while saving user-owned state

Platform Boundary

The game owns:

  • rendering, input, rules, game state, content, and assets
  • which state is safe to expose to AI
  • which actions AI or companion features may ask the game to run

Vifu owns:

  • runtime hosting, iframe isolation, AI provider routing, auth, quota, publish records, runtime resource URLs, and backend service access

That is why deployed games should call Vifu through the SDK instead of calling external AI or backend APIs directly.

Start Here

  1. Install the CLI and SDK.
  2. Follow the Quickstart.
  3. Read the Manifest Reference.
  4. Understand the Deploy Policy.
  5. Use Troubleshooting when deploy or runtime checks fail.