SaaS Solutions
We offer a range of ready-made SaaS solutions built around the Integria integration platform. Among them is a portfolio of six products aimed at academic institutions such as universities, university colleges and vocational schools. Everything is developed, hosted and operated by us, and data is entered once and used across the estate.
Contact usCoherence rather than systems
Identity is the layer everything else rests on
When a person is created, changes role or leaves, the consequence has to propagate to every system at once. Where it cannot, shadow accounting appears: accounts that live on, permissions nobody decided, data in several versions. Our products are therefore built on shared identity and organisational data with a single source of truth.
Integration architecture is a discipline. Mapping and validation must happen in one place, errors must be caught before they spread, and every data field needs an owner. We built Integria as the layer where that work is concentrated, because the alternative is each system solving it separately, differently, and without documentation.
The value of a coherent landscape grows with every connection: each new source, supplier and recipient makes the others worth more. That is network logic applied to administration. Five years of operating for educational institutions has taught us where the gain actually sits: in the work no longer done by hand.
Where the field is moving
Identity has become the first priority
Most breaches today do not begin with a hole in a firewall but with a valid account: a phished password, an access never revoked, a permission nobody decided. The identity layer has become both the most important attack surface and the most important defence.
Automatic provisioning and de-provisioning is therefore not a convenience but a security control. When an employee leaves, the consequence must reach every system the same day, not when somebody remembers. When a role changes, permissions must follow, in both directions.
Our products are built on that logic: people, roles and relationships have one source, and everything else derives from it. That removes the manual work, and it removes the forgotten accounts the auditors otherwise find every year.
Data portability has become a right
The EU Data Act has shifted a basic condition: the right to switch provider and take your data with you is now law, and exit fees are being phased out. What used to be a bargaining chip for the vendor is becoming an obligation.
That should change how software is bought. The requirement is no longer only what the system can do, but how you leave it: in what format data can be exported, what comes along, and whether anyone has actually tried. An exit that has never been tested is an assumption.
We build our products as if the customer could leave tomorrow. Data sits in documented formats, the integrations are described, and nothing is deliberately made hard to move. Dependency as a business model is an expiring strategy, and we never cared for it.
Integrations are moving from wires to contracts
When every system talks directly to every other, the number of connections grows with the square of the number of systems, and fragility grows with it. A field change in one place breaks something three systems away, and nobody can say why before the day is gone.
The countermeasure is to treat data flows as contracts: every field has an owner, a definition and an agreed meaning, and changes are announced as what they are, changes to an agreement. Mapping and validation are concentrated in one place, so errors are caught before they spread.
That is the architecture Integria is built on. It is less spectacular than a diagram with lightning bolts between systems, but it can be operated, debugged and extended. Boring architecture is a compliment.
The platform and the six products
Integria is the foundation, and on top of it sits a portfolio of six products for academic institutions. All of them share identity and organisational data, single sign-on via Entra ID, full logging and operations in Denmark. What separates them is the task.
Everything above talks to your systems through Integria rather than to each other. That is the whole architecture, and it is the reason a system can be replaced underneath without the other six noticing.
The hub every other system talks through.
Integria sits between your administrative systems, your identity platform and everything downstream, so nothing has to be wired directly to anything else. It handles API, event and batch integrations in the same place, with transformation, mapping and validation applied before data ever reaches the receiving system. Failures are logged, retried automatically where that is safe, and re-run by hand where it is not.
In production it does the unglamorous work continuously: creating, changing and closing user accounts, assigning groups and licences, building classes and relationships, and keeping records in step across systems that were never designed to agree with each other. Because the integrations are abstracted into one layer, a system can be replaced underneath without touching the others, which is what makes the rest of this portfolio practical to run.
Applications in at one end, provisioned people out at the other.
Admitra runs the admissions process end to end: intake, automated validation of the submitted data, case handling, decision, and then creation of the applicant as a real user in the systems that need to know about them. The steps that used to be a spreadsheet and a series of reminders become a tracked process with an audit trail.
Because it is connected through Integria, an accepted applicant becomes an account, a group membership and a class enrolment without anyone re-typing anything. Administrators keep the judgement calls and lose the data entry.
The whole credential lifecycle, from data to issued document.
Credentia manages credentials from the underlying data and template design through generation, issuing and subsequent handling. Templates are governed centrally, so a change to a layout or a wording is made once rather than in a folder of near-identical documents.
The data comes from the systems of record through Integria rather than from a manual export, which is what makes issuing at volume safe. Reissues, corrections and historical lookups are part of the product rather than an administrative favour.
Studia handles the requests that otherwise end up in an inbox: documentation requests, address changes, leave, status enquiries. Students see the same record the institution holds, submit with the same login as the rest of the platform and can follow the status of their case. The administration gets a structured queue with deadlines and ownership instead of a mailbox.
Identia manages student and staff cards as one product rather than two systems kept in agreement: photo collection with an approval flow, a digital card on the phone, a physical card where required, immediate blocking on loss, and integration with access control and print. The card's lifecycle follows the employment or enrolment automatically, through the same identity data as the rest of the platform.
Intraia targets announcements and information by role, class or department, with audiences that maintain themselves because they are built on organisational data rather than hand-tended lists. Important messages can require acknowledgement, documents are shared with version control, and nobody maintains a distribution list that was already stale when it was created.
Employa runs onboarding and offboarding as governed flows: contract and documents, equipment and access, introduction tasks and reminders to the people responsible. Because it shares its identity layer with the rest of the platform, access follows the employment automatically, in both directions. Leaving on the last day of the month means accounts closed on the last day of the month.
Four steps, from starting point to operations
Nobody was hired to type the same thing into three systems. The systems should talk to each other so the people do not have to.
Niels Reinau
Niels founded iCEO after a career spent at IBM, at eBay, and running platforms at DanDomain and Zitcom, two of the largest hosting companies in Denmark. Zitcom is today team.blue Denmark, and DanDomain is one of the brands it still trades under. He works alongside consultants who have been in this industry for twenty-five years. You get that experience directly, not a partner at the pitch and a graduate on the work.