Vifu
GitHub

Open-source game runtime

Open Source Game Runtime for AI-Native Games

Design gameplay state, Agent orchestration, and interactive story flows in Canvas or Short Drama. Preview, publish, and run the same backend through one stable project endpoint.

Run Vifu locallyView on GitHub
Example request pathPOST /my-project/v1/game/run
  1. 01Game clientgame.start / choice
  2. 02Vifu Serverauthorize + load release
  3. 03Game Runtimeadvance state graph
  4. 04Agent / hostresolve requested effect
Returnstate + eventssession persisted
Game runtime

Visual source, headless runtime

Design the game backend. Run it as an API.

Canvas and Short Drama write one project source. Publishing compiles it into an immutable runtime that web and native games drive through stateful commands.

  1. 01

    Shared game source

    Canvas and Short Drama edit the same executable project design.

  2. 02

    Agent profiles

    Bind provider-backed Agents to versioned personas and capabilities.

  3. 03

    Stateful sessions

    Choices, Agent effects, host actions, and endings advance one durable state.

  4. 04

    Immutable releases

    Publish a pinned runtime while the next project draft keeps evolving.

POST http://localhost:6790/my-project/v1/game/run
Authorization: Bearer vifu_pk_example
Content-Type: application/json

{
  "host": {
    "engine": "my-game",
    "capabilities": []
  },
  "input": {}
}
Playable demo

Built with Vifu

See one project become a playable anime game.

Last Train to the Moon combines four character Agents, branching state, free-text interactions, host actions, localization, media, and three endings. This playthrough runs against its published Game Runtime endpoint.

Published releaseCanvas and Short Drama compile into the runtime used here.
Built for games

One backend, many presentations

Connect game logic to the experience your players see.

Interactive dramas

Compose scenes, choices, Agent dialogue, media, localization, and endings.

AI NPC systems

Manage character behavior and versions behind one project runtime.

Dynamic quests

Connect player state, conditions, tools, and Agent decisions as a graph.

Engine integrations

Drive the same release from a web game or native engine through its endpoint.

First project

Local and self-hosted

Go from checkout to a playable endpoint.

Run the Apache-2.0 stack, build a project in the Dashboard, test a real session, and publish the runtime your game will call.

  1. 01

    Prepare

    Copy .env.example to .env in the open-source Vifu checkout.

  2. 02

    Start

    Run docker compose up -d to launch PostgreSQL, Vifu, and the Dashboard.

  3. 03

    Connect

    Open localhost:6791, create a project, configure a provider, and add its Agents.

  4. 04

    Publish

    Build in Canvas or Short Drama, run Preview, then publish the project Game endpoint.

Follow the quickstart