# Frameworks and hosts

Use this section to choose where your application runs. You select one
framework integration and one deployment preset. ViteHub then discovers your
Definitions during the build and writes the files and bindings that the host
needs. Application code keeps using ViteHub imports instead of generated paths
or provider SDKs.

## Choose a framework

| Framework | Register | Guide |
| --- | --- | --- |
| Vite | `vitehub()` from `vite-hub` and `nitro()` from `nitro/vite` | [Installation](https://vitehub.dev/docs/getting-started/installation) |
| Nuxt | The `vite-hub/nuxt` module | [Nuxt](https://vitehub.dev/docs/frameworks-hosts/nuxt) |

Both integrations use Nitro to build the server output.
[Nitro and UnJS](https://vitehub.dev/docs/frameworks-hosts/nitro-unjs) explains where ViteHub
packages register Nitro handlers.

To move a Nuxt application from NuxtHub, read
[Migrate from NuxtHub](https://vitehub.dev/docs/getting-started/migrate-from-nuxthub).

## Choose a preset

`preset` is required. It selects the host, the Nitro preset, and the provider
that each enabled feature uses by default.

| Preset | Guide | Production output | Default providers | Rejected when enabled with `true` |
| --- | --- | --- | --- | --- |
| `node` | [Node and self-hosted](https://vitehub.dev/docs/frameworks-hosts/node-self-hosted) | `.output/server/index.mjs` | Blob `fs`, KV `fs-lite`, Rate Limit `memory` | Queue, Sandbox |
| `cloudflare` | [Cloudflare](https://vitehub.dev/docs/frameworks-hosts/cloudflare) | `.output/server/wrangler.json` | Blob R2, KV Workers KV, Queue, Rate Limit, and Sandbox on Cloudflare | None |
| `vercel` | [Vercel](https://vitehub.dev/docs/frameworks-hosts/vercel) | `.vercel/output/**` | Blob Vercel Blob, KV Upstash Redis, Vercel Queues, Vercel Sandbox | Rate Limit |
| `netlify` | [Netlify](https://vitehub.dev/docs/frameworks-hosts/netlify) | `.netlify/**` | Blob Netlify Blobs | Queue, Rate Limit, Sandbox |
| `deno` | [Deno](https://vitehub.dev/docs/frameworks-hosts/deno) | `.output/server/index.mjs` | KV Deno KV | Blob, Queue, Rate Limit, Sandbox, Schedule |

A rejected feature fails the build. It does not fall back to another provider.
Browser and `email: true` require the `cloudflare` preset. Blob without an
explicit store also requires a preset with a Blob provider. When KV has no
explicit driver, every preset except `deno` selects Upstash Redis if
`KV_REST_API_URL` and `KV_REST_API_TOKEN` are set during the build.

ViteHub sets the Nitro preset. The build fails when `nitro.preset`,
`NITRO_PRESET`, or `SERVER_PRESET` selects a different one. The
[support matrix](https://vitehub.dev/docs/frameworks-hosts/support-matrix) lists every primitive
for every host, including explicit provider choices.

## Keep runtime imports stable

Import server APIs through documented ViteHub paths. The same code runs on every
preset. Do not import framework virtual modules or generated files unless a
reference page marks the path public.

```ts [server/settings.ts]
import { kv } from 'vite-hub/kv'

export async function saveSettings(settings: Record<string, unknown>) {
  const [error] = await kv.set('settings', settings)
  if (error) throw error
}
```

Libraries and focused integrations can register an individual `hubX()`
integration from its `@vite-hub/*/vite` package instead of `vitehub()`.

## Inspect the output

Vite development proves discovery and local generation. A production build
writes the output for the selected preset. List the generated host files with
the CLI.

```bash [Terminal]
pnpm build
pnpm vitehub inspect provider-output
```

## Next steps

- Read [Production deployment](https://vitehub.dev/docs/frameworks-hosts/production) before you serve traffic.
- Use [Provider output](https://vitehub.dev/docs/reference/provider-output) for generated host artifacts.
- Use [File conventions](https://vitehub.dev/docs/reference/file-conventions) for discovery paths.
- Use [Local development](https://vitehub.dev/docs/development) for local checks.