What is the difference between a certification portal and an LMS?
An LMS handles learning content, progress and, optionally, an exam. A certification portal handles formal issuance: registration, identity verification, payment, assessment by independent reviewers, issuance with legal status (eIDAS QES), a public register, renewals and a revocation flow. The two can complement each other; for training institutes we often build a combination.
Are you replacing an existing certification package or audit management system?
For a small certification, usually not. We come into the picture when your scheme, integrations or publication requirements are so specific that an off-the-shelf package only works with expensive customisation. During the intake, we set your current licence and customisation costs against a custom build. Some clients keep their audit management system in-house and only have us build the customer and register portal.
How do you technically ensure the independence of assessors?
Conflict-of-interest detection runs automatically on employer, previous relationship and region, and blocks assignment as soon as a match is found. Reviewers work blind: they cannot see each other's scores before submitting their own assessment. If their assessments differ, the application is escalated automatically. Every assessment is traceable in the audit trail.
Which eIDAS providers do you integrate with?
Signhost (Evidos), ValidSign, KENA, Adobe Sign, DocuSign and, for specific domains, domain-specific QTSPs. For QES, we work with QTSPs that have a valid status on the EU Trusted List. Which provider fits depends on the scheme, the cost per issuance and your contractual situation; we advise on this.
How well is the public register protected against misuse or scraping?
We build in rate limiting, CAPTCHA for abnormal patterns, and a structured API for parties that need large volumes (with API keys, a contract and logging). Bulk export goes through a formal connection, not through scraping. For sensitive schemes, we can restrict search to an exact match on certificate number.
How do you handle the right to be forgotten for revoked certificates?
A revocation leaves the certificate visible with the status 'revoked' and the date, which is precisely the purpose of publication. Personal data of an applicant who was never certified is destroyed after the retention period. For revoked certificates, a retention obligation often applies on your side; we build this trade-off as an explicit workflow with a final check by your data protection officer.
Do you work with our current IT partner or our internal IT team?
More often than not, yes. We deliver the codebase, build instructions, architecture overview and runbook so that an external maintenance provider can take over, a deliberate design choice to avoid vendor lock-in. Some clients keep us on under a maintenance contract; others hand maintenance to their own team.
Can a certification portal run on-premises, or does it have to be in the cloud?
Both are possible. For government or accreditation-sensitive environments, we run the stack in a Dutch single-tenant private cloud or your own data centre. For other contexts, we use an EU-based cloud in consultation with you. In both scenarios, the encryption keys stay with you.
What if we want to add an extra scheme along the way?
That is why we build the scheme engine as data, not as code. A scheme administrator can set up a new scheme or a new version themselves via an editorial interface. For schemes with entirely new technical requirements, we do a short further-development sprint.
What determines the cost?
The biggest cost drivers are the number of schemes, the complexity of the assessment process, the depth of the integrations (payment, accounting, external registers, accreditation reporting), the requirements around eIDAS QES and publication, and the migration of existing certificates. We work with fixed sprint budgets so you can adjust the scope sprint by sprint.