Langfuse vs The Linux Foundation

Langfuse CLI 1.0 and new evaluator features

Langfuse CLI 1.0 released, along with new evaluator template gallery and reusable evaluators for production evaluations.

Deploying Langfuse Open-Source LLM Observability

This technical guide explains how to deploy Langfuse, an open-source observability platform for LLM applications, using Docker Compose. The deployment uses PostgreSQL for metadata, ClickHouse for trace and metrics analytics, Redis for cache/queueing, and S3-compatible object storage for media/exports, with Traefik and Let's Encrypt providing TLS. The article includes required prerequisites (Linux server 4 vCPU / 16GB RAM, Docker + Docker Compose, domain A record), step-by-step environment and docker-compose configuration, first-run setup (create organization/project and API keys), and a test-trace example using the Langfuse SDK and an OpenAI-compatible client. Publication date: 2026-08-12.

• Langfuse is an open-source observability platform for LLM applications that traces prompts/responses, tracks token usage and cost, and provides debugging analytics.
• The guide deploys Langfuse via Docker Compose using Traefik (TLS), PostgreSQL (metadata), ClickHouse (trace/metrics analytics), Redis (cache/queue), and S3-compatible object storage.
• Container images and versions shown include traefik:v3.7.0, postgres:17, clickhouse/clickhouse-server:26.5.1-alpine, and redis:7-alpine; Langfuse images used are langfuse/langfuse:3 and langfuse/langfuse-worker:3.

Reliable AI Agents: FSMs and Hidden Costs

This technical article argues that building production-grade AI agents requires engineering discipline rather than relying solely on LLM capability. It identifies common failure modes in naive agentic workflows—hallucination loops, infinite recursion, and context-window exhaustion—and recommends embedding LLMs inside deterministic Finite State Machines (FSMs) using an Orchestrator pattern to enforce valid transitions and step limits. The piece also highlights operational "hidden costs" (token complexity/latency, cost of failure, and observability/debugging overhead) and lists production best practices including human-in-the-loop approvals, structured output/schema validation, idempotent tool design, and fallback mechanisms.

• Agentic workflows are systems that perceive, plan, act, and observe to achieve multi-step goals and differ from simple prompt-response chatbots.
• Common failure modes in naive agents include: hallucination loops, infinite recursion (unbounded tool-call loops), and context window exhaustion.
• Finite State Machines (FSMs) and the Orchestrator pattern are recommended to govern LLM-driven agents, enforce valid state transitions, and limit steps.

Open Secure AI Alliance Joins the Linux Foundation to Build a Shared, Open Defense Stack for the AI Era

Originally founded by dozens of enterprise leaders and NVIDIA, the Alliance moves to neutral governance to expand industry collaboration on open AI security tools, research and shared defenses.

Open Secure AI Alliance Joins Linux Foundation for Open Defense Stack

The Open Secure AI Alliance, originally founded by NVIDIA and other enterprise leaders, has officially joined the Linux Foundation to establish a neutral governance home for developing open, shared defenses for AI systems. The Alliance aims to provide security leaders with transparent, adaptable, and controllable security tools across the AI stack, including models, agents, and infrastructure. A key initiative is the Shared AI Findings Exchange (SAFE), which will confidentially collect and analyze AI security incidents to enable collective learning and evidence-based controls. The move is expected to foster collaboration between AI, cybersecurity, and open source communities, enhancing the security posture of AI adoption across industries.

• The Open Secure AI Alliance has joined the Linux Foundation, gaining neutral governance.
• The Alliance was originally founded by NVIDIA in collaboration with members including the Linux Foundation.
• A core initiative, the Shared AI Findings Exchange (SAFE), is open for comments until September 21.

Context Passing in Multi-Agent AI Systems

Engineering teams face new challenges when capabilities are split across multiple independently deployed AI agents owned by different teams. Microsoft’s Industry Solutions Engineering (ISE) team published a case study describing three evaluated approaches for sharing conversational context across agents: (1) domain agents reading shared storage, (2) making domain agents stateful, and (3) embedding summarized conversation history in each message payload. Microsoft adopted the third approach, sending summarised history inside messages and applying a 10-turn summarisation threshold to balance fidelity and performance. The post contrasts the Model Context Protocol (MCP), which standardises agent-tool connections, with Agent2Agent (A2A), an open peer-to-peer agent communication protocol originally developed by Google and now stewarded via the Linux Foundation. The article highlights governance, security, auditability, and operational benefits of keeping domain agents stateless.

• Microsoft Industry Solutions Engineering (ISE) published a detailed account of how it addressed context passing in a multi-agent engagement.
• Agent2Agent (A2A) is an open agent communication protocol originally developed by Google and now maintained by a cross-vendor technical steering committee at the Linux Foundation.
• Microsoft evaluated three approaches for sharing conversational context (shared storage, stateful domain agents, and embedding summarised history in message payloads) and adopted payload summarisation.