Platform
Platform Overview

Platform Overview

Xilos is an AI infrastructure platform that sits between your users and the Large Language Models (LLMs) they call. Every prompt, every response, and every token flows through Xilos, where it is observed, secured, and orchestrated before a single inference call is made.

The platform is built on three pillars — Observe, Secure, and Orchestrate — each of which can be adopted independently and composed as your needs grow.

The Three Pillars

  • Observe — Gain total visibility into AI traffic. Dashboards, query logs, cost controls, and metrics surface every query, every treatment, and every dollar in real time.
  • Secure — Enforce policy before the model is called. Guardrails detect PII, block prompt injection, and apply restriction rules that block, mask, or flag queries by intent.
  • Orchestrate — Route each query to the right model, compress prompts to cut cost, cache semantically equivalent responses, and compound knowledge across every interaction.

Request Flow

Every query that enters Xilos follows the same path. The pillars apply sequentially, and each stage can act on or transform the request before it reaches the model.

Ingest

A user submits a query through a connected application, API, or agent. Xilos receives the request and attaches a trace identifier that follows it end to end.

Secure

Restriction rules evaluate the query for blocked, masked, or flagged content. PII detection redacts sensitive fields. Prompt injection defense runs before any model is invoked. Queries that violate policy are terminated here.

Orchestrate

The internal Small Language Model (SLM) classifies query intent, selects the optimal target LLM, and applies context compression, semantic caching, and enrichment from the Context Engine. Multi-model workflows, tools, and routines are applied as configured.

Execute

The AI Kernel dispatches the prepared request to the selected model — public or private — and retrieves the response.

Observe

The response, governance actions, compression statistics, and cost breakdown are written to the Query Log and rendered on the Dashboard in real time.

Info: Stages 2 and 3 can transform the request. A masked query, for example, reaches the model with sensitive fields already redacted — the model never sees the original PII.

Multi-Tenancy

Xilos supports multi-tenant deployments out of the box. Each tenant is an isolated boundary with its own:

  • Routing rules — query-to-model mappings scoped to the tenant.
  • Restriction rules — governance policies that block, mask, or flag by tenant.
  • Dashboards and Query Log — activity and audit data isolated per tenant.
  • Users and roles — authentication and authorization managed independently.
  • Cost controls — budgets, limits, and model allow-lists set per tenant.

Tenants share infrastructure but never share data. A query submitted under Tenant A cannot be observed, governed, or served by Tenant B.

Model-Agnostic Integration

Xilos integrates with public and private models through a single, unified API. Public providers include Anthropic (Claude), OpenAI (GPT), and Google (Gemini). Private models include self-hosted deployments such as Llama and Phi.

Integration is model-agnostic in two respects:

  1. Routing rules target any supported model. A rule can send billing inquiries to Claude Sonnet, sensitive HR data to a private Llama deployment, and general knowledge questions to GPT-4 — all from the same tenant.
  2. Applications call one endpoint. Client applications send queries to Xilos, not to the underlying provider. Xilos handles authentication, routing, and response delivery, so swapping models requires no client-side changes.

Deployment Options

Xilos can be deployed in three configurations:

DeploymentDescriptionBest For
Xilos CloudFully managed SaaS hosted by Mill Pond Research.Organizations that want zero infrastructure overhead.
Self-HostedXilos runs in your own cloud or on-premises environment. Private models stay inside your network.Regulated industries and organizations with data residency requirements.
HybridXilos Cloud manages the control plane; private models run in your environment.Teams that want managed convenience alongside private model control.

Info: All deployment options expose the same API surface. Applications built against Xilos work identically across Cloud, Self-Hosted, and Hybrid configurations.

Next Steps

  • Explore the Observe pillar to understand dashboards, query logs, and cost controls.
  • Review the Secure pillar to configure guardrails and restriction rules.
  • Start with the Orchestrate pillar to build routing rules and workflows.