✨ From vibe coding to vibe deployment. UBOS MCP turns ideas into infra with one message.

Learn more
Andrii Bidochko
  • Updated: August 26, 2026
  • 7 min read

Spyre-Accelerated Retrieval-Augmented Generation on IBM LinuxONE: A Cloud-Native Architecture for Secure, High-Throughput Enterprise AI Inference

{{IMAGE_PLACEHOLDER}}

Direct Answer

The paper introduces Spyre‑Accelerated Retrieval‑Augmented Generation (RAG)—a cloud‑native, six‑subsystem architecture that runs entirely on IBM LinuxONE, leveraging the Spyre PCIe inference accelerator, the Telum II on‑chip classifier, and Red Hat OpenShift for orchestration. By keeping every step of the RAG pipeline inside a single, FIPS‑compliant hardware perimeter, the design delivers sub‑two‑second end‑to‑end latency while meeting the strict security and audit requirements of regulated enterprises.

Background: Why This Problem Is Hard

Enterprises that handle sensitive data—banks, hospitals, government agencies—face a paradox when adopting large language models (LLMs). The most capable LLMs live in public clouds or dedicated GPU farms, but the data they need to process often cannot leave the corporate firewall because of:

  • Regulatory constraints: GDPR, HIPAA, and industry‑specific mandates demand data residency and immutable audit trails.
  • Latency penalties: Shipping a request across the public internet to a remote GPU adds tens to hundreds of milliseconds, which compounds when a RAG workflow performs multiple retrieval and generation steps.
  • Security exposure: Even encrypted traffic can be vulnerable to side‑channel attacks or mis‑configurations, and many organizations lack confidence in the cloud provider’s key‑management practices.

Existing on‑prem solutions typically rely on CPUs or generic accelerators that cannot match the throughput of modern GPUs, leading to either prohibitive cost or unacceptable response times. Conversely, cloud‑only approaches sacrifice data sovereignty for raw performance. The gap is a secure, high‑throughput inference stack that can host both the retrieval engine and the generative model without ever leaving the trusted hardware boundary.

What the Researchers Propose

The authors present a modular RAG framework built around six tightly coupled subsystems:

  1. Query Intake Service – receives user prompts via REST or gRPC and normalizes them.
  2. Vector Store & Retrieval Engine – stores document embeddings in an on‑node vector database and returns the top‑k relevant chunks.
  3. Prompt Composer – stitches retrieved passages with system instructions to form a context‑rich prompt.
  4. Generative Inference Engine – runs the LLM on the Spyre accelerator, which is purpose‑built for low‑latency transformer inference.
  5. Compliance Filter – a lightweight Telum II classifier that scans the raw LLM output for policy violations, PII leakage, or disallowed content.
  6. Response Dispatcher – formats the final answer and routes it back to the caller, optionally logging for audit.

Key roles:

  • Spyre accelerator provides deterministic, sub‑millisecond matrix multiplication, enabling the LLM to generate tokens at a rate comparable to high‑end GPUs.
  • Telum II handles classification and policy enforcement with near‑zero overhead, freeing the generative path from extra passes.
  • Red Hat OpenShift supplies container orchestration, service mesh, and auto‑scaling while preserving the LinuxONE security envelope.

How It Works in Practice

The end‑to‑end flow can be visualized as a linear pipeline, but each stage runs as an independent microservice inside OpenShift, communicating over mutually authenticated TLS channels. The process unfolds as follows:

  1. Ingestion: A client (e.g., a chatbot or internal portal) posts a query to the Query Intake Service. The service validates the request against API keys and logs the payload for compliance.
  2. Embedding Lookup: The service forwards the sanitized text to the Vector Store, which uses a pre‑computed embedding model (e.g., MiniLM) stored on‑node SSDs. A k‑nearest‑neighbors search returns the most relevant document fragments.
  3. Prompt Assembly: The Prompt Composer concatenates the retrieved chunks with a system prompt that encodes domain‑specific instructions (e.g., “Answer in plain English, do not disclose patient IDs”).
  4. Generative Pass: The assembled prompt is handed to the Spyre inference engine. Spyre’s custom compiler translates the transformer graph into a PCIe‑optimized kernel, executing the forward pass entirely on the accelerator card.
  5. Compliance Screening: The raw token stream is streamed to the Telum II classifier, which flags any disallowed patterns. If a violation is detected, the filter either redacts the offending segment or triggers a fallback response.
  6. Delivery: The sanitized answer is packaged by the Response Dispatcher, optionally enriched with provenance metadata, and sent back to the originating client.

What sets this architecture apart is the elimination of any network hop that crosses the hardware trust boundary. All data—embeddings, prompts, model weights, and outputs—remain resident on the LinuxONE chassis, protected by Secure Execution (SE) technology that encrypts memory at rest and in use, and provides attestation logs for every inference request.

Evaluation & Results

The research team benchmarked the Spyre‑Accelerated RAG stack against three baselines:

  • Cloud‑GPU RAG (AWS p4d instances with NVIDIA A100 GPUs).
  • On‑prem CPU‑only RAG (x86 servers with Intel Xeon Gold CPUs).
  • Hybrid Edge‑GPU RAG (local GPU boxes connected via 10 GbE to a central data lake).

Key scenarios included:

  1. Legal‑document question answering (≈10 KB context per query).
  2. Clinical‑note summarization (≈5 KB context, strict PII filtering).
  3. Financial‑report insight extraction (≈15 KB context, high compliance load).

Findings:

MetricSpyre‑RAGCloud‑GPUCPU‑OnlyEdge‑GPU
Average end‑to‑end latency1.8 s3.6 s7.4 s4.2 s
Throughput (queries / sec)55301222
Compliance‑filter latency overhead0.12 s0.35 s0.48 s0.27 s
Data‑in‑flight encryption costnegligiblemoderatelowmoderate

Beyond raw numbers, the authors highlight that the Spyre stack achieved a 20× reduction in total latency compared with a naïve off‑platform approach, while maintaining FIPS‑140‑2 level encryption and providing immutable audit logs for every inference request. The compliance filter, powered by Telum II, added less than 100 ms of overhead, demonstrating that security does not have to come at the expense of speed.

Why This Matters for AI Systems and Agents

For AI architects building enterprise agents, the Spyre‑Accelerated RAG design offers three concrete advantages:

  • Secure by design: Confidential Computing on LinuxONE guarantees that model weights, prompts, and user data never leave the encrypted enclave, satisfying regulators without the need for costly VPNs or data‑masking pipelines.
  • Predictable performance: Sub‑two‑second response times enable real‑time conversational agents, decision‑support bots, and automated compliance assistants that would otherwise be throttled by network latency.
  • Unified orchestration: By running all services on OpenShift, enterprises can leverage existing CI/CD pipelines, auto‑scaling policies, and service‑mesh observability tools, reducing operational overhead.

These benefits translate directly into business outcomes. Financial institutions can deploy AI‑driven risk‑assessment agents that answer regulator‑style queries instantly, while healthcare providers can embed clinical‑note summarizers into EMR systems without exposing patient data to external clouds. Moreover, the modular microservice layout means that developers can swap out the vector store (e.g., integrate Chroma DB integration) or add new compliance rules without redesigning the whole stack.

What Comes Next

While the prototype demonstrates impressive latency and security, several open challenges remain:

  • Model scaling: The current implementation supports up to 13 B‑parameter models on Spyre. Future work must explore multi‑card orchestration to handle 70 B‑parameter LLMs.
  • Dynamic retrieval: Integrating real‑time document ingestion pipelines (e.g., streaming logs) would broaden applicability to security‑operations use cases.
  • Cost analysis: A detailed TCO comparison against managed cloud services is needed to guide CFOs in budgeting decisions.

Potential next steps for enterprises include piloting the architecture on existing LinuxONE installations, extending the compliance filter with domain‑specific ontologies, and exploring hybrid deployments where edge devices forward encrypted embeddings to the central LinuxONE hub.

Organizations interested in building secure AI agents can start by reviewing the original arXiv paper for technical depth, then explore the UBOS platform overview for a complementary low‑code orchestration layer. For regulated sectors, the Enterprise AI platform by UBOS offers pre‑validated compliance modules, while the AI marketing agents showcase how the same secure pipeline can power customer‑facing bots without exposing proprietary data. Finally, teams can prototype end‑to‑end workflows using the Workflow automation studio, which integrates with existing CI/CD pipelines and provides visual monitoring of latency and audit trails.

By marrying high‑throughput hardware acceleration with confidential computing and container‑native orchestration, Spyre‑Accelerated RAG charts a practical path for enterprises that demand both speed and security from their AI agents.


Andrii Bidochko

CTO UBOS

Andrii Bidochko is an AI entrepreneur and researcher focused on AI agents, reinforcement learning, and autonomous systems. He writes about the technologies shaping the future of machine intelligence, from frontier models and agent architectures to real-world AI applications.

Sign up for our newsletter

Stay up to date with the roadmap progress, announcements and exclusive discounts feel free to sign up with your email.

Sign In

Register

Reset Password

Please enter your username or email address, you will receive a link to create a new password via email.