FAQ

Common questions when generating and integrating — languages, databases, regeneration, and secondary development.

Common questions about integrating generated code into your existing system. For install, login, and run issues, see each doc’s “FAQ” section at the bottom.

Pricing & credits

Is Zero-CRUD free? The basics are free: sign up and you get bonus credits, which are enough to generate normal projects. To unlock Pro advanced features, a single top-up at any tier works — it takes effect permanently. There are no subscriptions and nothing expires. You buy credit packs by tier ($5/$10/$30/$100); credits are spent on generation and iteration, with bonus credits consumed first. That revenue lets us keep iterating and serving better — if Zero-CRUD is valuable to you, a top-up is welcome. See the pricing page for what you get.

Languages & databases

Which backend languages are supported? Go, Python (FastAPI), TypeScript (Express), Java (Spring Boot) — pick one at generation time.

What frontends are supported? Vue (Element Plus) and React. Backend and frontend can be combined freely.

Which databases are supported? MySQL, PostgreSQL, SQLite, MariaDB. init.sql is generated for the dialect you select; PostgreSQL and others create tables sorted by inter-table dependency, so foreign-key relationships succeed in a single pass.

Does every DDL work? No, a few table shapes are restricted. Tables without a primary key and composite primary keys are clearly flagged at parse time and won’t generate CRUD as expected; some types that make poor primary keys (e.g. booleans) also get a warning. Beyond that, most common schemas work fine — just watch the parse messages.

Generation & regeneration

Do I need to regenerate after changing config? Yes. Generation parameters, advanced settings, and permission config only land in the actual code after you regenerate.

Want to switch language stacks? Change the backend/frontend language in project settings, then regenerate.

Can multiple tables be generated at once? Yes. Import several tables and generate once — each table gets its endpoints and pages, with inter-table foreign keys preserved.

Secondary development

Can I modify the generated code? Yes. The generated project is a complete runnable project — add business logic directly in its directories (list pages, form pages, pagination, and filtering are ready; extend on top).

Can I add my own business endpoints? Yes. In each backend, add routes/controllers under the matching directory; on the frontend, add pages and request wrappers under src/views and src/api.

Will my changes be overwritten on regeneration? Regeneration rebuilds the project from the current schema and config; it does not auto-merge your edits inside the generated directory. For changes you want to keep, merge them yourself with your version-control tool (e.g. git merge or a diff tool). Putting generated code under git first is recommended.

Permissions & login integration

Are the generated permissions and login wired up by default? Yes. The chain “login state → role → permission check” is connected out of the box.

How do I plug in my company’s existing login? See Login Integration: swap the login hook to map the current user; permissions only depend on “the current user’s role”, independent of the login method.

How do I change permission rules? Edit permissions.json in the generated code — config takes effect immediately, no business-code changes. See Permission Integration for the structure.