The platform in detail
AI Development with an engineering backbone.
CodamAI connects modern AI coding workflows with explicit backend models, permissions, validation rules, traceable configuration and controlled delivery.
A modular platform
Six modules. One foundation.
CodamAI is not a monolithic suite. You combine the modules your project actually needs – each with a clearly delimited job and its own identifier that reappears in the Hub, in licensing and in the pricing model.
Modules and pricing-
CDMS
Data Management
Data models, persistence, APIs, versioning and multi-tenancy.
Standard -
CIAS
Identity & Access
Identities, roles, permissions, organisations and authentication.
Standard -
CRMS
Reporting
Structured reports, templates and export to HTML, PDF and XML.
Add-on -
CADS
App Development
App and mobile development based on Vue/Nuxt and Cordova.
Add-on -
CFDS
Frontend Development
Frontend components, UI structures and generators.
Add-on -
CPMS
Process Management
Processes, workflows, tasks and states.
Add-on
Standard means CDMS and CIAS form the foundation and are part of every package. Add-on marks the modules you add depending on package and project.
CDMS · Data Management
The backend stays a structure, not a text file.
CDMS is the data and backend foundation of the platform. Data models, fields, relations, validation rules and metadata are modelled explicitly – and from that come persistence, APIs and standard logic based on Java and Spring Boot.
When the domain structure stays explicit, a person can review it – and an AI can change it deliberately instead of guessing it anew.
- Models & relations
- Entities, fields, relationships and metadata as a modelled structure instead of scattered code.
- Validation rules
- Domain rules sit on the model and apply to every access path – not only where a form happens to check them.
- Standardised APIs
- Every model gets interfaces with consistent semantics – same structure, same rules, same permissions across all models.
- Multi-tenancy
- Multi-tenancy is part of the foundation, not a filter retrofitted later.
- Versioning & history
- Data states and changes stay traceable – the basis for evidence later on.
- Files
- File management as a platform capability, tied into the same permissions and data models.
Extensible, not locked in. The generated code is a regular Spring Boot application. You can extend it per project, test it and run it with your own tooling.
CIAS · Identity & Access
Who may do what – and why.
CIAS keeps identities, roles and permissions together in one place. That makes authorisation a reviewable model rather than a collection of conditions spread across controllers and frontends.
A permission model you cannot read out completely is worthless in an audit – no matter how correctly it is implemented.
- Users & groups
- Identities and group memberships as first-class, manageable objects.
- Roles & permissions
- Permissions are assigned to roles and apply consistently across the platform capabilities.
- Organisational context
- Organisations and tenants are part of the access model, not merely a field on the record.
- Authentication
- Sign-in and session context as a platform function, shared by all modules.
Connecting existing IAM systems is possible depending on the project. Which methods are supported in your setup is something we clarify in the technical fit conversation – we deliberately do not publish a blanket compatibility list here.
CRMS · Reporting
Reports from the data, not from manual work.
CRMS produces structured analyses directly from the platform models. Templates are reusable, results reproducible – and the same data basis is available for evidence.
A report nobody can reproduce is a snapshot. A report generated from the model is evidence.
- Structured reports
- Analyses come from the data models instead of manually assembled exports.
- Reusable templates
- Report templates are defined once and used across projects.
- Export
- Output to HTML, PDF and XML – suitable for further processing as well as for archiving.
- Shared permissions
- Reporting uses the same permission model as the rest of the data access.
Add-on modules
Modules beyond the foundation.
These three modules extend the platform with application, interface and process capabilities. Which of them your project really needs is something we clarify in the technical conversation – instead of selling you the full scope by default.
CADS
App Development
App and mobile development based on Vue/Nuxt and Cordova.
CFDS
Frontend Development
Frontend components, UI structures and generators for the interface layer.
CPMS
Process Management
Domain process logic, states, tasks and approvals.
Across all modules
What holds the modules together.
Five capabilities belong to no single module but to the platform itself. They decide whether AI-assisted development stays controllable.
AI & MCP Integration
CodamAI can be plugged into agentic development workflows through an MCP server. The AI tool then works against defined platform capabilities instead of producing arbitrary code. Which model or environment you use remains your decision – Claude Code or Codex, for example.
Human review explicitly remains part of the flow. MCP shortens the path to a definition; it does not replace the decision on whether that definition is right.
MCP in professional workflowsCodamAI Hub
In the Hub, people see what the AI defined: models, relations, permissions and configuration become visually comprehensible and can be corrected deliberately – before anything is built.
The Hub is not a no-code builder. It is the control layer over a definition that stays valid without it.
Traceability & evidence
Histories, changes and the link between configuration, build and release stay technically traceable. That supports teams with elevated demands on quality, auditability and documentation.
To be clear: CodamAI provides technical prerequisites for validation-oriented development. It replaces neither your quality management system nor your SOPs, your risk assessment or your validation planning.
Regulated development with AICI/CD & Container Delivery
Delivery runs in your pipeline: load the project definition, build the backend application, create the container image, run the quality gates, deploy.
- Load the project definition
- Build the application
- Create the container image
- Run the quality gates
- Deploy
Your pipeline. Your infrastructure.
Whether your own GitLab, Jenkins, on-premise, private cloud or Kubernetes – the target environment stays under your control.
OpenAPI & Swagger
The API documentation of the generated application closes the loop back to the frontend. It describes precisely what the backend can do – and becomes reliable integration context that AI coding tools can consume as well.
That reduces manual coordination between frontend and backend to what genuinely needs a domain decision.
Does CodamAI fit your engineering setup?
The most honest way to find out is a technical conversation: about your stack, your delivery and the requirements you have to evidence.