The rzfz.ai Stack

The rzfz.ai Stack — the integrated open-source stack for local AI infrastructure — bundles curated open-source modules as Docker Compose containers, behind Caddy as the single externally reachable entry point and Authentik SSO, on the rzfz.ai Box, your own Ubuntu 26.04 servers, or in the cloud.

The Stack Map

From the reverse proxy to the agents — the entire rzfz.ai Stack, live from the data, grouped by layer. Click, focus, or tap a tile for details.

  • developed by razzfazz.ai GmbH
  • Experimental

Agentic AI

Data & documents

Standard applications & security

Operations

LLMs & RAG

Core

Agent architecture — per user, sandboxed, all local

The Agent-Manager gives every user their own sandboxed agent — reachable from any local chat surface, with no cloud involved.

Local on your box · no cloud

Access — native, everywhere local

Open WebUI
Web terminal (OpenCode)
Matrix
Hermes · Moltis personal agents
Agent-Manager provisions · per user · sandboxed

Per user: sandboxed agent instances

Sandbox

Agent · User A

Sandbox

Agent · User B

Shared local services

Local LLM inference
RAG / knowledge Cognee · LightRAG
Documents Docling · Tika
Tools via MCP MCP-Manager → Gitea · web search

What the stack does for you

Seven core capabilities, ready to use on your own hardware — each already proven in real use cases.

Local Workflow Automation

Automate business processes with AI — on your own hardware

In practice →

Local Knowledgegraph Brain

One central company brain for agents, chat and workflows

In practice →

Local Personal Agents

Personal AI agents per employee — no Telegram, no WhatsApp needed

Document OCR & Interpretation

From PDF to structured data — locally

In practice →

PII Redaction

Detect and redact personal data — in text and images

In practice →

Features

The rzfz.ai Stack — the integrated open-source stack for local AI infrastructure — covers seven core scenarios end to end. Each feature combines several modules into a finished use case, entirely on your own hardware.

Local Chat

ChatGPT comfort without a word leaving the building

Open WebUI is the central chat interface for every model on the box — combining retrieval-augmented generation, web search and speech in/out in one interface. In the background, GPUStack with llama.cpp handles inference on your own GPU, so every request is answered locally. Because the model, vector search and interface all run on the same infrastructure, no prompt and no answer ever leaves the building — with no external API dependency at all. In practice, Open WebUI serves as the front end for central knowledge bases and industry-specific RAG applications, from production control to foreign trade.

Modules: Open WebUI, GPUStack + llama.cpp

In practice: Central RAG knowledge base for production control , Finding TARIC goods codes via RAG

Local Workflow Automation

Automate business processes with AI — on your own hardware

Dify orchestrates business processes as visual workflows — from simple classification to multi-step document pipelines with approval steps. Every node in the workflow runs against the stack's local models, so automations can be assembled without programming knowledge and tested directly against real business data. Because orchestration and inference run on the same box, sensitive client and customer data stays in house throughout processing. In production, Dify already classifies support emails for an IT service provider, supports accounting processes at a tax advisory firm, and structures digitalization projects in consulting.

Modules: Dify

In practice: Support email classification for IT operations , AI-assisted annual financial statement review & documentation , Framework for digitalization consulting

Local Knowledgegraph Brain

One central company brain for agents, chat and workflows

Cognee builds a knowledge graph across your documents and systems and answers questions via GraphRAG instead of plain keyword search — more precise for complex relationships and across document boundaries. In the stack it serves as shared memory that chat, workflows and agents access through the MCP registry, instead of every module keeping its own knowledge. Because the knowledge graph is built entirely on your own hardware, internal documents and process knowledge stay in house — Cognee is currently included as an experimental module and under active development. At one production company it already consolidates manuals, incident history and process documentation into one central knowledge base that staff query simply via chat.

Modules: Cognee

In practice: Central RAG knowledge base for production control

Local Personal Agents

Personal AI agents per employee — no Telegram, no WhatsApp needed

Every employee provisions their own personal agents through the agent manager — Hermes as a Python agent with persistent memory and more than 30 tools, Moltis as a Rust-based agent server with Matrix integration. They are reached the normal way, through Open WebUI, with no need for Telegram, WhatsApp or any other external messenger. Because the agent manager, Hermes and Moltis all run on the same box as the models, memory contents and conversations stay entirely local — all three are currently included as experimental building blocks of the stack. This makes it possible to build personal assistants that remember earlier requests and take on tasks independently, without data ever leaving your own infrastructure.

Modules: Agent Manager, Hermes, Moltis

Local Coding Agents

No code leaves the box

Coding agents run in a protected container terminal on the box or master — with access to the local Gitea and on-box coding models. They take on bounded jobs like raising test coverage, refactorings or spec-driven implementation and deliver results as merge requests. With models, code and git server on the same infrastructure, there are no external API keys and not a single line of code leaves the premises. One customer already runs an agent that raises unit-test coverage around the clock.

Modules: Codex, OpenCode, gsd-pi, Gitea, OpenHands

In practice: 24×7 dev agent raising test coverage , Local coding with on-box models

Document OCR & Interpretation

From PDF to structured data — locally

Docling, Tika and Gotenberg read, convert and interpret documents of every kind — from PDFs and Office files to scanned receipts with layout analysis. Vision models on your own GPU handle image recognition, while Stirling PDF is available as a toolbox for merging, splitting and converting. Because the entire pipeline — recognition, conversion and vision inference — runs on the same infrastructure, invoices, contracts and other sensitive documents never leave the building; Docling, Tika and Stirling PDF are currently included as experimental modules. In production, this pipeline already pre-processes receipts for a tax advisory firm and extracts inbound customer documents before sensitive data gets redacted.

Modules: Docling, Apache Tika, Gotenberg, Stirling PDF

In practice: AI-assisted annual financial statement review & documentation , Document extraction and redaction of sensitive data

PII Redaction

Detect and redact personal data — in text and images

Microsoft Presidio detects and anonymizes personal data in document pipelines before it is passed on to other modules — more than 30 categories, in text as well as in images. The Analyzer identifies sensitive spots, the Anonymizer redacts or replaces them, and the Image Redactor does the same job for photos and scans. Presidio runs internal-only as a preprocessing step on the same box as the other modules — personal data gets redacted before it ever reaches a language model; the module is currently included as an experimental building block of the stack. It is already used to redact inbound customer documents and, in image analysis for patient care, to keep sensitive health data entirely within the facility.

Modules: Presidio

In practice: Document extraction and redaction of sensitive data , Local image analysis in patient care

The stack in action

Management dashboard of the rzfz.ai stack with an overview of every container, GPU/VRAM usage and running LLM models

Management UI

Manage it all in one place

The rzfz.ai-developed management UI runs the whole stack — backup & restore, updates, secrets, users. No shell required.

Developed by rzfz.ai →
OpenCode coding agent in the web terminal of the rzfz.ai Stack, running in a sandbox

Agents

Personal & coding agents

The agent manager gives every user their own persistent agents. Coding agents run in a sandbox inside the stack — source code never leaves the box.

Local LLM

Models run locally — GPUStack

GPUStack serves the language models on your own hardware — no request ever calls out to a cloud.

PII redaction with Presidio in the rzfz.ai stack: the original document on the left, the same page with personal data blacked out on the right

Privacy

Personal data stays redacted

Presidio finds and redacts personal data before a document goes anywhere else — automated, local and auditable.

Knowledge Graph

Your organization's memory

Cognee turns your documents into a living knowledge graph — entities, relationships and summaries your agents reason over like a shared memory. All local, on your box.

Knowledge graph generated by Cognee in the rzfz.ai stack: documents, text chunks, extracted entities, types and summaries as a connected graph

Developed by rzfz.ai

The stack is more than the sum of its open-source parts: we build these components ourselves — the first-party layer that turns loose OSS into a product.

Config UI: management dashboard with an overview of every container, GPU/VRAM usage and running LLM models in the rzfz.ai stack

Config UI

The Management UI: run the whole box from one screen

The rzfz.ai-developed management UI is the stack's control center — not just a backup tool, but a full operations cockpit: turn modules on and off, manage secrets, roll out updates, trigger backups, upload certificates, and run a factory reset when things go wrong.

One dashboard, many views — modules, module configuration, Help Center and licenses below.

Start portal linking to every unlocked module in the rzfz.ai stack

Start portal

Start portal: one click to every module

After login, users land on the rzfz.ai-developed start portal — a landing page that automatically links every unlocked module. No bookmark chaos, no hunting for the right URL.

Agent Manager admin UI for managing personal and coding agents in the rzfz.ai stack

Agent manager

Agent manager: run personal and coding agents

The agent manager gives every user their own persistent agents — including coding agents that run in a sandbox inside the stack. The MCP manager wires matching integrations into those agents automatically.

Setup screen for configuring a custom coding agent in the rzfz.ai stack

Custom coding agent

Bring your own coding-agent tool

Prefer your own coding-agent tool? Install it as a user-defined coding agent in the persistent workspace — configured directly through the agent manager.

All seven building blocks at a glance

Config Portal

Config portal — central interface for configuring the rzfz.ai stack

Help Center

Help center — locally hosted documentation and support articles for the stack

Start Portal

Start portal — landing page linking to every unlocked module in the stack

Licenses

License management — activation and status of unlocked modules and bundles

Agent Manager

Agent manager — management and monitoring of every agent running in the stack

MCP Manager

MCP manager — registration and permissioning of MCP servers for agents

User Defined Coding Agents

User-defined coding agents — free choice of your own coding-agent tool in a persistent workspace

"Nothing leaves the box unless a module is explicitly configured to reach out."

Hardening & compliance

The rzfz.ai Stack — the integrated open-source stack for local AI infrastructure — is hardened for enterprise use: identity, network and compliance are designed in from the start, not bolted on afterward.

Identity & access

Authentik sits in front of every module — no service is reachable without signing in. Role-based access control (RBAC) and multi-factor authentication (MFA) are the default, not an add-on.

Network hardening

  • Caddy is the only externally reachable entry point — with rate limiting against abuse.
  • The Docker daemon is never directly exposed; a Docker socket proxy mediates every access.
  • An SSRF proxy filters outbound HTTP calls from workflows before they leave the network.
  • Every service port is bound to localhost — nothing listens on a public interface.

Compliance

The security documentation includes mapping tables for NIS2 and ISO 27001, plus an assessment against the OWASP LLM Top 10. Every release ships with an SBOM and a security assessment.

Secrets & backups

Secret rotation tooling and GPG-encrypted backups are part of standard operations — no plaintext credentials, no unencrypted backups.

Commercial operation

The community edition, the rzfz.ai subscription and the separately bookable services are described in full on the Enterprise page — including prices and what is explicitly not included.

Subscription & services in detail →

Releases

The rzfz.ai Stack — the integrated open-source stack for local AI infrastructure — is versioned with CalVer and currently ships on a monthly release cycle. The list below shows every release, newest first.

Roadmap

2026.09 and beyond

Directional — planned features, subject to change.

Coming in 2026.09

  • LLM Manager — one console for the whole inference fleet: worker management, model deployment straight from the HuggingFace catalogue, live dashboards, a playground plus per-API-key usage and cost overview.
  • Managed worker nodes — attach additional inference nodes with a single command; runner images are distributed, updated and rolled back centrally by the master.
  • Unified agent portal — all personal agents (coding tools, Hermes, Moltis) in one interface with a multi-pane view.
  • Stack-wide LLM observability — chat, workflows and agents feed cost, latency and token metrics into one shared dashboard.
  • Platform currency — Open WebUI 0.11, Dify 1.16.1 and a base-image refresh across the whole stack.

On the horizon

  • Log and metric export into customer-owned SIEM and monitoring systems.
  • Support for new model architectures and faster inference through speculative decoding.
  • GRC building blocks for security monitoring and ISMS support (under evaluation).
  1. v2026.08-ga

    , currently v2026.08-ga.15 of 21 August 2026 — Current stable release

    Offline & air-gapped operation: the box runs, installs and updates entirely without internet.

    • Offline & air-gapped — installation, updates and module operation without internet access: offline bundles including every image, completeness checks before each restart, optional kernel-side egress sealing of the host.
    • Apple Silicon inference — Mac machines serve as local inference nodes, integrated seamlessly into the box through a gateway.
    • rzfz.ai ShortCuts — curated mini-apps for business users, managed through the start portal.
    • Enterprise documentation portal — access-protected customer documentation at docs.rzfz.ai.
    • Domain change in one click — a changed box domain name now propagates fully: SSO provider, login URLs and every service follow automatically.
    • Password manager hardened — Vaultwarden stores in PostgreSQL (part of the standard backup), SSO login issues fixed, compatibility with current Bitwarden clients.
    • Security and currency sweep — including a critical Gitea hotfix (CVE-2026-59774), updates for Matrix, LightRAG, Valkey and base images; four hardened internal auth paths.
    • Continuously hardened across 15 patch releases; public downloads now on GitHub (github.com/rzfz-ai/rzfz-ai-service-stack).
  2. v2026.07-ga

    — Previous release

    Open-core licensing goes public: Apache-2.0 Community, the rzfz.ai Subscription and coding-agent workspaces

    • Open-core licensing, delivered publicly — a free Apache-2.0 Community tier, a source-available tier (BUSL-1.1) under the rzfz.ai Subscription, a live license overview, a public GitHub mirror and a published Community Wiki
    • Coding-agent workspaces — personal coding agents are now per-type sandboxed containers (OpenCode, Codex, user-defined) with live web-app preview plus per-user MCP integrations and memory
    • Dify 1.15.0 — single sign-on no longer asks you to log in twice
  3. v2026.06-ga

    One default model: qwen3.6 at 1M context for chat, coding and vision

    • qwen3.6 is the one default model for chat, coding, general tasks and vision at 1M context — no per-role model juggling
    • Document Q&A works out of the box — the reranker and chunking defaults that make RAG find the right facts ship pre-configured
    • Smoother upgrades — both the standard and the from-2026.04 upgrade paths are validated, with upgrade self-healing and journaling
    • Unattended USB appliance — a bootable USB image performs an unattended Ubuntu 26.04 install and prepares the stack for first boot
    • Audit-ready compliance tables — structured NIS2 (EU 2022/2555) and ISO/IEC 27001:2022 evidence in the security architecture
  4. v2026.05-ga

    Per-user personal agents: Hermes, Moltis and coding agents in the "My Agents" drawer

    • rzfz.ai start portal — tile launcher with per-user pinning
    • New Crawl4AI module and observability profile (OpenLIT + ClickHouse)
    • Open WebUI ↔ Dify manifold pipe
  5. v2026.04-GA

    One command from base install to fully configured stack: razzfazz-post-install.sh

    • razzfazz-post-install.sh automates GPUStack model deployment plus Open WebUI and Dify setup in one step
    • Two experimental RAG modules: LightRAG (graph-aware) and Cognee with FalkorDB
    • Encrypted .env snapshots before every configuration change; AMD GPU inference fix

System requirements

The rzfz.ai Stack — the integrated open-source stack for local AI infrastructure — supports only Ubuntu 26.04 LTS as an operating system. The same rule applies to every deployment profile: We name the limits before you find them.

Supported deployment profiles of the rzfz.ai Stack rzfz.ai Box Primary support AMD Strix Halo (Ryzen AI MAX+), 128 GB unified memory Own server / VM without GPU Supported Any Ubuntu 26.04 host, ~16–24 GB RAM NVIDIA/CUDA server Supported Ubuntu 26.04 host with NVIDIA GPUs — own hardware or GPU cloud Cloud instance Supported Any Ubuntu 26.04 cloud instance — with GPU as worker, without GPU as control plane

rzfz.ai Box

AMD Strix Halo (Ryzen AI MAX+), 128 GB unified memory

32 GB container budget + 96 GB VRAM (raisable to 110 GB)

Requirements

  • Ubuntu 26.04 LTS (pre-installed)
  • Network access, ports 22/80/443

Limitations

  • AMD-only inference — no NVIDIA/CUDA path on the box
  • vLLM currently unsupported on Strix Halo (production: llama.cpp via Vulkan)
  • The 32 GB container budget limits how many modules run concurrently
  • One intensive agent loop at a time — sizing rule ~1 box per 6–10 employees

Own server / VM without GPU

Any Ubuntu 26.04 host, ~16–24 GB RAM

Requirements

  • Ubuntu 26.04 LTS, kernel 7.x
  • Docker Engine + Compose v2

Limitations

  • CPU inference is slow — fine for light or batch workloads, not for interactive agents
  • As a control plane it delegates inference to GPU workers (boxes or cloud)

NVIDIA/CUDA server

Ubuntu 26.04 host with NVIDIA GPUs — own hardware or GPU cloud

Requirements

  • Ubuntu 26.04 LTS
  • CUDA-capable NVIDIA GPU(s)
  • Docker Engine + Compose v2

Limitations

  • Inference via llama.cpp on CUDA, models in GGUF format
  • The VRAM ceiling is a budget question, not an architectural one

Cloud instance

Any Ubuntu 26.04 cloud instance — with GPU as worker, without GPU as control plane

Requirements

  • Ubuntu 26.04 LTS
  • Docker Engine + Compose v2

Limitations

  • Data sovereignty depends on the cloud provider — for strictly local scenarios choose the box or own hardware

Mixed fleets

Many teams combine profiles instead of committing to one: a control plane without its own GPU orchestrates several rzfz.ai boxes as local inference workers and, when needed, pulls in additional cloud GPU workers for peak load. Core operations stay local — peak load is covered by resources booked from the cloud, without giving up data sovereignty. Find matching combinations under Bundles.

What do you need? What system do you have?

Type a need or your system — we tell you honestly how it fits the stack.

How integration works with us

Prewired

A module in the stack already covers it — ready to use, no extra work.

Dify plugin

The Dify Marketplace covers it — the stack inherits it automatically. for technicians

REST / MCP

If your system speaks REST or MCP, it connects directly — no detour.

Custom · built by us

Local, niche business software that's in no catalog — that's exactly what we build the integration for.

Write to us

Your details come straight to us — no tracking, no cookies, no sharing beyond our processors.