Deployment  ·  Cloud, hybrid or your own

Your data. Your perimeter.

The product is the same in all three models. The same Assistants, the same portal, the same mobile apps. What changes is where the platform runs and who operates it.

Where your data has to live should be a configuration, not a reason you cannot use the platform.

Good afternoon, Peter

Tellexa workspace · Monday 1 Jun

Active

3/3

Credits

3.2k

Tasks

14

Autos

6

Assistants

3 online · 3 total

Tasks

5 open · 9 done

Automations

6 active

Voice Agents

1 agent · 240m

Team

8 members

Billing

Auto-topup on

Recent activity

  • Google Workspace connected 2m
  • Anna completed onboarding flow 15m
  • 3 approvals awaiting review 1h

Three models

Pick the one your policy allows.

The choice is usually driven by data residency obligations, internal security policy and how much of the operational burden you want to carry. You are not locked in. Plenty of customers start on the cloud to prove the value and move later, and the configuration, Assistants and knowledge move with them.

Tellexa Cloud

Fully managed. The platform runs in our infrastructure, we operate it and you use it. Nothing to install, nothing to maintain and you are working the same day. Updates, patching, monitoring, backup and capacity are ours to worry about.

This suits most organisations, particularly anyone without a dedicated platform team or anyone who wants to prove the value before making an infrastructure decision.

Fastest We operate it
Regulated

Hybrid

The control plane stays with us while the components that touch your sensitive data run inside your environment. You keep the managed portal, the managed updates and our support. The Assistant runtime and the connections to your internal systems sit on your side of the boundary.

This is the usual answer when an Assistant has to reach a system that is not exposed to the internet, or when policy says certain data never leaves your network. It is the most common choice for regulated and enterprise customers.

Internal systems Data locality

On premise

The entire platform inside your environment, whether that is your own data centre or your own cloud tenancy. You hold the infrastructure, the data and the operational control. We license the platform and support it.

This can run with no dependency on any external AI service, using a closed model hosted inside your environment. It is the right answer for defence, government, financial services and anyone with a hard sovereignty requirement.

Closed model Sovereignty

Constant across all three

What does not change.

  • Your data stays isolated

    Assistants belonging to one organisation cannot search, read or retrieve another organisation's conversations, documents, knowledge or memory.

  • Your content is not used for training

    We do not train models on your content and we do not pool customer data to improve the product for anyone else.

  • Credentials are encrypted and never shown back

    You authorise a connection through the provider's own sign in. We never ask for a password, and a connection can be revoked from the portal at any time.

  • The governance layer is identical

    Permissions, approvals, role based access and the audit log work the same way whether the platform runs in our environment or yours.

Overview

Workspace · production

2 min ago

Policy check

Passed

Risk score

18

Low risk

Pending approvals

+3 new
  • Data access policy 2m
  • External tool: Xero 15m
  • Customer escalation 1h

How it runs

A hybrid or full deployment is a project.

Not a signup form. It is scoped, planned and handed over properly, and that is also where the quote comes from.

01

Technical discovery

We size the environment, agree the integration surface and establish what your policy actually requires.

02

Scope and quote

You get a written scope and a figure that reflects it, rather than a rate card that was never built for your situation.

03

Deploy

We deploy alongside your team. Backup and continuity are designed to fit your existing standards rather than sitting outside them.

04

Handover and support

Operational handover to whoever runs it day to day, with ongoing support against your agreement.

If you have restrictions on third party processing, raise them early. The answer often points at hybrid or a full deployment rather than a contractual amendment.

Get started

Tell us what your
policy requires.

Bring the constraint, not the workaround. Most of what sounds like a blocker turns out to be a deployment model we already support.