Enterprise deployment

Your environment. Your approved AI sources.

PromptLeash analyses agreed AI activity within your organisation's approved environment. Your teams control deployment, updates and the scope of the evidence used.

Book a demo
How it fits together

Approved activity in. Evidence your teams can review out.

Step 1

Approved sources

The provider, chat, application and agent logs you agree to include.

Step 2

Local analysis

Classification models and your role and workflow context, running in your environment.

Step 3

Evidence for review

Role and workflow views your teams use in business reviews and improvement decisions.

Analysis runs separately from live model requests. It reads the activity you have approved rather than sitting in the path of a request your people or agents are making.

01 / Scope

Start with the sources you approve.

Agree which provider, chat, application and agent logs will be used, and which roles and workflows the analysis should cover.

  • Nothing is analysed until it is in the agreed scope.
  • Coverage reflects the sources connected in your deployment, not every interaction in the organisation.
02 / Processing

Run analysis locally.

Classification models and customer context operate in your environment, separately from live model requests.

  • Interaction content is analysed within the approved scope to understand the work being performed.
  • Analysis runs alongside your AI stack rather than in the path of a live request.
03 / Access

Give the right people access.

Use SSO and role-based access within the agreed deployment configuration.

  • Executive, manager and individual views show what that audience should see.
  • Access follows the roles agreed during deployment.
04 / Planning

Plan deployment around your organisation.

Work through source availability, technical requirements, access and business review needs with your team.

  • Scoping covers which sources exist, who owns them and what is practical to connect.
  • Specific hosting environments, connectors, retention and support arrangements are confirmed against current product documentation during scoping.
Confirmed during scoping

What we will not state until it is verified.

Supported hosting environments, the connector list, retention periods and support arrangements depend on your deployment and are confirmed from current product documentation during scoping rather than promised here.

This page describes the product's deployment model. Our privacy notice covers website visitors and is not the product's data-processing specification.

Plan deployment around your organisation.

Work through source availability, technical requirements, access and business review needs with your team.

Book a demo