> ## Documentation Index
> Fetch the complete documentation index at: https://venator-06aff335.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Who Uses Venator

Venator is designed for environments where secure service execution, financial governance, and operational control must operate together. It supports multiple stakeholders across organizational levels, each interacting with the platform differently.

***

## **1. Primary Users**

### Operations & Platform Management Teams

Operations teams use Venator to manage service configuration, monitor execution activity, and maintain structured control over service consumption.

For them, the priority is visibility and control. Venator helps centralize routing, standardize execution flows, and provide clear monitoring of transactions and system activity. The result is governed service usage with measurable operational oversight.

***

## **2. Secondary Users**

### IT & Integration Teams

IT and integration teams oversee secure connectivity, authentication enforcement, and system scalability.

They use Venator to integrate backend systems through secure APIs, enforce centralized validation rules, and manage vendor orchestration without direct exposure. For these teams, reliability, security, and standardized execution logic are essential.

***

## **3. Indirect Users**

### Client Organizations & Service Consumers

Client organizations interact with Venator when consuming external services through structured and governed channels.

They benefit from controlled execution, predictable pricing, standardized responses, and transparent transaction tracking. While they may not see the orchestration and wallet governance layers directly, they experience secure and consistent service delivery.