Trust is not a feature. It is the foundation.

Secure

Data access is controlled at every step. Data is encrypted in transit and at rest, and isolated per customer, from a private space on shared infrastructure up to a fully sealed installation.

Governed

Policies and approvals are built in. Automations act within rules you define. Anything that needs a human decision is routed to the right human, every time.

Auditable

Every question, model call, automation and action is logged. You can always trace what happened, who approved it and why. Nothing is a black box.

Permission aware

VOKT respects the access rules of every connected system. An answer never contains something the person asking is not allowed to see. Permissions travel with the data.

Model agnostic

GPT, Claude, Gemini, Kimi, Mistral, open source and private models all sit behind the same governance and the same permissions. You choose what runs, and where.

Deploy your way

Shared cloud, dedicated server, your own hardware or fully sealed. Your security posture decides where VOKT runs, not the other way round.

Single sign on

VOKT plugs into your identity provider. People sign in with the company login they already have.

Revoked in one place

When someone leaves, you close their account where you always do. Their access to VOKT ends at the same moment, because VOKT never had an access list of its own to forget about.

Roles, defined once

Roles and permissions are defined once and enforced everywhere: in search, in answers, in dashboards and in automations. At the manufacturer in our deep dives, every employee's assistant is scoped by their role.

Source permissions respected

If a person cannot open a document in the source system, VOKT will not show them its contents either. Permission aware retrieval is enforced at query time, not by a policy promise.

Read only by default

The assistant looks, it does not touch. In the deep dives, all 21 tools the chat can use are read only. Changes to your systems happen through automations you define, not through a chat window.

Filter first, then search

VOKT does not search everything and hide what you may not see afterwards. It searches only inside what you may see. Records outside your role are never loaded, so they cannot appear in an answer, a summary or a follow up question.

Every answer carries its sources

An answer in VOKT shows where it came from: which system, which document, which record. If a claim cannot be traced to a source, it should not be trusted, and VOKT makes that visible.

Facts checked against documents

Where a mistake would be expensive, VOKT checks facts in the answer against the source text. At one manufacturer, every project number read from 259 supplier confirmations was checked against the document. Zero were invented.

Same question, different person, different answer

Ask where the company is losing margin as a project leader and you see your own projects. Ask as finance and you see the whole picture. Ask from the warehouse and VOKT tells you that your role does not have access. That is not a bug. That is the point.

Norwegian company, European by default

VOKT is built and operated by VOKT AI AS in Norway, with GDPR built into how we work. Vokt Sandbox runs in the EU. Vokt Private runs in your choice of EU or US region, so your data lives under the jurisdiction you answer to.

No hyperscaler dependency

VOKT does not run your data through American hyperscaler platforms. For Vokt Premise this is the entire point: your data never leaves your building.

Isolated per customer

Every customer has its own space. On Vokt Private there is no shared tenancy at all. On Premise and Sealed, the only tenant is you.

Encrypted

Data is encrypted in transit and at rest. The technical details are part of the security documentation, available on request.

Leave with everything

Your data is exportable at any time. If you leave, everything you connected and everything you built goes with you, and your data is deleted from our infrastructure.

Never used to train models

Not ours. Not anyone's. Not for training, not for resale, not for benchmarking, not for anything. Your data works for your business and nothing else. This holds on every tier, from Sandbox to Sealed.

The right model for the job

VOKT picks the right model for each task and puts every one of them behind the same permissions and the same audit trail. Changing models does not change your security.

EU hosted by default

EU hosted models are the default. Every priced tier includes an open model, Qwen3.5 397B A17B, and other models are available where your policy allows them.

You decide whose AI runs

With European and local open source models available, you can decide that no data ever reaches a model provider outside the EU, or outside your building. On Vokt Sealed, only local models run.

Models receive the minimum

A model receives only the records needed for the answer, and only records the person asking may see. It is a tool that reads and writes, not a place where your data is kept.

Rules you own

Automations act within rules you define. At the manufacturer in our deep dives, the team owns the rule package for cutting list checks. A new standard is a file dropped into a folder, with no developer and no release.

Safe fixes, flagged exceptions

Only changes that are known to be safe are applied automatically. Everything else is flagged for a person, per control. Across 28 real before and after pairs, there were zero false positives on automatic fixes.

Approvals are decisions

Decisions belong to people. Automations route them to the right person, record who decided and when, and carry the context the decision was based on.

Locked where it matters

Fields that come from a system of record can be locked, so the next sync or a well meaning colleague cannot overwrite them. Ordered quantities always mirror the ERP.

What is logged

Every question, answer, model call, automation, approval and change. In the deep dives, the production overview also notifies people when someone hides their project, and keeps a full audit log of who changed what.

What every entry holds

• What happened. The question, the answer, the automation or the action.
• Who did it. Tied to an identity, on every entry.
• What it was based on. Answers carry their sources. Decisions carry their context.
• Who approved it. Approvals are recorded with the person and the moment.

An entry, in plain words

Illustrative example.

GDPR

A data processing agreement is part of every subscription. You choose where data lives. Export and deletion are available on request. Your data is processed for your business and nothing else, on every tier.

EU AI Act

The Act asks companies deploying AI for governance, human oversight, transparency and documentation. That is not a checklist VOKT bolted on. It is how VOKT works: every action governed, approvals routed to people, every answer sourced, every step logged. When your auditor asks how you control your AI, you show them the audit trail.

NIS2 and supply chain

If your company falls under NIS2, the security of your suppliers becomes your concern. VOKT gives your assessment what it needs: a clear deployment choice, documentation on request, a subprocessor list, and the option to keep everything inside your own walls.