Skip to content

Requirements & installation

Hardware

Teleutias is delivered and configured on a dedicated workstation, sized according to the number of users and the expected workloads.

Reference configuration:

Component Indicative specification
GPU NVIDIA with 16 GB of VRAM (e.g. RTX 5060 Ti 16 GB)
RAM 32 GB or more
Storage NVMe SSD, 1 TB recommended (models + knowledge base + logs)
Operating system Windows or Linux, according to the client's IT preferences

Why a dedicated GPU

Local language models require a GPU to respond within timescales that suit daily work. CPU-only inference is technically possible but too slow for operational use: the GPU is not an option, it is the central requirement.

The machine can be supplied by Teleutias fully configured, or installed on the client's existing hardware if compatible.

Network

  • The interface is reachable from the company's local network via browser: nothing needs to be installed on users' PCs.
  • No exposure to the public internet is required. The machine accepts no inbound connections from outside.
  • For remote support and maintenance, an encrypted point-to-point remote access channel (mesh VPN, e.g. Tailscale) can be enabled, in agreement with the client, with limited permissions revocable at any time.
  • An internet connection is only needed during installation and for scheduled updates; day-to-day operation is entirely offline.

Commissioning procedure

  1. Initial analysis — gathering use cases, reference documents and the client's IT constraints.
  2. Machine preparation — installation of the inference engine, web interface and selected models; load testing.
  3. Assistant configuration — instructions, operational limits and knowledge base for each activated vertical.
  4. Connection to the client's network — LAN integration, user and permission setup.
  5. Kick-off session — user training on the assistant's capabilities and limits.
  6. Verification period — initial support with real but selected use cases, and configuration tuning.

Updates and maintenance

  • Updates (models, software components, configurations) are scheduled and agreed with the client: no uncontrolled automatic changes.
  • Every new model is verified before going into production, against the client's use cases.
  • The client may request the status of installed components and versions in use at any time.