We kept running into the same problem. So we built the layer that was missing.
We spent years deploying AI agents for enterprises, and the same governance gaps showed up on every project, for every client. TapPass is the authority layer we needed ourselves.
- Company
- Cogniqor BV
- Headquarters
- Antwerp, Belgium
- Hosting
- EU region
- Backed by
- Start it @KBC · VLAIO
- Founders
- Jens Bontinck · Jonathan Berte
- Focus
- The authority layer for agentic AI
Not proofs of concept. Production, in regulated industries.
What if the agent reads data it should not? How do we prove to the auditor what it did? What if it runs away and burns the budget overnight?
We built and deployed automation agents, data pipelines and customer-facing assistants for enterprises, in banking, insurance and professional services. The same questions came back every single time.
They were not hypothetical. An agent looped for hours because nobody had set a budget limit. A customer service bot surfaced internal pricing data. An operations agent ran for six months before anyone in security knew it existed.
So we kept building the same guardrails from scratch: custom logging, manual budget checks, ad hoc access controls. It worked, but it did not scale, and it would not have survived an audit.
- 01VisibilitySecurity did not know how many agents were running, or what data they touched.
- 02IdentityShared API keys. You could not tell agents apart, scope their permissions, or revoke one without breaking the rest.
- 03EnforcementPolicies on paper, with nothing at run time to enforce what agents were allowed to do.
- 04Audit trailLogs caught prompts but missed tool calls, data flows and the chain of decisions.
- 05ProportionalityBlock everything, or allow everything. No way to size governance to each agent.
We set out to stop rebuilding guardrails. Every enterprise needed the same thing.
TapPass began as a proxy between our own agents and the model providers. Every request checked against our rules, every action on the record.
Controls that enforce, not guidelines that suggest.
Governance that fits each agent, from watching to a person on every payment.
A tamper-evident record, not a developer’s recollection.
More agents with confidence, not fewer agents out of fear.
We are not building TapPass because AI is dangerous. We are building it because AI is valuable, and that value is at risk without governance.
The answer is not to avoid the technology. It is to govern it well enough that the CISO can say yes.
Every CISO who blocks AI because the risk cannot be measured is making a rational decision. The cost of standing still is real too.
We want to take an active part in AI innovation, in a governed way. That is not a contradiction. It is the whole point.
Built in Belgium, on European infrastructure. A choice, not an accident.
European companies run AI under GDPR, DORA, NIS2 and the EU AI Act at the same time. Governance that holds up here holds up everywhere.
The people behind TapPass. Innovation and governance, together.

Engineer turned founder. Formerly in the Office of the CTO at ML6, where he spent years building and deploying AI systems for enterprises in banking, insurance and professional services. He saw teams ship agents quickly, then scramble when security, compliance or legal asked what those agents were doing. He leads product, engineering and architecture.
LinkedIn
More than a decade where AI meets enterprise strategy. As CEO of Robovision he scaled an AI vision platform across manufacturing, logistics and retail. He knows what it takes to sell AI into regulated environments, and how governance becomes the enabler of adoption. He drives strategy, partnerships and go to market.
LinkedIn

Six commitments that shape the product.
Agents are eager. TapPass makes eager safe. Where the idea came from, and where the category is going.
Read the story Press and brand kitLogos, screenshots, boilerplate and quick facts.
Open the kit Trust CenterSecurity posture, data handling, subprocessors and legal documents.
Visit the Trust CenterGovern your agents well enough that your CISO can say yes.
Connect one agent and see every call TapPass would have held, stopped or routed elsewhere. Nothing is blocked while you learn.