Business software from a model – as real, extensible code.
CodamAI is the software factory of Codamic AG. You describe your data as a model, and CodamAI generates a complete Spring Boot application from it: REST API, validation, database, tenant separation, permission checks and history. Your business logic is added through hooks, without touching the generated code.
- 01HubModelmodels, fields, relations · permissions per model and field
- 02BuildGeneratorgenerates the code on every build · entity, DTO, API, persistence
- 03CDMSApplicationREST API and hooks · history and files
- 04CIASAccesstoken, tenant, roles · sign-in through Keycloak
- 05DatabaseDatasystem and tenant data kept apart · every change as a revision
Build faster without giving in on quality and security
Model first
The data model is the single source. Entities, DTOs, payloads, endpoints and validation are generated from it – no hand-written boilerplate.
Real software, not a construction kit
The result is a regular Spring Boot application. Your own logic lives in hooks, services and controllers. No low-code, no closed platform.
Multi-tenant from day one
In multi-tenant mode every tenant gets its own database. Where the tenant of a request comes from and what it may see is handled by the system – not by each endpoint on its own.
Secure by default
Sign-in through Keycloak, roles per model and operation, field permissions and row filters. What you may not see does not exist for you.
Traceable
Every change is stored as a revision: who, when, what. You read an object’s history and roll it back to an earlier state when needed.
Run it where you want
The result is a Spring Boot JAR or a native image. It runs in the cloud, in a private cloud or in your own data centre.
One core, several modules
Each module has one clearly bounded job and a fixed colour you will find on every page.
The data layer: from the model to a REST API with search, writes across relations, tenants, history, files and hooks.
Identity and access: users, tenants, roles, groups, registration and invitations. Keycloak handles the sign-in itself.
Reports from templates: data and template become HTML and PDF, with preview and charts.
Frontend components, UI structures and generators for the user interfaces of a CodamAI application.
App and mobile development on the same foundation, with Vue/Nuxt and Cordova.
Processes, workflows, tasks and states on top of an application’s data.
How CodamAI works
The documentation explains the processes in CDMS and CIAS: what happens, in which order, who is involved and which variants exist. First pick a module, then a subject area, then a topic. The legend explains how to read the diagrams.
The data layer of CodamAI. A model becomes a REST API that reads, searches, writes and deletes data. It checks every request for permissions and tenant, and it logs every change.
The bridge between a CodamAI application and the identity provider (Keycloak). CIAS knows who a person is, which tenant they belong to, which roles exist, and who may grant them. Keycloak handles the sign-in itself.
How CDMS and CIAS work together, as a single unit in one process or as separate services. With flows walked through from login to the database. A good starting point for newcomers.
Markers: done · draft · planned.
Frequently asked questions
- Is CodamAI a low-code or no-code tool?
- Where does my own business logic go?
- How does CodamAI keep the data of different customers apart?
- Where can a CodamAI application run?