Skip to content

Glossary

Authoritative definitions for terms used across docs, code, and customer-facing material. If a term is ambiguous, define it here before using it.

TermDefinition
AdapterA per-provider component that translates the canonical AI-ESB request format into a specific provider’s API format and back.
AI-ESBThis product. AI Enterprise Service Bus.
Audit log / Audit ledgerThe append-only, hash-chained, tamper-evident record of everything that happens in the system.
BYOKBring Your Own Key. Customer-managed encryption keys held in the customer’s KMS, used to wrap AI-ESB-generated data keys.
Compliance packThe bundle of control mappings, evidence, and attestations supporting a regulatory framework (e.g. SOC 2, HIPAA).
Control planeThe administrative side of AI-ESB — tenant management, billing, licensing, policy authoring. Separate from the data plane.
Data planeThe request-handling side — gateway, router, adapters. Optimised for throughput.
Data residencyThe geographic constraint on where data can be processed and stored, set per-tenant or per-request.
EgressA request leaving AI-ESB toward an external model provider.
Eval / Eval harnessThe system that runs golden test fixtures to verify routing decisions, redaction behaviour, and end-to-end quality.
Failover chainAn ordered list of providers/models the router will try in sequence if the primary fails.
FinOpsFinancial operations — cost tracking, budgeting, chargeback, optimisation.
GatewayThe edge service handling auth, rate limiting, and request orchestration. The front door.
Industry packA bundle of routing rules, prompt templates, policies, and compliance mappings tailored to a vertical (healthcare, finance, etc.).
Licence (on-prem)A signed JWT containing feature flags, expiry, and customer ID, validated at runtime by on-prem deployments.
MarkupThe margin AI-ESB adds on top of provider costs (where applicable to the commercial model).
OPA / RegoOpen Policy Agent and its policy language. Used for policy evaluation.
PackShorthand for industry pack.
PII / PHIPersonally Identifiable Information / Protected Health Information. Subject to detection and redaction.
PolicyA versioned, declarative rule that constrains what requests can do. Inbound or outbound.
PrincipalAn authenticated identity — human user or service account.
ProjectA logical grouping inside a tenant; typically one application or team.
RedactionRemoving or tokenising sensitive content from a request before it leaves the trust boundary.
Residency tagThe geographic constraint attached to a request (US, EU, AU, UK, …).
RouterThe component that decides which model handles a given request.
Semantic cacheA cache keyed on embeddings, returning previous responses for semantically similar prompts.
Sub-processorAn external service (e.g. Anthropic, OpenAI) that processes customer data on AI-ESB’s behalf.
TenantA customer organisation. The unit of isolation, billing, policy, and contract.
Trust centreThe customer-facing site exposing certifications, sub-processors, and security posture.
Walking skeletonThe minimum end-to-end working slice; M1 of the roadmap.