Skip to content

Pro / Studio roadmap

Community must remain the stable foundation. Commercial features should be added by extension, without polluting the Community package.

Open-core principle

txt
Community = stable public base
Pro = advanced commercial extensions
Studio = NFZ-specific integration
Enterprise = support, SSO, offline licensing, SLA

Why separate Pro code?

Frontend JavaScript cannot be protected only with a simple if (license) condition. A better model is to distribute Pro code through a separate package and keep high-value server actions behind protected APIs.

Priority Pro features

txt
advanced theme builder
advanced AND/OR conditions
Zod and JSON Schema import
template library
visual history panel
custom fields and panels
AI-assisted form generation

Future integration

ts
export default defineNuxtConfig({
  extends: [
    '@vevedh/qform-builder-layer',
    '@vevedh/qform-builder-pro-layer',
  ],
})

NFZ differentiator

The strongest differentiator is not only drag-and-drop. It is the integration with Nuxt 4, Quasar, Feathers, Zod and NFZ Studio:

txt
NFZ service → schema → builder → viewer → CRUD page generation

QForm Builder — reusable Nuxt 4 / Quasar / FormKit layer.