Security is the product

No external APIs. No data leaves.

Most AI sends your data to third-party servers for processing. Vokt runs entirely inside your infrastructure. That's not a feature. That's the architecture.

Two worlds of AI

AI is splitting in two. Which side are you on?

With the EU AI Act, the choice between open and private AI is no longer optional. It's a compliance decision.

Open cloud AI

  • Data sent to external APIs for processing
  • Model provider sees your queries and documents
  • No control over where data is stored or processed
  • Vendor lock-in to US cloud infrastructure
  • Compliance burden falls on you to prove safety
  • Third-party outage = your AI is down

Private AI (Vokt)

  • All processing happens inside your environment
  • No external API calls — your data stays with you
  • You choose where it runs: your servers, EU cloud, or fully offline
  • No vendor lock-in — runs on standard hardware
  • Compliance is built in, not added after the fact
  • Works without internet — even air-gapped environments

Five layers between a question and an answer.

Every query passes through five checks before you see an answer. This isn't a policy document. It's how the system is built.

1

Questions are screened before processing

Manipulation attempts, out-of-scope requests, and malformed inputs are blocked automatically — before any data is accessed.

2

Only your documents, nothing else

The system can only access files and databases you have explicitly connected. No outside data, no cross-contamination between teams or projects.

3

Every answer shows where it came from

No answer is returned without a source. Every claim traces back to a specific passage in a specific document. You can check it yourself.

4

It says "I don't know" instead of guessing

When confidence is low, the system tells you. Fabricated numbers and invented facts are caught and flagged — not presented as truth.

5

Everything is logged and reviewable

Every question asked, every answer given, every source cited. Full traceability for compliance audits, internal reviews, and governance reporting.

How data moves

Your data never leaves. Not even once.

The entire pipeline — ingestion, processing, querying, and response generation — runs inside your perimeter.

┌─────────────────┐      ┌──────────────────┐      ┌─────────────────────┐
Your Documents    ───▶    Vokt Engine       ───▶    Verified Answer
└─────────────────┘      └──────────────────┘      └─────────────────────┘

Never leaves              Runs on your                Cites sources
your server               infrastructure              you can check

Built for the EU AI Act. Not retrofitted.

The EU AI Act requires transparency, traceability, and human oversight for AI systems. Vokt meets these requirements because of how it's built — not because of a policy document.

GDPR compliant EU AI Act ready Schrems II safe Full audit trail Data residency: EU

Transparency, risk classification, documentation — these aren't afterthoughts. They're default behaviour.

Deploy your way

On-premise. Private cloud. Air-gapped.

On-premise

Your hardware, your network, your rules. Runs on standard servers — no specialised equipment needed. No internet connection required.

Private EU cloud

Dedicated instances on European infrastructure. You choose the provider and the country. Your data never crosses an ocean.

Air-gapped

For environments with no internet access. Defence, critical infrastructure, classified operations. Fully functional offline.

Your data. Your infrastructure. Your rules.

Most AI tools are a liability. Vokt isn't. No external APIs. No data exposure. Full control.

Get a Demo