ViteHub
ViteHub is still experimental. Expect bugs and breaking changes.

Runtime and host support

Compare ViteHub runtime, output, provisioning, and proof across supported hosts.

Available Package-specific Local-only Not provided
ContractDevelopmentHosted providersRuntimes
Local ViteCloudflareVercelNetlifyDenoNitro / UnJSNode / self-hosted
Runtime
Runtime helpersApplication imports and handlers
Local providersState and execution without a cloud account
Server primitives
BrowserProvider-backed browser operations
BlobObject storage
DatabaseNamed SQL databases
EmailTransactional email delivery
KVKey-value storage
QueueMessage delivery
Rate LimitAtomic request budgets
RealtimeAuthoritative collaborative rooms
SandboxIsolated command execution
ScheduleStatic and runtime schedules
WorkflowDurable execution
WorkspaceAgent file-tree state
Output
Provider outputGenerated deployment files
ProvisioningResources ViteHub can create
Proof
Contract testsSource and generated-output assertions
Local provider runBuilt output exercised in CI
Live smokeShared playground deployed nightly

Qualifications

Select any status to inspect its package, provider, durability, and proof boundaries.

  • Local Vite: Active integrations expose their package imports and generated registries. Blob fs, KV fs-lite, Rate Limit memory, and Workspace local or memory provide local state. A local build can still generate output for an explicit or inferred hosted provider.
  • Cloudflare: Blob, Database, KV, Queue, Rate Limit, Sandbox, Schedule, Workflow, and Workspace run in the live playground. Browser and Agent have package-owned output outside the nightly run. Enabled integrations compose the Worker, wrangler.json, bindings, callbacks, and runtime modules. ViteHub can provision R2 buckets, D1 databases, and Cloudflare Queues.
  • Vercel: Blob, Database, KV, Queue, Sandbox, Schedule, Workflow, and Workspace run in the live playground. Agent routes have separate package output outside the nightly run. Enabled integrations write Vercel Build Output, functions, routes, cron entries, and runtime modules. ViteHub can create a Blob store and configure the project environment.
  • Netlify: Blob uses netlify-blobs. Agent HTTP routes and static Schedules write functions under .netlify/v1/functions. CI runs the real-project fixture through Netlify CLI. ViteHub does not provide Netlify provisioning or published live proof.
  • Deno: Agent chat and webhook routes and KV with deno-kv are supported with their documented permissions. The standalone Schedule integration writes a Deno.cron entrypoint, but vitehub({ preset: "deno", schedule: true }) rejects Schedule because that output is outside the deployed Nitro entrypoint. ViteHub does not generate a general Deno bundle or publish live proof.
  • Nitro and UnJS: Auth and Agent handlers, the Schedule Nitro bridge, Workspace runtime setup, and Database Nuxt D1 wiring are package-owned integrations. Nitro is integration glue rather than a storage or execution provider. ViteHub does not provide Nitro provisioning or one unified live matrix.
  • Node and self-hosted: Server APIs and handlers run when their selected driver supports Node. Blob fs, KV fs-lite, Rate Limit memory, and Workspace local or memory are single-process providers. ViteHub does not emit one Node deployment bundle, provision a self-hosted plan, or publish one live suite.

Local memory and filesystem providers stay single-process after deployment. Generated files remain package-owned and must not be imported by application code.