App Lifecycle
The lifecycle of an App in Tyk AI Studio follows several distinct stages, from creation to deactivation. As an administrator, you play a key role in this process, particularly in the review and activation stages.1. Creation
An AI Developer creates an App, defining its name, description, and selecting the necessary resources such as LLMs, Tools, and Data Sources. At this stage, the App’s credentials are created but are inactive.2. Review
Once an App is created, it appears in the Apps list in the Admin section. As an administrator, you should review the App’s configuration to ensure it complies with your organization’s policies. This includes checking the selected LLMs, Data Sources, and Tools for appropriateness and security.3. Activation / Rejection
After reviewing the App, you can either activate or reject it.- Activation: By toggling the “Active” switch for the App’s credentials, you approve the App. It can now be used to make authenticated requests to the AI Gateway.
- Rejection: If the App does not meet your organization’s standards, you can leave its credentials inactive. It’s recommended to communicate with the user who created the App to explain why it was not approved.
4. Monitoring
Once an App is active, you should monitor its usage and performance. The App Details view provides insights into token usage, costs, and detailed request/response logs. This allows you to track resource consumption and identify any unusual activity.5. Deactivation
If an App is no longer needed, is misbehaving, or violates policies, you can deactivate it at any time by toggling its credentials to “Inactive”. This immediately revokes its access to the AI Gateway.Managing Apps
The Apps View in the AI Studio dashboard is your central hub for managing all user-created applications.Viewing App Details
From the Apps list, you can click on any App to see its detailed view. This view provides a comprehensive overview of the App, including:- App Information: Name, description, owner, and associated LLMs, Data Sources, and Tools.
- Credential Information: The App’s Key ID and its active status.
- Token Usage and Cost: A graph displaying token consumption and associated costs over time.
- Proxy Logs: Detailed logs of inbound and outbound requests, essential for troubleshooting and auditing.
Editing Apps and Approving Credentials
In the App Edit View, you can:- Modify the App’s name and description.
- Change the associated LLMs, Data Sources, and Tools.
- Approve or reject the App by toggling the Active switch for its credentials. This is a critical governance control.
Privacy Level Validation
The system enforces data governance by validating the privacy levels of resources. When a user creates or an admin updates an App, the privacy levels of the selected Data Sources cannot be higher than the privacy levels of the selected LLMs. Privacy levels are categorized from low to high:- Public
- Internal
- Confidential
- Restricted (PII)