Verdictan vs. Red Hat Connectivity Link
Both products can govern AI API traffic, but Connectivity Link extends the boundary to cluster ingress, APIs, DNS, and multicluster networking.
Connectivity Link is Kubernetes-native
It configures Gateway API data planes in supported OpenShift clusters with custom resources for traffic, identity, limits, DNS, and TLS.
TokenRateLimitPolicy reads OpenAI-style usage
The policy extracts usage.total_tokens, selects limits by identity or group, and rejects later requests after a limit is reached.
The MCP gateway is Technology Preview
Red Hat says the feature lacks production SLA support, might be incomplete, and is not recommended for production.
Documentation differences
10 of 12 rows have different documentation labels. Matching labels do not establish equivalent behavior. Read each product's scope and sources.
| Feature | Verdictan | Red Hat Connectivity Link |
|---|---|---|
| Customer-managed gateway data plane | Limited: Connected gateway The gateway runs on a customer computer, container or server. The Console and API run in the Verdictan organization region; the gateway requires a control-plane connection. | Documented It is a control plane for Gateway API data planes in supported OpenShift Container Platform clusters. Sources: [7] |
| Model API exposure | Documented The customer runs the gateway, which connects to the Verdictan control plane for configuration and authenticated requests. Supported request families have different policy coverage. | Limited: Chat Completions Red Hat demonstrates OpenAI-compatible /v1/chat/completions endpoints for private or external models. Sources: [11] |
| Declarative configuration | Limited: Documented boundary Versioned gateway configurations declare provider targets, routing and policy. Configuration files are not a no-code agent builder or model-version registry. | Documented Teams apply Gateway, HTTPRoute, AuthPolicy, RateLimitPolicy, TokenRateLimitPolicy, DNSPolicy, and TLS policy resources. |
| Route-level identity policy | Limited: Documented boundary Applications use scoped Verdictan API tokens, distinct from gateway tokens and upstream provider credentials. Bindings can restrict gateway, team, user, provider, model and spend access. Sources: [19] | Documented AuthPolicy supports API keys, JWT or OIDC identity, groups, defaults, and route-level overrides. |
| Token rate limits | Limited: Distinct limit paths The local token limiter counts buffered Chat Completions only and excludes streams and other families. Connected-request model access rules separately apply per-token RPM and TPM limits at the control plane. | Limited: Tokens only TokenRateLimitPolicy counts OpenAI-style usage by user or group and enforces time-window limits, not monetary budgets. |
| Multicluster routing | Not documented in the cited sources The reviewed Verdictan sources document provider routing, but not multicluster gateway routing. | Documented Connectivity Link supports weighted traffic, global DNS, health checks, failover, and multicluster gateway management. |
| Runtime content guardrails | Documented An active policy chain applies configured controls to supported gateway traffic. Available actions and input, output and streaming coverage depend on the individual control and request family. | Not documented in the cited sources The listed Connectivity Link 1.3 core guides cover access and traffic policies. They do not establish built-in prompt-injection, response-content or PII inspection. Confirm any guardrail integration separately. |
| MCP gateway | Limited: Separate MCP surfaces A published agent hostname exposes Verdictan tools over streamable HTTP MCP. A separate, host-enabled MCP provider bridge calls external MCP backends with configurable tool checks; this is not an enterprise server catalog. | Limited: Technology Preview Version 1.3 aggregates MCP servers, but Red Hat labels the gateway Technology Preview and not production-ready. |
| MCP tool filtering | Limited: Separate MCP surfaces A published agent hostname exposes Verdictan tools over streamable HTTP MCP. A separate, host-enabled MCP provider bridge calls external MCP backends with configurable tool checks; this is not an enterprise server catalog. | Limited: Technology Preview Preview virtual servers combine curated tool lists with identity-based discovery filters. Tool calls still need authorization. Sources: [14] |
| Kubernetes policy acceptance checks | Limited: Documented boundary Local policy tests compare configured verdicts, reason codes and supported output assertions with supplied cases. They do not establish provider access or complete live gateway behavior. Sources: [28] | Limited: Acceptance checks Kubernetes status conditions and documented request checks confirm policy acceptance and enforcement. Verify broader regression testing. |
Show all 12 features
| Feature | Verdictan | Red Hat Connectivity Link |
|---|---|---|
| Scope and deployment | ||
| LLM gateway traffic management | Documented The customer runs the gateway, which connects to the Verdictan control plane for configuration and authenticated requests. Supported request families have different policy coverage. | Documented Connectivity Link combines AI gateway, API management, multicluster connectivity, DNS, and global load balancing. Sources: [6] |
| Customer-managed gateway data plane | Limited: Connected gateway The gateway runs on a customer computer, container or server. The Console and API run in the Verdictan organization region; the gateway requires a control-plane connection. | Documented It is a control plane for Gateway API data planes in supported OpenShift Container Platform clusters. Sources: [7] |
| Model API exposure | Documented The customer runs the gateway, which connects to the Verdictan control plane for configuration and authenticated requests. Supported request families have different policy coverage. | Limited: Chat Completions Red Hat demonstrates OpenAI-compatible /v1/chat/completions endpoints for private or external models. Sources: [11] |
| Declarative configuration | Limited: Documented boundary Versioned gateway configurations declare provider targets, routing and policy. Configuration files are not a no-code agent builder or model-version registry. | Documented Teams apply Gateway, HTTPRoute, AuthPolicy, RateLimitPolicy, TokenRateLimitPolicy, DNSPolicy, and TLS policy resources. |
| Policy and traffic management | ||
| Route-level identity policy | Limited: Documented boundary Applications use scoped Verdictan API tokens, distinct from gateway tokens and upstream provider credentials. Bindings can restrict gateway, team, user, provider, model and spend access. Sources: [19] | Documented AuthPolicy supports API keys, JWT or OIDC identity, groups, defaults, and route-level overrides. |
| Token rate limits | Limited: Distinct limit paths The local token limiter counts buffered Chat Completions only and excludes streams and other families. Connected-request model access rules separately apply per-token RPM and TPM limits at the control plane. | Limited: Tokens only TokenRateLimitPolicy counts OpenAI-style usage by user or group and enforces time-window limits, not monetary budgets. |
| Multicluster routing | Not documented in the cited sources The reviewed Verdictan sources document provider routing, but not multicluster gateway routing. | Documented Connectivity Link supports weighted traffic, global DNS, health checks, failover, and multicluster gateway management. |
| Runtime content guardrails | Documented An active policy chain applies configured controls to supported gateway traffic. Available actions and input, output and streaming coverage depend on the individual control and request family. | Not documented in the cited sources The listed Connectivity Link 1.3 core guides cover access and traffic policies. They do not establish built-in prompt-injection, response-content or PII inspection. Confirm any guardrail integration separately. |
| MCP, evidence, and validation | ||
| MCP gateway | Limited: Separate MCP surfaces A published agent hostname exposes Verdictan tools over streamable HTTP MCP. A separate, host-enabled MCP provider bridge calls external MCP backends with configurable tool checks; this is not an enterprise server catalog. | Limited: Technology Preview Version 1.3 aggregates MCP servers, but Red Hat labels the gateway Technology Preview and not production-ready. |
| MCP tool filtering | Limited: Separate MCP surfaces A published agent hostname exposes Verdictan tools over streamable HTTP MCP. A separate, host-enabled MCP provider bridge calls external MCP backends with configurable tool checks; this is not an enterprise server catalog. | Limited: Technology Preview Preview virtual servers combine curated tool lists with identity-based discovery filters. Tool calls still need authorization. Sources: [14] |
| Gateway activity records | Documented Runtime Events record request decisions. History retains content only when capture is enabled. Trail separately records control-plane changes and hash-chain integrity; these are different evidence surfaces. | Documented Connectivity Link documents Prometheus metrics, OpenTelemetry traces, Envoy access logs, alerts, and Grafana dashboards. Sources: [9] |
| Kubernetes policy acceptance checks | Limited: Documented boundary Local policy tests compare configured verdicts, reason codes and supported output assertions with supplied cases. They do not establish provider access or complete live gateway behavior. Sources: [28] | Limited: Acceptance checks Kubernetes status conditions and documented request checks confirm policy acceptance and enforcement. Verify broader regression testing. |
Questions
Is Connectivity Link only an AI gateway?
No. It also provides API management, multicloud and multicluster connectivity, DNS, and global load balancing.
Sources: [6]
Does it require OpenShift?
The 1.3 documentation defines supported OpenShift Container Platform and Service Mesh combinations.
Sources: [7]
Can it enforce model token limits?
Is the MCP gateway ready for production?
What evidence does it expose?
Red Hat documents Prometheus metrics, OpenTelemetry traces, Envoy access logs, alerts, and Grafana dashboards.
Sources: [9]
What should a pilot verify?
Sources and scope, updated Nov. 5, 2026
This comparison summarizes official documentation. Each reference shows its own review date. A documentation gap does not prove that a feature is absent. Product scope, plan access, beta status and support can change; these sources do not establish equivalent performance or a tested integration.
- 1. Verdictan: Verdictan AI governance gatewayReviewed Aug. 11, 2026
- 2. Verdictan: Verdictan platformReviewed Aug. 11, 2026
- 3. Verdictan: Verdictan documentation overviewReviewed Aug. 11, 2026
- 4. Verdictan: verdictan gateway runReviewed Nov. 5, 2026
- 5. Verdictan: Usage costs and budgetsReviewed Nov. 5, 2026
- 6. Red Hat: Red Hat Connectivity LinkReviewed Nov. 5, 2026
- 7. Red Hat: About Connectivity Link 1.3Reviewed Nov. 5, 2026
- 8. Red Hat: Deploying Red Hat Connectivity LinkReviewed Nov. 5, 2026
- 9. Red Hat: Connectivity Link observabilityReviewed Aug. 11, 2026
- 10. Red Hat Developer: Manage AI resource use with TokenRateLimitPolicyReviewed Nov. 5, 2026Updated Feb. 18, 2026
- 11. Red Hat Developer: Model-as-a-Service: How to run your own private AI APIReviewed Aug. 11, 2026Updated June 12, 2026
- 12. Red Hat: Introduction to the MCP gatewayReviewed Aug. 11, 2026
- 13. Red Hat: Installing and configuring MCP gatewayReviewed Aug. 11, 2026
- 14. Red Hat: Creating virtual MCP serversReviewed Aug. 11, 2026
- 15. Red Hat: Connectivity Link 1.3 release notesReviewed Nov. 5, 2026Updated April 30, 2026
- 16. Verdictan: Runtime request familiesReviewed Nov. 5, 2026
- 17. Verdictan: Gateway and control-plane architectureReviewed Nov. 5, 2026
- 18. Verdictan: Provider configurationReviewed Nov. 5, 2026
- 19. Verdictan: Manage API tokensReviewed Nov. 5, 2026
- 20. Verdictan: Rate limit configurationReviewed Nov. 5, 2026
- 21. Verdictan: Policy configuration overviewReviewed Nov. 5, 2026
- 22. Verdictan: Policy controls catalogReviewed Nov. 5, 2026
- 23. Verdictan: Connect an MCP clientReviewed Nov. 5, 2026
- 24. Verdictan: Execution targets and runnersReviewed Nov. 5, 2026
- 25. Verdictan: Observability configurationReviewed Nov. 5, 2026
- 26. Verdictan: Runtime configuration and response cachingReviewed Nov. 5, 2026
- 27. Verdictan: Trail and audit evidenceReviewed Nov. 5, 2026
- 28. Verdictan: Test configurationReviewed Nov. 5, 2026
- The Connectivity Link 1.3 MCP gateway is a Technology Preview and is not recommended for production.
- TokenRateLimitPolicy depends on an OpenAI-style usage.total_tokens response field.
- Confirm supported OpenShift, Service Mesh, operator, identity provider, DNS, Redis, and subscription combinations.
Verdictan is not affiliated with Red Hat. Product names can be trademarks of their respective owners.
Test both with your traffic
Try Verdictan with representative traffic after you compare the documented boundaries. Or talk to sales first.
Create account