ViteHub

Choose a Package

Pick the right ViteHub feature by the job you need to solve on the server.

ViteHub works best when you start from the problem you need to solve, not from the package list. Use the groups below to narrow down the primitive you want, then open the package overview for installation and provider-specific setup.

Data

These packages store, retrieve, or derive state for your app.

Database
Add an ORM-first database layer with Drizzle or Prisma and generated runtime imports.
KV
Store keyed values behind a small API when you do not need relational queries.
Cache
Cache derived values with hosting-aware defaults and provider-backed stores.
Blob
Store files and unstructured assets such as images, documents, and uploads.
Vector
Define named vector indexes and run provider-agnostic similarity search against them.

Async and Automation

These packages move work out of the current request, run scheduled work, or execute remote environments.

Queue
Send retried, delayed, or provider-backed jobs out of band.
Workflow
Run durable multi-step processes that need state, retries, and resumability.
Cron
Schedule recurring work and keep the handler callable manually.
Sandbox
Run isolated execution environments on Cloudflare, Vercel, Deno, or Docker.
Browser
Drive remote browser sessions for screenshots, scraping, crawling, and PDF generation.

Integration and Output

These packages send data out of your app or connect ViteHub to external delivery systems.

Email
Author named emails in files and send them through provider-backed delivery adapters.
Analytics
Send page views and events through hosted analytics providers with one runtime call.
If two packages seem close, prefer the one that matches the runtime behavior you need. Use Queue for independent jobs, Workflow for coordinated multi-step state machines, Cache for disposable derived data, and KV for durable keyed values.

Before you open a package page

  • Read Entrypoints if you are unsure which import surface to use.
  • Read Architecture if you want to understand how Vite, Nitro, and Nuxt share the same feature bridge.

Overview

Learn the ViteHub package model, pick a starting path, and get to a working feature quickly.

Entrypoints

Understand what belongs on the package root and what each framework-specific entrypoint owns.