For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Choose where Telmai runs relative to your data

Telmai offers three deployment models. All three deliver the same product — profiling, monitors, incidents, and integrations — and differ only in where Telmai's services run and where your data is read.

Model
Where Telmai services run
Does raw data leave your environment?
What you operate

Telmai Cloud (SaaS)

Telmai's cloud

Yes — Telmai reads your sources

Nothing

Control plane in Telmai's cloud, data plane in your environment

No

One agent host, your own Spark engine, and cloud storage

Entirely in your cloud

No

The full Telmai stack, deployed with Helm and Terraform

Which model fits

Telmai Cloud (SaaS) is the default. Telmai hosts everything and connects to your data sources over the network. Nothing is deployed in your environment.

Hybrid keeps data processing in your environment while Telmai continues to host the application. You run a single lightweight agent, scans execute on your own Spark engine, and scan output lands in your own cloud storage, so no row-level data crosses the boundary. This is the smallest footprint that keeps data in place — there is no Telmai service tier, database, message broker, or search cluster to operate.

VPC runs every Telmai service inside your own cloud account, including the application tier and its datastores. Choose this when policy requires that Telmai's application and metadata also stay within your environment.

To discuss which model fits your requirements, or to begin a Hybrid or VPC deployment, contact your Telmai account manager.

Last updated