busysloths-mlox 0.5.0

Deploy and manage ML/AI infrastructure on your own servers. Slothfully simple.

Servers, Docker, Kubernetes, databases, workflows, model serving, data services, tracking, and monitoring, with your product at the center. Managed in one place and connected by design.

What is MLOX?

ML/AI infrastructure is fragmented. Setup is painful, managed platforms are expensive, and vendor lock-in limits your choices.

MLOX brings the infrastructure around your product into one connected system. It manages servers, sets up Docker and Kubernetes clusters, deploys open-source services, stores secrets, and wires dependencies across databases, workflows, experiment tracking, model serving, data services, and monitoring.

Use the CLI or TUI to operate the same inspectable, configuration-driven core. MLOX is built for solopreneurs, startups, and small teams that want to focus on their product instead of assembling and maintaining infrastructure.

It's for engineers who prefer thoughtful systems over chaos. Backed by open source. Powered by sloths.

Status, roadmap, and decisions — see docs/DOCTRINE.md, the single point of truth.

Current Status

Native, Docker, and Kubernetes execution, connector integrations, and the major services are functional. The project has been accepted at CAIN 2026.

We welcome contributors, users, and honest feedback. If you hit something broken, please open an issue or reach out at contact@mlox.org.

What Can You Do with MLOX?

Services Catalog

MLOX bundles a growing set of self-hosted services and connectors (MLflow, Airflow, Milvus, Feast, Kafka, LiteLLM, OpenBao, GCP, and more). The exhaustive, authoritative list — generated directly from the YAML plugin configs — lives in docs/SERVICES_CATALOG.md. Per-component maturity status is tracked in docs/DOCTRINE.md.

Architecture in 30 Seconds

CLI     TUI
  \      |
   +-----+
          |
          v
      `ProjectWorkspace`
          |
          v
   internal state + repository
          |
          v
 encrypted `project.mlox` (SQLCipher)
 metadata + data-source pointer + infrastructure + secrets
          |
          +-- active source: `self` today
          +-- PostgreSQL-ready repository boundary later

ProjectWorkspace is the single public runtime API. It loads and atomically persists internal workspace state containing metadata and Infrastructure; the single selected secret manager is available through workspace.secrets. Encrypted project storage is selected initially, with no silent fallback when an external provider is unavailable. The project also records its active data source (sqlcipher/self initially), leaving a clean migration path to PostgreSQL. CLI commands open a workspace per invocation, while the TUI retains one workspace in runtime state. (The Streamlit web UI is deprecated — see docs/DOCTRINE.md.)

Service and server definitions remain inspectable and configuration-driven, while execution is handled consistently across Native, Docker, Kubernetes, and connector backends.

For deeper reading:

• Architecture Guide — codebase walkthrough
• Python API — supported workspace SDK contract

Quickstart

# 1. Install uv (https://docs.astral.sh/uv/)

# 2. Install MLOX with the terminal UI included
uv tool install 'busysloths-mlox[tui]'

# 3. Launch the TUI and hit the "Create" button on the login screen
#    to make your first encrypted, portable project file
mlox tui

# ... or explore the CLI
mlox --help

See Installation Guide for a fuller walkthrough including Docker and Kubernetes setup. See Encrypted Project Files for creation, storage, backup, and legacy migration details.

Project Structure

mlox/
├── mlox/
│   ├── application/    # Stateful application API and shared use cases
│   ├── cli/            # Typer CLI package (root app + command modules)
│   ├── execution/      # Backend and system execution helpers
│   ├── project/        # Aggregate, SQLCipher repository, and secret adapter
│   ├── servers/        # Local, connector, and Ubuntu compute with Native, Docker, or Kubernetes
│   ├── services/       # Deployable ML/AI services and integrations
│   ├── tui/            # Textual terminal UI + TUI-specific UI handlers
│   ├── ui/             # Frontend UI handler registry
│   ├── assets/         # Runtime templates and packaged assets
│   ├── resources/      # Images and other static resources
│   ├── view/           # Streamlit web UI — deprecated (moving to plugin repo)
│   ├── infra.py        # Service/server graph
│   ├── config.py       # YAML loading + plugin discovery + UI handler lookup
│   └── executors.py    # Remote task executor layer used by services/servers
├── tests/
│   ├── unit/           # Fast tests, no external deps
│   └── integration/    # Multipass VM tests, including Kubernetes/k3s tests
├── examples/           # OTel, MLflow tracking, DAG templates
├── docs/               # Architecture, installation, contribution guides
├── wiki/               # GitHub Wiki source pages
├── scripts/            # Development and maintenance utilities
└── website/            # Astro landing page

Contributing

Sloth-Friendly Setup

# 1. Install Task (https://taskfile.dev/installation/)
# 2. Clone the repo
git clone https://github.com/BusySloths/mlox.git && cd mlox
# 3. Set up the dev environment (uv-based, installs the package with dev extras)
task first:steps

Run Tests

task dev:lint                   # flake8
task tests:unit:run             # unit tests (fast, no external deps)
task tests:integration:run      # integration tests (requires Multipass VMs)
task tests:integration:k8s      # Kubernetes integration tests (requires Multipass/k3s)

Ways to Contribute

• Bug reports
• Documentation improvements
• Feature requests
• New service implementations
• Examples and tutorials

See CONTRIBUTING.md for the issue, milestone, and PR workflow.

Documentation

Sponsors

MLOX is proudly funded by:

Supporters

License & Contact

MLOX is open-source, distributed under the MIT License. Contributions are welcome and subject to the same terms.

We are looking for people invested in the problem we're solving. Say hello at contact@mlox.org or start a conversation in GitHub Discussions.