Overview
Vike started about five years ago as vite-plugin-ssr and describes its goal as a framework with a stable core and hooks that let you plug in fast-moving tools. Rather than owning your UI layer, it offers extensions such as vike-react, vike-vue and vike-solid, and works with servers like Hono, Express.js, Fastify and Elysia. Pages choose SPA, SSR or SSG individually through config files, with filesystem routing, layouts, data fetching, route guards, HTML streaming and CSP support built in.
Deployment is flexible: self-hosting, Cloudflare, Vercel, AWS, Netlify, Google Cloud and EdgeOne are listed. Because Vike sits on Vite and standard servers, it suits teams that want to keep an existing backend, including non-JavaScript ones, and add server rendering.
Vike's business model is unusual. Its pricing page describes planned Open Source Pricing: free for small teams and small organisations, with larger organisations paying for a licence key that removes a development-time notice. The model is not in effect yet. The repository remains MIT, but the npm package would move to a proprietary licence once it starts.
Pricing and plans
| Plan | Price | What you get |
|---|---|---|
| Small team (2 developers or fewer) | $0 | Free forever, no licence key |
| Larger team, small organisation | $0 | Free, per the planned Open Source Pricing |
| Larger team, larger organisation | Custom | Planned one-time lifetime licence; not implemented yet, and no final price announced |
What it does
- UI-agnostic core
- React, Vue, Solid, Angular and others through official or community extensions.
- Per-page rendering
- +config.js files set SSR, SPA or SSG for sections of the site.
- Any backend
- Integrates with Hono, Express.js, Fastify, Elysia, or non-JS backends via APIs.
- Rendering hooks
- Hooks such as onRenderHtml and onBeforeRenderClient give low-level control of rendering.
- Built-in routing and guards
- Filesystem routing, layouts, route guards and client routing.
Strengths and limitations
Strengths
- Does not lock you into one UI library or server.
- Designed for long-term stability, keeping fast-changing tools out of the core.
- Fine control over rendering through documented hooks.
- Independent project with no investors.
Limitations
- Planned licensing would require larger organisations to buy a licence key, and the npm package would become proprietary.
- More assembly required than Next.js or Nuxt: you choose extensions, server and integrations.
- Smaller community and fewer tutorials than mainstream meta-frameworks.
Who it suits
Good for
- Teams that want SSR without adopting an opinionated framework
- Apps with an existing backend in another language
- Long-lived applications that value a stable core
Look elsewhere if
- Beginners who want everything decided for them
- Larger organisations that need a permissive npm licence without a fee (once pricing starts)
Alternatives to Vike
Questions
Is Vike free?
Yes for now: its pricing page says the Open Source Pricing is not implemented and everyone can use Vike free. Small teams and small organisations would stay free when it starts.
Is Vike the same as vite-plugin-ssr?
Yes. Vike is the continuation of vite-plugin-ssr under a new name.
Which UI frameworks does Vike support?
React, Vue, Solid, Angular and others through extensions such as vike-react and vike-vue.
Sources read for this page