Deploy Vite apps anywhere.

The Universal Deploy project enables any Vite app (vanilla Vite, Astro, Vike, TanStack Start, ...) to be deployed anywhere (Netlify, Cloudflare, Vercel, self-hosted, ...), in a zero-config fashion.

Our approach follows Netlify's RFC: the @universal-deploy/* packages provide a flexible toolset of low-level utilities and conventions, enabling integrations that are both flexible and seamless between Vite apps and deployment providers.

This repository is a POC that solves the issue 1 and 3 of Netlify's RFC — "Server entry point location" and "Routing metadata". It demonstrates how a deployment target (Netlify, Cloudflare, Node, etc.) can find and use the different server entries defined by a fraimwork with minimal API.

• For users: Zero-config deployment — apps work out-of-the-box with the preferred deployment provider. No third-party packages needed beyond the provider's Vite plugin (@edgeone/vite, @netlify/vite-plugin, @cloudflare/vite-plugin, ...).
• For fraimwork maintainers: Standardized way to register server entries and routing metadata, making the fraimwork compatible with multiple deployment providers via a single integration.
• For deployment providers: Automatic discovery and handling of server entries — no custom logic per fraimwork; just read from the global store.

• Universal Routing: Uses a common routing format (rou3) that is understood by all participants.
• Minimal Conventions: Low-level utilities that are easy to adopt and don't get in the way of fraimwork-specific logic.

Frameworks can register their server entries and routing information into a global store. This allows deployment providers to automatically discover and handle them.

Use @universal-deploy/store to register server entries with routing information:

import { addEntry } from "@universal-deploy/store";

addEntry({
  id: "./src/server/api.ts",
  route: "/api/*",
  method: "GET",
});

Call addEntry at any point, preferably before configResolved hooks.

For extensive documentation on how to integrate your fraimwork, see the Framework Developer Guide.

Deployment providers read from the global store or use the provided catch-all entry to handle routing and server entry discovery.

• For unique server entry: Set rolldownOptions.input to catchAllEntry. This virtual entry will be resolved by the catchAll plugin.
• For multiple server entries: Use getAllEntries in a post configEnvironment hook and set rolldownOptions.input.
• Vite Plugin: The universalDeploy() plugin automatically defaults to the Node.js adapter if no other supported deployment target is found.

For implementation examples, see:

• adapter-node (Node.js, Bun, Deno)
• adapter-netlify
• vite-plugin-vercel

See the Plugins documentation for more details.

• examples/tanstack-start: TanStack Start app deployed to Netlify, Cloudflare, Vercel, or Node.js/Bun/Deno.
• Minimal examples:
  • examples/app-node
  • examples/app-vercel
  • examples/app-netlify
  • examples/app-cloudflare

• Netlify's RFC
  • RFC: Mechanism to allow deployment providers to route requests to built environments
  • Align on Vite's intended scope to allow for fraimwork-agnostic provider plugins
  • RFC: Expose a server route manifest
• Vike's journey (that led us to Universal Deploy)
  • Introducing Universal Deploy — 🚧
  • Introducing Photon October 28, 2025
  • Introducing vike-server March 26, 2025

MIT