Add SpringBoot Generator to Code Generators

[tipikae]

Adds SpringBoot Generator to Code Generators.

Disclosure: I am the author of this tool.

Why it qualifies (criterion d — a niche product filling a gap): it generates the backend and the optional frontend as two separately deployable projects, and it generates n-ary association entities (join entities carrying three or more foreign
keys) directly from the visual schema.

Distinction from similar entries already listed:

• Bootify — broader than this tool in several areas (more databases, Kotlin, Spring Security, Flyway/Liquibase, modularization). Two concrete differences: Bootify embeds the generated Angular app inside the Spring application as a single artifact, whereas this tool emits backend and frontend as independent projects; and n-ary association entities are generated here rather than modelled by hand.
• JHipster — a CLI/Yeoman generator requiring a local Node toolchain and a JDL file. This tool is browser-based with no installation and no CLI.

Developer-friendliness requirements:

• Commercial, marked ![c]. Pricing is public at https://www.springboot-generator.com/pricing
• Free tier: project generation is free and requires no account, and covers MySQL, Java 21, Maven or Gradle, and the complete CRUD REST backend. Paid credits unlock the optional extras (PostgreSQL, Java 17 and 25, generated unit and integration tests, Docker, Swagger, Javadoc, logging, dev/prod profiles, the Angular or React frontend, and n-ary associations beyond two foreign keys).
• Closed source, so there is no license to disclose for source code. The generated projects belong to the user.
• Documentation is in English.

Entry is alphabetically sorted and follows the required format.

---

Summary by cubic

Add SpringBoot Generator to the Code Generators list in README. It’s a browser-based Spring Boot CRUD API generator that outputs a separate backend plus optional Angular/React frontend, and supports n-ary association entities.

^{Written for commit d6e9e90. Summary will update on new commits.}

[cubic-dev-ai]

2 issues found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="README.md">

<violation number="1" location="README.md:334">
P3: Adding this entry makes the Code Generators list contain 19 projects, but the section heading still reads `18 projects`. Bump the count to 19 so the heading stays accurate.</violation>

<violation number="2" location="README.md:334">
P3: The new entry breaks the visual convention used by every other entry in this Code Generators list. Unlike the surrounding items, which use the `<kbd>★ N</kbd> <kbd>License</kbd> <emoji><br>` badge format and a `<br>` before the description, this line uses a plain dash separator and no badges/tags. It's worth confirming whether this list's commercial (`![c]`) entries use a distinct format elsewhere; if not, consider aligning this entry with the `<br>` and badge style so the list reads consistently. Note this is a minor style/consistency concern, not a functional issue.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: Adding this entry makes the Code Generators list contain 19 projects, but the section heading still reads 18 projects. Bump the count to 19 so the heading stays accurate.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 334:

<comment>Adding this entry makes the Code Generators list contain 19 projects, but the section heading still reads `18 projects`. Bump the count to 19 so the heading stays accurate.</comment>

<file context>
@@ -331,6 +331,8 @@ _Tools that generate patterns for repetitive code in order to reduce verbosity a
 
 > **[Spring CRUD Generator](https://github.com/mzivkovicdev/spring-crud-generator)** <kbd>★ 38</kbd> <kbd>Apache-2.0</kbd> 🟢<br>Maven plugin for generating Spring Boot CRUD applications from YAML/JSON specifications.
 
+> **[SpringBoot Generator ![c]](https://www.springboot-generator.com)** - Browser-based generator for Spring Boot CRUD REST APIs from a visual schema, producing the backend and an optional Angular or React frontend as separately deployable projects, with n-ary association entities.
+
 > **[Telosys](https://www.telosys.org/)** <kbd>★ 212</kbd> <kbd>LGPL-3.0</kbd> 🟠<br>Java code-generation toolkit with a CLI and model-driven template engine.
</file context>

[cubic-dev-ai]

P3: The new entry breaks the visual convention used by every other entry in this Code Generators list. Unlike the surrounding items, which use the <kbd>★ N</kbd> <kbd>License</kbd> <emoji><br> badge format and a <br> before the description, this line uses a plain dash separator and no badges/tags. It's worth confirming whether this list's commercial (![c]) entries use a distinct format elsewhere; if not, consider aligning this entry with the <br> and badge style so the list reads consistently. Note this is a minor style/consistency concern, not a functional issue.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 334:

<comment>The new entry breaks the visual convention used by every other entry in this Code Generators list. Unlike the surrounding items, which use the `<kbd>★ N</kbd> <kbd>License</kbd> <emoji><br>` badge format and a `<br>` before the description, this line uses a plain dash separator and no badges/tags. It's worth confirming whether this list's commercial (`![c]`) entries use a distinct format elsewhere; if not, consider aligning this entry with the `<br>` and badge style so the list reads consistently. Note this is a minor style/consistency concern, not a functional issue.</comment>

<file context>
@@ -331,6 +331,8 @@ _Tools that generate patterns for repetitive code in order to reduce verbosity a
 
 > **[Spring CRUD Generator](https://github.com/mzivkovicdev/spring-crud-generator)** <kbd>★ 38</kbd> <kbd>Apache-2.0</kbd> 🟢<br>Maven plugin for generating Spring Boot CRUD applications from YAML/JSON specifications.
 
+> **[SpringBoot Generator ![c]](https://www.springboot-generator.com)** - Browser-based generator for Spring Boot CRUD REST APIs from a visual schema, producing the backend and an optional Angular or React frontend as separately deployable projects, with n-ary association entities.
+
 > **[Telosys](https://www.telosys.org/)** <kbd>★ 212</kbd> <kbd>LGPL-3.0</kbd> 🟠<br>Java code-generation toolkit with a CLI and model-driven template engine.
</file context>

Suggested change

	> **[SpringBoot Generator ![c]](https://www.springboot-generator.com)** - Browser-based generator for Spring Boot CRUD REST APIs from a visual schema, producing the backend and an optional Angular or React frontend as separately deployable projects, with n-ary association entities.
	> **[SpringBoot Generator ![c]](https://www.springboot-generator.com)** <br>Browser-based generator for Spring Boot CRUD REST APIs from a visual schema, producing the backend and an optional Angular or React frontend as separately deployable projects, with n-ary association entities.

[tipikae]

Thanks for the review. I checked both points against the file on main and I don't think either applies — happy to change it if a maintainer sees it differently.

1. Badge format. README.md on main contains no <kbd> and no ★ markup at all (zero occurrences of each). Every entry in Code Generators, including the two neighbouring commercial ones — Bootify ![c] and JPA Buddy ![c] — uses the plain - [NAME](LINK) - DESCRIPTION. form that CONTRIBUTING.md requires. The star and licence
badges shown in the review appear to be added by the review tool's own rendering rather than present in the file. Applying the suggested change would replace the - separator that CONTRIBUTING.md mandates with a <br>.

2. Project count. The section heading is ### Code Generators — there is no project count in it, nor anywhere else in the README, so there is nothing to bump.

The entry is unchanged and follows the required format and alphabetical ordering.