Skip to main content
Live systems

Three systems you can read right now

Each row reads the same sanitized public API as the page it links to, and says whether its number is live or a saved snapshot.

  1. Factory

    The Mills delivery pipeline: every run's stages, gates, retries, and cost over the last 30 days.

    420merged of 869 runs
    Live
  2. Inference plane

    Open models on self-hosted GPUs behind an OpenAI-compatible gateway, with the engine and hardware of each one that is warm.

    4warm of 20 models
    Live
  3. Cluster

    The K3s cluster that serves this site: node readiness, GPUs, and the health score FlexDeck computes from them.

    15/15nodes ready
    Live
Measured on the clustersnapshot

Verified FlexInfer benchmark results

Serving throughput across language, embedding, and image workloads. The live feed takes over when available; otherwise this shows the latest verified cluster snapshot.

Newest record

142.1tok/s recorded peak
FlexInfer docs

Snapshot scope. Each card is one run of the FlexInfer benchmarker against a deployed model: throughput, sample and token counts, and the GPU that deployment is pinned to. Candidates are tuning experiments, not serving lanes. Records from the older benchmarker keep only backend, hardware class, memory, and throughput. Treat these as operational baselines, not a cross-vendor leaderboard.

Inspect the source records
Platform posture

Four products, one operating boundary

The stack is intentionally layered: run and customize models inside your boundary, govern how agents reach tools and context, orchestrate repeatable DAG workflows over direct API models, and use fi-fhir when the workload is sensitive healthcare ETL instead of generic demo data.

Integration points

How the products connect

Use these contracts to map deployment and integration boundaries before implementation. The platform page carries the full boundary detail for each pair.

Core stack

Loom suite, FlexInfer, fi-fhir, and MentatLab

FlexInfer runs the models, Loom governs context and policy, MentatLab gives operators the DAG view, and fi-fhir carries the healthcare workload. Product pages explain what each component does, docs explain the interfaces, and the playground checks configuration.

Agent and DAG orchestration UI

MentatLab mission control

Mission Control interface for building, validating, monitoring, and executing DAG-based agent workflows in private environments.

Loom Core governs context routing and policy boundaries. MentatLab provides the DAG design and run-visibility layer over direct API model calls, internal services, and private FlexInfer endpoints.

Mobile fleet monitoring (iOS/iPad)

Loom Companion

SwiftUI app for fleet monitoring, session management, real-time alerts, and lightweight operator control from iPhone and iPad.

Loom Core exposes a frozen v1 mobile API (18 endpoints) with OAuth PKCE auth; Companion consumes it for on-the-go visibility into agents, sessions, and infrastructure.

Component directory
  • FlexInfer

    Inference control plane for private and hybrid workloads: model lifecycle, serverless activation, routing, and GPU-aware placement.

  • Loom Core

    Single-entry MCP and context control plane: registry sync, tiered memory, Weaver orchestration, proxy + daemon routing, and controlled execution.

  • Loom

    VS Code extension for multi-platform MCP config sync, skills registry, and agent context workflows.

  • Loom Zed

    Zed integration for Loom workflows: consistent servers, shared registry, and repeatable profiles.

  • fi-fhir

    Healthcare integration tooling: Source Profiles, parsing pipeline, and HL7v2 to FHIR workflows.

Enterprise capabilities

Operator controls already shipping across the platform stack

MCP routing, role-based access control, sandbox execution, and tracing. 4 controls are available today and 2 are in progress; each card carries its status.

MCP Gateway

Available

Centralized MCP routing via loom proxy with streamable HTTP transport, bearer/OIDC/mTLS auth, and hub failover.

Single context ingress with controlled routing, auditing, and automatic local fallback.

Role-based Access Control (RBAC)

Available

Role-aware permissions for MCP tool access with audit trail, cost tracking, and OAuth 2.1.

Enforces least-privilege context access with auditable decision logs across teams and environments.

Sandbox Executor (Docker + K8s)

Available

mcp-devbox sandbox runtime with Docker and Kubernetes backends for isolated agent execution.

Runs builds, tests, and automation in controlled containers with consistent isolation and audit trails.

Operational Foundations

Available

OpenTelemetry tracing across the MCP server fleet, JSON log correlation, observability stack, and deployment controls.

Distributed tracing, structured logging, and deployment procedures for investigating runtime behavior.

HUD Cost Dashboard

In progress

Cost monitoring integration: loom/cost-stats RPC, CostMonitor polling, SSE events, and OverviewPanel KPI tile.

HUD RBAC + Audit Visibility

In progress

RBAC config RPC, denied-calls ring buffer, ServersPanel RBAC sub-tab, and OverviewPanel badge.

Consulting

Bring it into production

If you want this stack inside your environment, the fastest path is a scoped audit or build engagement.