Backend inside Nitro
Embedded mode: Feathers runs in the same runtime as Nuxt 4 (Nitro).
Two modes: embedded Feathers backend inside Nuxt (Nitro) OR a remote Feathers client. Zod-first generation, Pinia client, Swagger (legacy), and optional Keycloak SSO.

bunx nuxt-feathers-zod init embedded --force
bun devbunx nuxt-feathers-zod init remote --url https://api.example --force
bun devRemote mode
In remote mode, NFZ behaves as a Feathers client (REST or Socket.IO). It does not scan local services and does not require an embedded users/authentication service.
feathers.servicesDirs = ['services'].bunx nuxt-feathers-zod add service ....bunx nuxt-feathers-zod init remote --url http://... (Socket.IO by default, REST via --transport rest).feathers.templates.dirs is optional (only needed if you want to override client templates).The module supports Feathers v5 (Dove) auth in both modes:
strategy: 'jwt') via @feathersjs/authenticationstrategy: 'local') via @feathersjs/authentication-localstrategy: 'oauth') via @feathersjs/authentication-oauthIn remote mode, the module does not require local schemas (services/**) to boot. entityImport is optional.
In embedded mode, the REST server (Express) can enable a “secure defaults” preset:
json + urlencoded body parsingexport default defineNuxtConfig({
feathers: {
server: {
secureDefaults: true,
secure: {
cors: true,
helmet: true,
compression: true,
serveStatic: { path: '/', dir: 'public' } // or false
}
}
}
})