Files
OmniRoute/docs
datrixlab 23677dacf0 fix(redis): namespace warmup circuit-breaker keys with REDIS_KEY_PREFIX
REDIS_KEY_PREFIX is documented as the namespace for all OmniRoute Redis
keys, and the rate limiter, auth cache and quota store honor it. The
warmup circuit breaker hardcoded `omniroute:warmup:cb:`, so with a custom
prefix on a shared Redis its keys still landed in the default namespace:
outside a key-pattern ACL such as `~tenantA:*`, and shared between
instances that set different prefixes to keep apart. The #11042 review
flagged this client as the one the prefix missed.

Derive the prefix the way redisQuotaStore does. With REDIS_KEY_PREFIX
unset or blank the key is byte-identical to before. The ops doc,
ENVIRONMENT.md and .env.example now list the fourth workload, and the ops
doc notes that a forbidden connection's key is persisted without a TTL,
so it does not age out after a prefix change.
2026-09-11 15:32:58 +07:00
..
2026-06-29 08:40:06 -03:00

title, version, lastUpdated
title version lastUpdated
OmniRoute Documentation 3.8.40 2026-06-28

OmniRoute Documentation

Navigable index of the OmniRoute documentation set. Topics are grouped by intent so you can find what you need quickly.

Looking for the project overview, install steps, or release notes? See the root README.md, ROADMAP.md, CHANGELOG.md, and CONTRIBUTING.md.


For Non-Tech Users

Simple guides for using OmniRoute — no technical background needed.

getting-started/

guides/


For Tech Users

Technical documentation for developers and contributors.

architecture/

How the system is put together — read these to understand the runtime, code layout, and resilience model.

reference/

Lookup material — API surface, environment variables, CLI flags, provider catalog.

frameworks/

Pluggable subsystems exposed to clients, agents, and operators.

routing/

Combo routing, scoring, and replay.

security/

Guardrails, compliance, stealth, and the mandatory patterns for handling public credentials and error messages.

compression/

Prompt compression engines, rules, and language packs.

providers/

Provider-specific integration guides.

comparison/

ops/

Release, deployment, proxies, tunnels, coverage, database, monitoring.

diagrams/

Mermaid sources and exported SVG/PNG diagrams referenced from the docs above. See diagrams/README.md.

i18n/

Translated mirrors of the documentation in 50 locales (plus the English originals — 51 languages in total). See i18n/README.md for the supported language list.

screenshots/

Static screenshots used by the dashboard and the README. Not part of the doc body.


Auto-generated artifacts

  • reference/PROVIDER_REFERENCE.md is generated by scripts/docs/gen-provider-reference.ts from src/shared/constants/providers.ts. Do not edit by hand.
  • The /docs UI is backed by Fumadocs MDX source generation from the subfolders above.