Private AI Platform for Sensitive Workloads
Run Kubernetes-native inference in private or hybrid environments with explicit runtime control, auditable context access, and operational surfaces designed for production teams.
How the portfolio fits together
FlexInfer anchors the runtime layer with model lifecycle, serverless activation, routing, and GPU-aware operations, while Loom Core and fi-fhir extend context and integration boundaries around it.
FlexInfer
Kubernetes-native model lifecycle, OpenAI-compatible routing, and GPU-aware runtime controls for predictable private or hybrid inference.
- Deployment boundary
- Model runtime placement, scheduling, caching, and activation stay inside your cluster boundary.
- Integration boundary
- Applications hit standard inference APIs while runtime operations stay inside your network and observability stack.
Loom Core
Registry-driven MCP config generation, daemon routing, and enterprise context controls roadmap (gateway, RBAC, executor).
- Deployment boundary
- Centralizes MCP server lifecycle and policy boundaries for internal tools and agent access.
- Integration boundary
- Defines how agents reach internal systems with auditable routing and least-privilege intent.
fi-fhir
Healthcare-focused ingestion and transformation workflows (HL7v2 to FHIR) with profile-driven, testable data handling.
- Deployment boundary
- Data transformation pipeline runs in your controlled environment and deployment topology.
- Integration boundary
- Profile-driven mapping and validation isolate source variability while preserving operational traceability.
Operator mission-control surfaces
Loom Core governs context and policy boundaries. MentatLab adds the operator-facing orchestration UX for DAG design and run visibility.
MentatLab
Mission Control interface for building, monitoring, and executing DAG-based agent workflows in private environments.
Loom Core governs context routing and policy boundaries; MentatLab provides the operator UX for DAG design and run visibility.
- Deployment boundary
- UI, gateway, and orchestrator services run inside your Kubernetes footprint alongside internal agent workloads.
- Integration boundary
- Connects orchestration workflows to internal MCP-governed tools and runtime services without moving data to shared SaaS control planes.
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.
- Deployment boundary
- Connects via LAN (trusted network) or Gateway (zero-trust with mandatory TLS) to your Loom Core HUD instance.
- Integration boundary
- Read-only fleet access with scope-gated mutations. Mobile tokens are isolated from internal agent routes with per-actor rate limiting and structured audit logging.
Current foundations and in-progress controls
4 controls are available today. 2 controls are currently in progress.
Healthcare-aligned implementation stories
A healthcare-first proof path demonstrates how this portfolio handles sensitive data transformations and operational reliability in private environments.
fi-fhir healthcare integration workflows
Profile-driven parsing and transformation for HL7v2 and FHIR in production-oriented workflows.
Operationalizing healthcare API integrations
Reliability patterns for long-lived, partner-facing integration surfaces under operational pressure.
Move from positioning to execution
Start with a readiness audit to baseline risk, cost, and deployment constraints. Then scope architecture work for your environment.