# Portkey and Prisma AIRS AI Gateway: functions and product boundaries

Evaluate Portkey and Prisma AIRS AI Gateway through product naming, deployment edition, routing policies, telemetry and operating responsibilities.

Author: Retrivium team
Updated: 2026-11-01
Canonical URL: https://retrivium.ai/journal/portkey-ai-gateway-guide/
Language: en

Portkey is known as a layer for model access, routing and observability. On November 1, 2026, the checked documentation was titled Portkey (Prisma AIRS AI Gateway) and pages indicated the new designation. We preserve both names to connect the search term with the current source.

A naming change does not establish acquisition terms or universal migration of every installation. Check the precise product, version and deployment mode for the working project.

## Define the gateway role

The [AI Gateway description](https://portkey.ai/docs/product/ai-gateway) lists a common API, fallbacks and conditional routing. Applications can use common rules across targets while execution remains at an external provider or separately configured infrastructure.

Show application, gateway and model execution as distinct blocks, exposing responsibility for access, policies and resources. A route to an owned endpoint does not mean the product creates demand for it.

## Identify the deployment edition

The project has an [official gateway repository](https://github.com/Portkey-AI/gateway) and deployment documentation. Compare the particular open version, managed service and enterprise offering separately; features, operating responsibilities and terms can differ.

Record data-plane location, component-update ownership and remaining external dependencies. Self-hosting does not necessarily remove external calls: models and integrations may still live elsewhere.

## Test policies on a real scenario

Suppose one team uses a low-cost model for drafts while another requires an approved executor for documents. Write both requirements before configuring rules. Test rejection of a forbidden route as well as successful execution.

Test fallback and caching separately. A changed model requires answer-quality checks; caching requires correct keys and lifetimes. Savings should not come from returning an unsuitable result.

## Connect telemetry to team tasks

Observability helps explain specific events: executor selection, attempt count and cost components. Define minimum telemetry separately from request-content logging. A public dashboard example does not replace checking your environment.

Test ordinary work, provider unavailability, exceeded limits and unsupported parameters. Compare observed and expected behavior to evaluate the product against actual requirements. For procurement, preserve the exact edition name and documentation link so budgeting does not assume features of another version or placement mode.

## Meaning for GPU owners

We treat Portkey/Prisma AIRS AI Gateway as an infrastructure layer, not a confirmed channel that automatically accepts rented GPUs.

Read [OpenRouter versus Portkey](/journal/openrouter-vs-portkey/) and [self-hosted AI gateways](/journal/top-self-hosted-ai-gateways/) when choosing an architecture.