Vifu
DashboardGitHub

Open-source Agent Runtime

A small, fast, stateful, and portable runtime for agents.

Connect applications to agents from local or remote providers through one runtime for stable APIs, durable state, access control, routing, and traces.

Run Vifu locallyView on GitHub
Example request pathPOST /my-project/v1/chat/completions
  1. 01Application clientsend project request
  2. 02Vifu Serverauthorize + route
  3. 03Agent Gatewayresolve provider
  4. 04Providerrun Agent
Returnresponse + tracerequest persisted
Runtime

One model, two deployment shapes

Embed it in an application or run it as a service.

A self-contained VifuRuntime calls host-registered providers directly. Vifu Server reuses that invocation model and adds multi-project APIs, access control, database state, and traces.

  1. 01

    One runtime, one project

    Keep the providers, Agents, endpoints, sessions, and effects for one application together.

  2. 02

    Dynamic providers

    Register provider capabilities at runtime instead of compiling a feature for each vendor.

  3. 03

    Stable named endpoints

    Let application code call the same endpoint while the Agent or provider behind it changes.

  4. 04

    Stateful sessions

    Use host storage or portable snapshots with async and game-loop invocation APIs.

EMBEDDED
Application
  └─ VifuRuntime
       └─ local or remote provider

SERVICE
Application
  └─ Vifu Server
       ├─ provider
       └─ Agent Gateway → provider
Operations Console

Operate the deployment

Manage the runtime without hiding its infrastructure.

The lightweight Console shows projects, Agents, providers, API keys, Gateway connections, and traces from the same Vifu deployment.

Vifu operations Console showing a local runtime deployment
Self-hosted deploymentThe Console and public APIs operate the same runtime.
Plugins

One core, product-specific behavior

Extend Vifu without forking the runtime.

Use an embedded plugin for in-process behavior, a runtime service plugin for an independent backend, or a Gateway integration for an Agent Provider.

Embedded runtime plugins

Add application behavior as Bevy systems inside the portable Rust runtime.

Runtime service plugins

Connect an application-specific state machine or compiler through the HTTP and JSON-RPC extension contract.

Provider integrations

Implement an in-process provider or use Agent Gateway as the remote transport for Vifu Server.

Product plugins

Keep product-specific state, tools, content, and UI outside the reusable runtime core.

First deployment

Local and self-hosted

Go from checkout to a callable project endpoint.

Run the Apache-2.0 stack, configure a provider in the Console, create a project key, and make a real request.

  1. 01

    Install

    Run the Vifu installer to select the current GitHub Release binary for your Mac, Linux, or Windows machine.

  2. 02

    Start

    Run the vifu binary to start the local Runtime, Agent Gateway, TUI, and embedded Dashboard.

  3. 03

    Operate

    Watch live Agent activity in the TUI and press B to open the same Runtime in the Dashboard.

  4. 04

    Call

    Connect a provider, call the stable project endpoint, and inspect its trace.

Follow the quickstart