Start your project
with one vertical slice.
Each template is a working Storm application at its smallest: two entities, one repository query, one service, two endpoints, and the tests that cover them. It runs on H2 the moment you clone it, and PostgreSQL is a configuration change. Around three hundred lines, so there is nothing to delete before your own code goes in.
//Starter templatesGitHub template repositories. Press Use this template, rename the package, replace the schema, and the project is yours. Working with a coding agent? Run
npx @storm-orm/cli init in the new project and the agent knows Storm too.Starter template · Kotlin + Ktor→
A Ktor application wired by one
install(Storm): the connection pool, the repositories, the Flyway migration and entity validation at startup. Coroutine-native transactions in the service, JSON endpoints, and tests on H2.KotlinKtor 3H2 or PostgreSQL
Starter template · Kotlin + Spring Boot→
The same slice on Spring Boot 4: the starter builds the
ORMTemplate, registers the repositories as beans, bridges Storm's transactions with Spring's, and validates every entity against the live schema at startup.KotlinSpring Boot 4H2 or PostgreSQL
Starter template · Java + Spring Boot→
The Java flavor on Java 21: immutable record entities, a metamodel query that navigates the foreign key, a Spring-managed transaction, and the same two tests. No JPA, no proxies, no persistence context.
Java 21Spring Boot 4H2 or PostgreSQL
//What is insideThe same slice in every template, so the language and the framework are the only difference.
Two entities and a migration→
City and User as immutable records or data classes, with
@PK and @FK, and the Flyway migration they map to. Storm checks the two against each other at startup, so a mismatch fails the application rather than the first request.A repository, a service, two endpoints→
One query that navigates the foreign key without naming a join, a service that reads in a read-only transaction and writes two rows in one, and the endpoints that expose them.
Tests that come with it→
A repository test on H2 through
@StormTest, asserting the statements with SqlCapture, and a schema validation test that checks every entity against the migration. Both run without Docker.//Looking for a complete application?The templates are where a project begins. The examples are where Storm is shown at scale.