The platform is not new. The clients running on it are not pilots.
Kwerio has been built and refined since 2006 against the operational requirements of clients in regulated and operationally complex sectors. Energy, retail, transport, financial services, public-sector adjacent operations, education, construction, hospitality. Multi-country delivery across Belgium, France, Switzerland, the Nordics, the Baltics, Morocco.
The architecture has been pressure-tested by two decades of production.
The platform is not new. The clients running on it are not pilots. The architecture has been pressure-tested by two decades of production work in environments where uptime, audit trail, and operational integrity are the contract, not the marketing.
Each of the companies above runs its own security and compliance review. Each has been satisfied for years.
An ecosystem since 2006.
Kwerio is the platform. Imageplus is the Brussels-based team that builds, maintains, and operates it. Zentinel is a compliance product built on Kwerio for EU financial services. Three names, one ecosystem, in continuous client production since 2006.
The platform is delivered directly through this ecosystem. Engagements are scoped, configured, integrated, and operated by the same team that maintains the platform. Not handed off to a separate implementation network. The people who answer your platform questions are the people who built the substrate. The people who deliver your engagement are the people who will operate it for you afterwards.
This is not the model larger platform vendors operate. It is a deliberate choice. The benefit is that there is no telephone game between a platform vendor, a certified partner, and an operations contractor. The whole chain is one team. The trade-off is that engagement bandwidth is finite. We say no to engagements where the fit is not right.
Kwerio is the platform you buy. Imageplus is the team that delivers it. Zentinel is the compliance product built on top of it.
Governance is structural, not promised.
Most application platforms govern their data with policy. RBAC is enforced by application code. Audit trails are written by handlers. Approval gates are application logic. When the application is updated, or compromised, or extended by an AI agent, the governance has to be re-verified.
Kwerio's governance is compiled into the database, from the schema. Permissions, segregation of duties, approval gates, and audit trail are not behaviours added by application code. They are properties of the data layer itself. An auditor who reads the schema can determine deterministically what is possible, regardless of what the application says it does.
This matters more in 2026 than it did in 2016. The EU AI Act requires structural human oversight of AI systems acting in regulated contexts. NIS2 requires demonstrable governance, not just documented policy. DORA, for the financial entities it covers, requires verifiable operational resilience. These are not marketing tailwinds. They are procurement requirements.
For Kwerio, they are properties the platform was already built to satisfy, before they were named.
How it works →AI agents inside the same governance.
When an AI agent calls the Kwerio API, it hits the same compiled gates as a human user. It carries an identity. It is bound to a role. Its actions are recorded in the same audit trail. It cannot exceed the permissions of the role it was granted, and it cannot bypass an approval gate that requires human sign-off.
This is a structural property, not a configuration choice. The platform does not have a separate path for AI agents and another for humans. The schema-compiled governance is the only path either of them can take.
Agents can be deployed inside regulated operations without rebuilding the governance layer. The audit trail is consistent across human and machine actors. The segregation of duties is preserved when an agent stands in for a human. The platform's answer to "can your AI agents bypass governance?" is structural. By architecture, not by policy, no.
What we do not have.
Kwerio holds no third-party security certifications today. No SOC 2. No ISO 27001. No TISAX.
This will be relevant to some procurement teams as a hard filter. We are not going to pretend otherwise. Two things are true alongside the absence.
The first is that our architecture is openly documented and our public policies on backup, residency, access control, encryption, multi-tenant isolation, audit trail, and incident response are published and verifiable. We invite procurement and audit teams to read them, ask questions, and assess Kwerio on the architecture rather than on a certification badge.
The second is that the security and compliance teams at the companies running Kwerio in production today have done their own assessments. At scale, in regulated sectors, repeatedly, for years. The credibility we lead with is theirs, not certificates we do not yet hold.
If your procurement process requires a specific certification as a precondition, tell us. We will be honest about whether Kwerio is the right fit for the timing of your decision.
For procurement and security →What is not on the Kwerio site.
Two clarifications worth being explicit about, because the boundaries matter.
Compliance products are sold separately. Zentinel, the compliance evidence product in the ecosystem, handles deep DORA, CSRD, ISO 27001 mapping, cross-framework audit reporting, and regulatory evidence orchestration for EU financial services. If that is what you are shopping for, Zentinel is the conversation, not Kwerio.
Implementation services are sold separately. If you are looking for digital transformation consultancy, custom development, or operational integration, that work is delivered by Imageplus, the implementation team in the ecosystem. Imageplus.be is the engagement. Kwerio is the platform.
The clearer the boundary, the more useful each conversation.
Talk to us