A complete local AI stack.

Lokalaise delivers the complete software stack to run local AI in your company — from connectors to integration with your tools. If needed, we supply the managed hardware as well, as part of the service.

100% locally operatedGDPR-compliantproductive in 14 days

01The architecture

Five layers, one managed stack.

From connecting your sources to integrating with your tools — each layer builds on the one below. Select a layer to see its role.

1.1

Connector Layer

Reads your source systems — incrementally, true to the source, with no data migration.

Delta sync instead of full exports: connectors continuously read your systems and carry over documents, metadata, and and access rights (ACLs) true to the source. Nothing is copied to a cloud, and no system needs to be migrated.

SharePointSMBExchangeConfluenceERP/DMS

1.2

Knowledge Layer

Makes data AI-ready — indexed, permissioned, versioned.

A hybrid index of full text and embeddings: every fragment carries its source, permissions, and and version. Retrieval is permission-aware — whoever asks sees only what they would be allowed to see in the source system.

IndexingEmbeddingsPermissionsVersioning

1.3

Agent Layer

Automates processes — controlled, logged, measured.

Agents take over recurring processes — first in shadow mode alongside your people, then in production. Every step lands in the audit trail, and nightly evals measure quality against real cases.

Shadow modeAudit trailNightly evals

1.4

User Layer

Where your teams work — chat, search, and and frontends.

The interface to all permissioned knowledge: chat and search in natural language. Every answer carries citations — one click leads to the exact passage in the original document, including its version.

ChatSearchCitations

1.5

Integration Layer

Brings answers into your existing tools — instead of adding another one.

Answers and workflows land where the work happens: in Outlook, in Teams, and and via API in your business applications. The platform becomes part of your tools — not yet another window.

OutlookTeamsAPI

The entire stack is operated by Lokalaise — including managed on-site hardware, if you wish.

02From data to answer

Governed knowledge, not generic RAG.

Every document passes through the same controlled path — and every answer carries its source, permissions, and and version.

  1. 2.1

    Source systems

    SharePoint

    SMB · Exchange

    ERP/DMS

    Your data, where it lives

  2. 2.2

    Connector Layer

    Delta sync

    ACLs carried over

    Metadata true to source

    reads, doesn't copy

  3. 2.3

    Knowledge Layer

    Index + embeddings

    Permissions per fragment

    Version state

    makes it AI-ready

  4. 2.4

    User Layer

    Chat & search

    Citations per statement

    One click to the source

    answers with evidence

one path · no cloud · permissions end to end

Grounded answer

The verified structural analysis for component B-204 was released in revision 3 — valid fire-protection class F90, confirmed by the test report dated 12 March.

Source: Structural_analysis_B-204.pdf, p. 7Permission: Construction project teamVersion: Rev. 3 (current)

No free guessing — every statement is tied to a specific, permissioned document and can be verified.

03The layers in detail

What each layer actually delivers.

Connector, Knowledge, Agent, User and Integration work together — from connecting your sources all the way into your everyday tools.

3.5Integration Layer
3.4User Layer
3.3Agent Layer
3.2Knowledge Layer
3.1Connector Layer

Hardware — on-site · managed on request

3.5

Integration Layer

Answers and workflows land in the tools your teams already use — Outlook, Teams, and and via API in your business applications.

  • No extra window — the platform becomes part of your tools
  • Open API for custom integrations
3.4

User Layer

Chat, search, and and frontends across all permissioned knowledge — every answer carries citations, and one click leads to the exact passage in the original.

  • Natural language instead of search syntax
  • Citations with source, page, and and version
3.3

Agent Layer

Agents take over recurring processes — first in shadow mode alongside your people, then in production and fully logged.

  • Audit trail for every step
  • Nightly evals measure quality against real cases
3.2

Knowledge Layer

A hybrid index of full text and embeddings — every fragment stays tied to its source, permissions, and and version.

  • Permission-aware retrieval on every query
  • Versioning instead of outdated copies
3.1

Connector Layer

Reads source systems incrementally — delta sync instead of full exports, with access rights and metadata carried over true to the source.

  • SharePoint, SMB, Exchange, Confluence, ERP/DMS
  • No data migration, no cloud copy

04Grounded, not claimed

The difference between evidence and assertion.

Same question, two answers: generic AI asserts from training data — without a source. Lokalaise answers from your documents — with source, version, and and permissions.

Question

When does supplier contract LF-118 expire?

Generic AI

Assertion without a source

Supplier contracts typically run for one to three years — so the contract should expire around the end of 2026; exact terms vary.

No sourceNo versionNo permissions
  • Answer guessed from statistical model knowledge
  • No source, no permissions, no version state
  • No audit path — not traceable
  • Sounds convincing, even when it's wrong

Lokalaise

Source · Version · Permission

The approved contract LF-118 runs until 31 December 2027 and includes fixed pricing for the first 24 months (§ 12).

Source: Contract_LF-118.pdf, § 12Version: final (Rev. 2)Permission: Purchasing
  • Answer tied to a specific, permissioned document
  • Source, version, and and permissions travel with the answer
  • Complete audit path for every statement
  • Says clearly when the sources aren't sufficient

05Value over time

Software wears out. Knowledge compounds.

Every tool you buy is most valuable on day one. Lokalaise is most valuable on the last: the knowledge layer learns every night from usage and feedback — and every workflow becomes a building block for the next.

  1. 01Usage during the day
  2. 02Feedback & benchmarks
  3. 03Optimization overnight

— and more precise answers in the morning.

5.1

Learns every night

Usage, feedback, and and benchmarks flow back overnight — hit rates, ranking, and and answer precision improve automatically.

5.2

Workflows as building blocks

Every knowledge workflow you set up becomes a reusable building block. The next use case starts faster and at lower cost.

5.3

A knowledge layer that grows

New documents, projects, and and sources continuously extend the knowledge layer — the platform becomes more valuable with your work.

06A turnkey solution

Turnkey — productive in 14 days.

You're not buying an AI project, you're buying a result: stack, operations and, if you wish, the hardware come from a single provider. The first workflow runs on real data after 14 days.

14 days

to the first live workflow

100%

locally operated

no cloud, no external APIs

0

in-house AI team required

fully managed by Lokalaise

6.1 · Days 1–3

Connect

The infrastructure is set up on-site and your sources are connected via the Connector Layer — no cloud, no data export.

6.2 · Days 4–10

Build the knowledge layer

Your data is indexed, permissioned, and and versioned. In parallel, the first workflow takes shape — on your real data, not demo material.

6.3 · Day 14

Live in production

The first workflow goes live — with grounded answers and measurable value on a real use case.

6.4 · After that

Roll out

From there, the platform scales across additional teams, sources, and and departments — step by step, with evidence at every stage.

Ready for grounded AI

From raw data to a grounded answer — on your own infrastructure.

Let's set up a first workflow on your real data — managed, local, and and productive in 14 days.

One-time onboarding · Platform incl. hardware · Managed workflows