> ## Documentation Index
> Fetch the complete documentation index at: https://docs.forge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Supported clients, policy depth, and protocol boundaries.

The Resource gateway terminates the client protocol, evaluates structured
facts, and opens a separate authenticated connection to the destination. No
Forge SDK is required. Direct clients use the command generated on the
Resource page; automatically routed clients keep their existing command.

| Protocol | Client support | Decisions | Data controls | Direct port |
| - | - | - | - | - |
| HTTP/HTTPS | HTTP/1.1 and HTTP/2 | Connection and request | Bounded JSON request redaction; response redaction and filtering | `443` |
| PostgreSQL | Simple and prepared commands | Connection and command | Result-column redaction and row filtering | `5432` |
| MySQL | Ordinary and prepared commands | Connection and command | Result-column redaction and row filtering | `3306` |
| Redis | RESP2/RESP3 commands and buffered pipelines | Connection and command | None | `6379` |

PostgreSQL, MySQL, and Redis always use verified TLS to the destination. HTTP
Resources can use HTTP or verified HTTPS. Forge does not provide a setting to
skip certificate verification.

Choose a protocol for its exact connection syntax, inspected fields, and
limits:

* [HTTP and HTTPS](/resources/protocols/http)
* [PostgreSQL](/resources/protocols/postgresql)
* [MySQL](/resources/protocols/mysql)
* [Redis](/resources/protocols/redis)

See [Resource Policies](/secure/resource-policies) for the shared evaluation
model, action precedence, exceptions, and approvals.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.