Skip to content

docs: FAQ — gateway plane vs in-process middleware - #520

Closed
vgmartinez wants to merge 1 commit into
mainfrom
cursor/faq-gateway-vs-middleware-3217
Closed

vgmartinez wants to merge 1 commit into
mainfrom
cursor/faq-gateway-vs-middleware-3217

Conversation

@vgmartinez

Copy link
Copy Markdown
Contributor

Addresses #519.

Adds a short design FAQ under docs/ that turns the issue's risk-placement note into a page: when an agent gateway plane is the better cut than in-process middleware for tool egress, identity, break-glass, and audit.

No README or nav change: docs/ already has standalone markdown (MCP, telemetry, operational metrics) and no FAQ/concepts index. Linking this from the README would invent a new conceptual-docs pattern.

Issue #519 is left open for community Q&A.

Disclosure: Building TrustGate at NeuralTrust (CTO).

Open in Web Open in Cursor 

Turn issue #519 into a short risk-placement note under docs/.

Co-authored-by: Victor <victor.garcia@neuraltrust.ai>
@vgmartinez
vgmartinez marked this pull request as ready for review August 23, 2026 15:56
@github-actions

Copy link
Copy Markdown
Contributor

Trivy code scan — HIGH/CRITICAL

No HIGH or CRITICAL vulnerabilities found. (run)

@vgmartinez

Copy link
Copy Markdown
Contributor Author

Related cut for this FAQ lane: secrets placement is #523 (upstream MCP/provider keys on the gateway; agents get short-lived consumer identity). Orthogonal to the middleware-vs-gateway table in this PR — worth a one-line “Related reading” pointer when you next touch the doc, not a merge of the two topics.

Disclosure: Building TrustGate at NeuralTrust (CTO).

@vgmartinez vgmartinez closed this Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants