Skip to content
Lokalaise
Demo

Security & operations

AI at your company.
Responsibilities clearly defined.

Your AI runs on hardware in your office – encrypted, with roles and permissions, and logged.

  • Runs in your office

    Models and processing on the Lokalaise hardware at your company.

  • Roles and permissions

    Every account has roles, defined during setup.

  • Encrypted and logged

    Data encrypted with AES-256, access logged.

Your AI runs in your office.

Language models and processing run on the Lokalaise server at your company; your content goes to no external model provider for this. You connect online sources such as SharePoint deliberately – they keep the connection to their service.

Permissions reach into the answer.

Connecting a repository does not grant access to everyone: before every answer, Lokalaise checks what the asking account may access. Where the source provides permissions, they continue to apply.

We manage operations. You stay informed.

Technical operations and content approvals have clear owners. The details are documented in the operating concept.

Lokalaise

  • Set up the platform and agreed connections
  • Updates and technical support within the agreed scope
  • Coordinate operational requirements with your IT team

Your company

  • Approve sources and access
  • Appoint subject-matter and technical owners
  • Review and approve work results

Agreed together

  • Administrative permissions and operational access
  • Diagnostic data and update procedures
  • Access from outside, such as from home

Operational access is agreed, logged and traceable for you.

Your IT team’s questions. Answered clearly.

Clear answers for your IT team.

AI processing takes place on local hardware at your company. Connected online sources, such as SharePoint, require a connection to the respective service.

Administrative permissions, operational access and procedures are defined in the operating concept. Lokalaise accesses the system for operations and updates within the agreed scope; who may do so, for what purpose and how it is logged is set out there.

You define accounts and permissions during setup. We review the existing permissions of your sources for each connection. For a public support chat, you approve a separate knowledge base.

Local operation supports your control over the processing location and makes GDPR compliance easier. Technical and organisational measures and the required agreements are part of the rollout. ISO 27001 certification is in preparation.

Backups, logs and response times are part of the operating agreement: we define scope, ownership and retention for your environment. The same applies to encryption details and SSO.

Let’s discuss your requirements.

Together with your IT team, we clarify sources, access rights and operational responsibilities.