Product lanes for private AI operations
Compare runtime, context, and sensitive-data integration lanes. Then validate deployment and integration boundaries before rollout.
Match runtime, context, and integration responsibilities to the right lane.
Confirm deployment and integration boundaries before production.
Track Loom Core enterprise controls currently in progress.
Decide lane ownership, then execute
Start at Platform for portfolio context, then use docs and playground for implementation flow.
Loom
Editor-first MCP tooling with registry-driven config sync, shared skills, and agent context workflows.
- Single registry across editors and assistants
- Shared skill and context workflows
- Consistent MCP server rollout patterns
FlexInfer
Kubernetes-native inference routing and deployment tooling with schema-backed configuration and operational workflows.
- Routing + backend orchestration with clear config contracts
- Predictable rollout, rollback, and capacity tuning
- Docs and playground workflows stay in sync
fi-fhir
Source Profiles, pipeline mapping, and HL7v2 to FHIR workflows for production-grade healthcare integration.
- Profile-driven ingestion across legacy healthcare formats
- Pipeline stages for parse, transform, and validate
- Operationally friendly mapping and troubleshooting flow
MentatLab
Operator-facing DAG orchestration UI for private environments, paired with Loom Core context and policy controls.
- Mission-control UI for DAG workflow design and run visibility
- Complements Loom Core policy boundaries and context routing
- Deploys inside private Kubernetes environments with internal tooling
Loom Core control plane + MentatLab execution UX
Loom Core governs context routing and policy boundaries; MentatLab provides the operator UX for DAG design and run visibility.
Position lanes before implementation
Use Platform to frame on-prem scope, then use Products to select lane-level tooling and docs.
Validate workflows end-to-end
Validate routing config, integration mappings, and registry workflows with docs-backed tool surfaces.
Lane boundary matrix
Loom Core capability roadmap
Enterprise controls are part of the Loom Core lane and currently in progress.
Core lanes: runtime, context control, and sensitive-data integration.
Boundary types to validate before rollout: deployment and integration.
MCP Gateway, RBAC, and dev-box executor are being built in the Loom Core enterprise lane.
Platform architecture
High-level views of inference routing, the FlexDeck API surface, and GPU GitOps automation across the platform stack.
Multi-model inference platform
Routing layer, providers, and platform boundaries.
FlexDeck public API
Sanitized read-only API surface for live operations data.
