What enterprises expect from a gateway, and where Flexway stands.

Scopes per endpoint, overrides per tenant and per agent, models allowed per backend; models allowed per caller (tenant, plan, use case, client) are missing

Only the gateway holds the keys; forbidding the direct network route is the job of the customer's network egress rules

Routing by capability (chat, vision, embeddings); model aliases and use cases framed; routes per declared task are missing

Cost: a soft cap that switches; measured latency, declared cost, region and hosting class as declared criteria are missing. Quality cannot be measured by the gateway (evaluation: out of scope)

Possible through a declared route (the task says so); a classifier on the path is excluded by a product rule

The external attribute of backends and pinning of sensitive requests; the declared hosting class (cloud, private, local) is missing

Tenant and agent built; user and use case framed; application, team, project and cost centre are missing

Requests per second per caller, tokens per day and per month; a token rate per minute against peaks is missing

Monthly budget in euros per tenant, gauges and status in the console; budget alert thresholds and built-in rules are missing

429 refusal and the tenant's soft-cap switch; graduated actions for each budget level are missing

Consumption per tenant, CSV export from the console; attribution per cost centre and its export are missing

Masking of REST response fields built (redact); in prompts, nothing yet: deterministic detectors and masking

A request marked sensitive is pinned to an internal backend; data classes and the backends allowed per class are missing

Announced "by policy", not built: regions allowed per tenant or per class, proven in the trace

Input and output guardrails in the catalogue from the start, never framed

Declared patterns and the customer's guard service; the gateway is not a sufficient guarantee (the analysis says so too)

Chained audit of authorisation decisions, closed refusal codes; the guard decision line, without content, is missing

Tenant, agent, client; hashed subject in the audit; use case framed; application and cost centre

Per backend and capability; the model served is in the audit, not in the metrics

Chained audit; exportable execution proof planned; DORA and NIS2 reports on the horizon

Cost per backend, reload marks, comparison of two windows; quality belongs to an evaluation platform

Scopes, roles, unattended agents, delegation chain; contextual control of arguments (an amount by identity) is missing

The gateway requires and verifies an approval proof issued by the identity provider; the workflow stays with the customer

Scopes per endpoint, unattended: false; approval and task rights are missing

Embeddings under budget, search APIs and vector databases served as endpoints; filtering rights per document is out of scope

Configuration versioned in Git, models allowed per backend; models approved per caller planned; prompt registry and result comparison: out of scope

REST response cache; semantic cache planned; routes per task planned

Sensitive requests pinned to an internal model, relay to another Flexway; data classes and hosting planned

Declared agent client, delegated token bounded in duration and depth, an exchange that only ever narrows; rights limited to one task are missing

Every client goes through the same identity, quota and audit; attribution per application (the client) with its budget is missing

Catalogue of endpoints, Agents screen (tools, federated servers), declared backends; a unified catalogue (models, agents, tools, owners, terms) is missing

Pinning, audit without prompts; models, data and logging per class planned; execution proof planned

Planned through declared rules; autonomous selection by a model is excluded

Approved tools = contract, scopes, quotas, inter-agent traces built; contextual arguments, budget per run, registry to come

Bounded RFC 8693 delegation built; task rights and approval proof planned, together with the IAM

Recommendations as reviewed proposals (AI for operations); autonomous application is excluded: the console never mutates

Versions of an upstream; canary between inference backends; prompt versions: out of scope

Multi-gateway console framed with no milestone; common policies distributed through GitOps; shared common fragments: candidate

Foundation built; cost attribution and declared routing planned

Tools, delegation, A2A built; agent actions planned

Federation: candidate; arbitration by declared rules only

The contract's endpoint is the business action; approval and task rights planned

The binary runs locally with no central plane; signed configuration pulled by a site: planned

external-call covers HTTP; asynchronous commands: candidate

Multiple issuers, partner mTLS, token exchange, per-field encryption; declared purpose of use: candidate

Revocation by reload, closed by default, egress guards, declared automatic rollback, local protection by design; an automatic suspension decided by a detector is excluded (proposals only)