Frameworks

The fifteen frameworks revenexx Storefronts builds out of the box, which rendering adapters each supports, and how detection works.

revenexx Storefronts hosts and serves web apps built with a range of frameworks. "Supported" means the platform knows the framework's conventions — it can detect it, pick sensible install and build commands, find the build output, and choose the right rendering adapter with little or no configuration from you.

Zero-configuration approach

When you deploy, the platform:

Detects your framework from your dependencies and config files.
Applies that framework's default install command, build command, and output directory.
Determines the rendering adapter — ssr or static — from what your build actually produced.

Step 3 is worth dwelling on. If you don't set an adapter, it is detected from the build output and then remembered on the site. If you do set one, it is checked against the output: declaring ssr on a build that produced a purely static bundle fails the build rather than deploying something that won't run. That is deliberate — a silent downgrade to static is much harder to debug later than a failed build now.

Supported frameworks

Fifteen frameworks, with the identifier you pass to the API and CLI:

Framework	Identifier	Adapters
Analog	`analog`	`ssr` `static`
Angular	`angular`	`ssr` `static`
Next.js	`nextjs`	`ssr` `static`
Nuxt	`nuxt`	`ssr` `static`
SvelteKit	`sveltekit`	`ssr` `static`
Astro	`astro`	`ssr` `static`
TanStack Start	`tanstack-start`	`ssr` `static`
Remix	`remix`	`ssr` `static`
React	`react`	`static`
Vue	`vue`	`static`
Lynx	`lynx`	`static`
Flutter	`flutter`	`static`
React Native	`react-native`	`static`
Vite	`vite`	`static`
Other	`other`	`static`

The eight frameworks at the top support both adapters, because each has a first-class server build as well as a static one. The rest are static-only: they produce a bundle of files, and the platform serves those files.

The list the platform will actually accept is available over the API, which is the right thing to read if you're generating configuration:

Shell

curl -s https://api.revenexx.com/v1/sites/frameworks \
  -H 'X-Revenexx-Tenant: <tenant-slug>' \
  -H 'X-Revenexx-Api-Key: <api-key>'

Choosing an adapter

ssr runs your server build per request — the right choice for a commerce storefront, where prices, stock, and the buyer's session are per-request facts. See SSR.
static serves pre-built files with no server execution. Ideal for documentation, marketing sites, and single-page apps. See Static.

A revenexx theme is a Nuxt 4 app deployed with the ssr adapter, since a storefront needs server-rendered catalog pages and its own server routes for the BFF layer.

Frameworks that aren't listed

Anything that produces a static bundle can be deployed. Pick the other framework identifier and set the install command, build command, and output directory yourself. The platform still detects the adapter from what your build produces — it simply doesn't presume to know your conventions.

The default install and build commands per framework are listed under Develop.

Was this page helpful?