Getting started

Install ViteHub, choose a documentation path, and run your first primitive or agent.

ViteHub has one setup flow and two product paths.

Use Server primitives when your app needs storage, background work, schedules, sandboxes, queues, workspace files, or runtime environment values.

Use Agents when your app needs model-backed actors with instructions, invocations, triggers, workspace context, evaluations, and controlled capabilities.

Installation
Add the packages you need and register their ViteHub integrations.
First server primitive
Add KV and call it from ordinary server code.
First agent
Define an Agent and run one invocation from a server route.

Choose the first path

You want to buildStart here
App settings, flags, caches, or small lookup recordsFirst server primitive
Relational data, uploads, background work, workflows, or sandboxesServer primitives
A support agent, code agent, research agent, or workspace-aware assistantFirst agent
Custom model-facing tools or guarded product abilitiesAgent capabilities

Package shape

ViteHub keeps packages small, but the docs are organized by user intent. Install the package that owns the feature you use, then stay in the feature page for host configuration, runtime behavior, and examples.

Cloudflare, Vercel, local, and other host behavior lives inside the feature it changes. There is no separate docs path for host setup.

Copyright © 2026