Telha design partner programme is now open. Learn more →

Deployment

Deploy where your
evidence already lives.

Telha is designed to run inside the customer environment, connect to approved business systems and keep investigation data under customer control.

Reference architecture · self-hostedPrivate environment
Your environment · data never leaves
Your systems
Microsoft 365
Slack
ServiceNow
Records & logs
Approved uploads
Self-hosted Telha
Telha core
Evidence and investigation layer
Versioned evidenceMandates & casesProvenance
Open-weight AI
Deployed alongside Telha on your infrastructure
Case-scoped analysisNo external APIs
Authorised team · SSO
Legal
Compliance
Internal audit
Security
Appointed reviewers
Outside the boundary No evidence to vendor cloud No external AI API calls

Two places to run it. One boundary rule.

Evidence, prompts and AI output stay inside an environment you own, whichever option you choose.

Option 01 · Your cloud tenancyMost common

In your cloud subscription.

Telha and its AI models deploy into an Azure, AWS or Google Cloud subscription you own. Your existing cloud agreement, regions and audit controls apply unchanged.

  • Data boundaryYour subscription & region
  • Runs onAzure · AWS · Google Cloud
  • Time to stand upDays, not months
  • AI computeReserved, or rented per second
Option 02 · Your data centre

On your own hardware.

For restricted networks and strict residency mandates, Telha runs on a single GPU server on your premises. The model sits beside the evidence. Nothing needs to leave the building.

  • Data boundaryYour premises
  • HardwareOne workstation-class GPU server
  • Network postureSuits limited-egress environments
  • Model updatesPinned versions, your schedule

AI capacity, in plain terms.

Three capacity profiles cover most investigation teams. Same models, same features: they differ only in responsiveness and how much runs in parallel.

On-demandAI compute starts when a case needs it, shuts down after. StandingMost teamsOne dedicated AI instance, ready throughout the working day. High-throughputDedicated capacity for parallel casework and archive-wide analysis.
Best for Periodic investigations, a few cases a quarter A standing team with weekly casework Multiple teams or heavy consolidation workloads
First response after idle Under ~2 minutes while compute spins up Immediate Immediate
Parallel workload One analysis at a time A small team working concurrently Concurrent teams, plus scheduled archive-wide jobs
AI hardware held None, billed per second of use One 24 GB-class GPU One 48 GB-class GPU, or a pair
Indicative compute cost From ≈US$50 / month ≈US$600 to 1,400 / month ≈US$1,400 to 2,700 / month
Available on Cloud tenancy Cloud or data centre Cloud or data centre

Indicative figures at typical mid-2026 cloud GPU rates, billed by your cloud provider at cost. Telha does not resell compute. On-premises hardware is a one-time purchase with no per-token fees. Exact sizing is confirmed during an architecture review.

A simple enterprise deployment model.

Start with a bounded investigation workflow and expand source coverage deliberately.

01
Deploy

Install Telha in the agreed customer-controlled environment.

02
Connect identity

Map enterprise users, roles and investigation approvers.

03
Add sources

Connect the systems required for the initial investigation type.

04
Configure governance

Define mandate, scope, retention and evidence rules.

05
Run a case

Validate the complete workflow with representative evidence.

AI that never leaves the boundary.

Telha deploys an open-weight model inside your environment, so investigators get AI assistance without evidence ever reaching an external service.

01

Open-weight models

Deployed with Telha and sized to your hardware. You can inspect the model, pin its version and upgrade on your own schedule.

02

Case-scoped assistance

Summarise threads, draft chronologies and surface gaps, computed only over the evidence admitted to the case.

03

Nothing sent out

Prompts, embeddings and evidence stay on your infrastructure. No external AI APIs, and no vendor training on your data.

Designed to coexist with your current stack.

Telha does not require an immediate replacement of Microsoft Purview, archives, forensic tools or existing review systems.

01

Use existing holds

Keep Microsoft-native preservation and legal-hold processes where they are already established.

02

Admit existing evidence

Bring approved exports and forensic collections into the same governed case model.

03

Add investigation intelligence

Connect evidence across systems and turn it into chronology, findings and defensible output.

Architecture workshop

Map Telha to your environment.

Review sources, identity, network boundaries, deployment, evidence retention and operational ownership.