About consiness solutions
The product is new, the experience is not.
Nova IAM is an enterprise IGA platform for your entire IT landscape. It is built by consiness solutions GmbH, with a team spanning IAM, development and security.
- Vendorconsiness solutions GmbH, based in Hebertshausen, Germany.
- TeamIAM, development and security, with consiness as implementation partner.
- MaturityPre-1.0, with a public changelog and a public roadmap.
Who we are
consiness solutions GmbH builds Nova IAM
Nova IAM manages people and technical identities, their accounts in connected target systems and the entitlements they hold there. Connected systems include SAP, Active Directory and Entra ID. Nova manages AI agents as identities of their own, with owner, review and expiry.
Company details
| Company | consiness solutions GmbH |
|---|---|
| Legal form | Limited liability company (GmbH) under German law |
| Address | Bgm.-Herzog-Str. 8, 85241 Hebertshausen, Germany |
| Managing director | Hendrik Winkler |
Why Nova exists
A clear trigger and years of practice
The trigger
Mainstream maintenance for SAP Identity Management 8.0 ends on 31 Dec 2027. After that, SAP offers extended maintenance until 2030.
The experience
Nova grows out of years of hands-on practice with SAP Identity Management. The product itself is new, and the current version is pre-1.0.
The platform
Nova is not limited to SAP. It is built for your entire IT landscape: 14 standard integrations, including 6 target-system connectors.
Team
The people behind Nova IAM
We build Nova as a team spanning IAM, development and security. consiness GmbH & Co. KG is our implementation partner.
Hendrik Winkler
Founder, IAM architect
Amir Ameri
Co-founder, CISO
Florian Damss
IDM specialist
Fabian Haydecker
Full-stack developer
Thomas Winkler
UI/UX specialist
Laurent Baese
AI specialist
Marvin Hindmarsh
Security specialist
Maja Michaelis
Marketing & communications
Evelyn Huth
Finance & legal
consiness GmbH & Co. KG
Implementation partner
Hendrik Winkler
Founder, IAM architect
Hendrik Winkler co-founded Nova IAM and is managing director of consiness solutions GmbH.
He has published on SAP Identity Management, among other places in IT-Onlinemagazin: “SAP IDM Wartungsende: Herausforderungen, Alternativen und Ablösung” (in German), 26 April 2024.
Timeline
What has shipped since August 2026
A selection from the public changelog, with month and release.
- August 2026v0.9.4
AI agents as a first-class identity type
An owner and a purpose are mandatory when an agent is created. Agents taken over through the Keycloak or Entra import start without an owner and a purpose, and the healthcheck reports missing owners. Requests, recertification and the handover when the owner leaves are part of it.
- August 2026v0.9.5
New user interface
The entire user interface was rebuilt on Vue 3 with TypeScript, in German and English, with light and dark mode.
- August 20262026.08.2
Healthcheck per identity
19 checks, 11 of them with a suggested fix. The AI assessment can be switched on per run, and the healthcheck also works without it.
- October 20262026.10.1
Migration Workbench, admin chat, change journal
Imports from the legacy system’s export file, such as SAP IDM, have been expanded and can be reverted in Nova. The admin chat runs destructive actions only after a preview and a confirmation. The change journal now covers all connectors.
- October 20262026.10.2
Nova on BTP on the Cloud Foundry runtime
Nova runs on SAP BTP on the Cloud Foundry runtime. No dedicated Kubernetes cluster is needed. Nova reaches SAP systems in the customer network through the SAP Cloud Connector, currently read-only: status check and user lookup. Provisioning in SAP requires the self-hosted edition.
- November 20262026.11.1
SAP SuccessFactors as HR source and target system
Joiners, movers, leavers and rehires come from SuccessFactors. As a target system, Nova writes memberships in static permission groups.
- November 20262026.11.2
Risk engine
Segregation of duties and critical actions across all target systems, checked on new requests and continuously in the risk register, with simulation and mitigating controls. You maintain the rule set yourself.
Maturity
How we handle maturity
Nova is a young product. That is why we show openly what is finished, what has been postponed and what is still outstanding.
Enterprise describes the functional scope: lifecycle, roles, access requests, segregation of duties and recertification. The product is still before version 1.0; the external pentest and the ISO certificate are outstanding. Current status
Public changelog
Releases are listed with their version and month on the status page, including fixes and security changes.
Roadmap with postponements
Anything from the quarter just ended that was not finished stays visible and is marked as postponed.
Trust Center
Policies, audit log documentation and the GDPR, NIS-2 and CRA mappings are public and can be read without an NDA.
Source code escrow
With the maintenance contract, we deposit the source code with an independent escrow agent. The contract governs its release.
What is still outstanding
| Item | Details | Status |
|---|---|---|
| Version | Not yet at version 1.0, in active development. | Pre-1.0 |
| External penetration test | Still outstanding. We will announce the date once it is contractually fixed. | Date to follow |
| ISO/IEC 27001 | No certificate. We will announce the date of the certification audit once a certification body has been engaged. | No date yet |
| SOC 2 Type 1 | No SOC 2 report. Planned after ISO 27001, no fixed date. | After ISO 27001 |
The field test
A 90-day PoC with your own team
The PoC shows whether Nova fits your organization.
How the PoC works
- Parallel operationNova runs for 90 days alongside your existing tool.
- With your teamYour own approvers, owners and admins do the testing.
- DecisionAfterwards, your team decides whether Nova works in day-to-day use.