Runtime Overview¶
Last Updated: 2026-03-12 Purpose: Runtime summary for the current Jorvis platform.
Current Public Runtime Shape¶
- Jorvis uses Open WebUI as the primary user-facing surface.
- Jorvis API is the application layer that owns contracts, guardrails, backend routing, and document processing. It connects to five SQL providers (PostgreSQL, MySQL, Redshift, BigQuery, Snowflake) and ingests enterprise documents (Google Docs, Drive, PDF, DOCX, XLSX, PPTX, JSON, HTML) via a ProcessorFactory pipeline with semantic indexing.
- OpenClaw runs as a separate assistant/copilot subsystem with its own chat and memory-search lanes.
- The public visuals are the best first stop for topology and flow; the rendered reference pages below provide supporting detail.
Where To Go Next¶
- Current Architecture for the platform shape and subsystem boundaries
- Model Policy Current for model-lane separation
- OpenClaw Runtime Operations for the OpenClaw runtime surface
- Jorvis Architecture Visual
- OpenClaw Control Plane Visual
How To Use This Page¶
Use this page as the short orientation layer, then open the linked reference pages or visuals for deeper detail.