Vifu roadmap

The roadmap is organized around complete creator outcomes, not a list of internal tasks. It has no promised dates. A phase is complete only when a new user can finish its workflow with the public repository and documentation.

Phase 1: A complete self-hosted runtime

Status: Available

The current foundation includes:

• a Docker and native self-host path;
• project-scoped Agents and provider connections;
• Canvas and Short Drama editing one source;
• Preview using the real game runtime;
• immutable Game releases and stable project endpoints;
• project keys, logs, analytics, project export, and release export; and
• durable PostgreSQL sessions with reconnectable events.

Start with the Overview or run the full interactive short drama tutorial.

Phase 2: Make the creator journey dependable

Status: In progress

The current priority is to make the existing path shorter and more reliable:

1. start Vifu from a clean checkout;
2. connect a provider and add Agents;
3. build a game from an empty project;
4. preview every branch with real Agent effects;
5. publish one runtime endpoint; and
6. integrate that endpoint into a standalone game.

This phase includes removing dead ends in the Dashboard, improving validation and error messages, keeping docs aligned with the UI, and expanding end-to-end tests around import, publish, restart, and provider failure.

Phase 3: A reusable interactive story workflow

Status: In progress

Short Drama already supports portrait stories, choices, localization, media, Agent interactions, host actions, and multiple endings. The next outcome is a smoother path for two styles of interactive story:

• begin with text and add images, voices, music, or video when needed; or
• begin with a prepared media timeline and add live choices and Agent behavior.

This phase also needs reusable host components so a creator can move the same release from Preview into a real web or engine client with less custom glue.

Phase 4: Language roleplay

Status: Experimental

Explore a focused workflow for roleplay-based language learning: situations, characters, learning goals, speech input, evaluation, feedback, and speech output. It must reuse the same project source, runtime sessions, and endpoint rather than becoming a separate product architecture.

This phase is not available as a supported editor or starter today.

Phase 5: Portable runtime and extensions

Status: Experimental

Explore supported native and WebAssembly embedding, authoring through MCP, reusable experience kits, external node definitions, and a constrained plugin model. These designs must preserve the same release behavior across the Server and embedded hosts.

No stable public extension API is promised yet.

How roadmap items graduate

A roadmap item becomes Available only when it has:

• one complete user journey;
• public documentation and examples;
• local or self-host verification from a clean environment;
• tests for failure, restart, and persistence where relevant; and
• no dependency on an undocumented internal service.

Detailed work-in-progress designs belong on their own status-marked page. The roadmap stays short enough to answer one question: what can I use now, and what is Vifu building next?