Knotbind documentationOpen dashboard
Gateway modules overview

Paid add-ons that extend the Knotbind Gateway.

Gateway modules are paid, per-workspace add-ons you configure from the Knotbind dashboard. Each one extends what your managed Gateway does with every request that passes through your access key.

What modules do

Each module is a paid add-on. Semantic Cache is applied on your Gateway. Content Guardrails and Request Analytics run in Knotbind. Model Failover and Advanced Rate Limits add rules and quotas for your access keys. You turn a module on from the dashboard. A rule or quota is added on the Gateway page and takes effect without a restart.

Module catalog

ModulePriceApplies toDescription
Semantic Cache$19/moChat and completion responsesCache LLM responses by exact match or semantic similarity. Cut cost and latency for repeated or similar prompts.
Content Guardrails$19/moJSON chat responsesReplaces email addresses, US phone numbers, US Social Security numbers and payment card numbers in message and reasoning text.
Request Analytics$15/moRecent requestsGroups this workspace's recent requests by provider and model on the Gateway page.
Model Failover$29/moOne access keyAdds a fallback model list for one access key. Enabling it creates no rule.
Advanced Rate Limits$12/moOne access keyAdds a requests-per-minute quota for one access key, on top of the key's own limit.

Pricing

Each module adds a fixed monthly fee to your Pro or Business subscription. Your base plan already includes the Knotbind Gateway itself; modules are optional add-ons. Enable or disable a module at any time — the change takes effect immediately, and the next invoice reflects it.

What is available now

ModuleState
Semantic CacheAvailable. Configure it on Gateway modules.
Content GuardrailsAvailable. Knotbind redacts four patterns in JSON chat message and reasoning text.
Model FailoverAvailable. Enable it, then add a fallback rule on the Gateway page.
Advanced Rate LimitsAvailable. Enable it, then add a requests-per-minute quota on the Gateway page.
Request AnalyticsAvailable. The Gateway page groups recent requests by provider and model.

A module that is enabled but has no rule or quota yet is marked Not configured on the Gateway page. Content Guardrails covers four patterns only. For anything else, contact us.

Enabling a module

Open Gateway → Gateway modules as an Owner. Each module shows its price and state. Enable it there. Semantic Cache is configured on that page. Fallback rules and extra quotas are added on the Gateway page after the module is enabled. The Gateway page reports whether the module is running, not configured, or in error.

How configuration reaches your Gateway

Knotbind owns the whole path. Your dashboard settings are validated server-side, applied to your Gateway, and stored against your workspace so they survive restarts. When a module is enabled, the /v1 proxy also forwards that module's request headers — for Semantic Cache, the x-knotbind-cache-key header that names a cache entry. Headers belonging to a module you have not enabled are never forwarded.

Module configuration is private to your workspace: another workspace cannot read or change it, and every enable, disable and configuration change is written to your Audit Record with the acting member.