Overview

Model Lab is the model operations surface inside the Allternit platform shell. It brings together local inference, fine-tuning, model discovery, and cloud deployment so teams can work with open-weights models without leaving the Allternit workspace. The surface is built around a tabbed view that polls the underlying services every few seconds while it is open, keeping runtime status, job progress, and telemetry live.

Base URL / usage

Model Lab runs inside the platform shell:
Open programmatically from shell code:
The underlying APIs are served from the Allternit gateway:

Features

Engine

Inspect telemetry, manage cached models, launch inference runtimes, and run export/merge/evaluation jobs against the Local Engine controller.

Catalog

Browse Unsloth guides and search the Hugging Face model catalog with hardware-fit estimates.

Train

Fine-tune, export, merge, and evaluate open-weights models using job templates and a live job monitor.

Studio

Connect to a Local Studio controller, view GPUs and usage, and manage serving recipes.

Cloud Deploy

Register and test serverless endpoints for trained models.

Playground

Chat with any running local runtime through a streaming chat interface.

Tabs

Key concepts

Local Engine

The Allternit Local Engine is the controller that owns cached models and inference runtimes on the host. Model Lab’s Engine tab is a visual wrapper around its health, model cache, and runtime lifecycle APIs.

Cached models

A model tracked by the Local Engine has a source such as local_path, hugging_face, or unsloth_output, plus a filesystem path and a status like ready, downloading, or failed.

Runtime recipes

A recipe tells the Local Engine which backend to use and how to launch it. Supported backends:

Model Lab jobs

Long-running work is submitted as jobs. Job types map to the operations you can queue from the Engine and Train tabs:

Brain registration

The Engine tab can register the Local Engine or a local sidecar as a brain provider. Once registered, the models served by that runtime appear in the platform’s model picker and chat composer.

Local Studio

Local Studio is a separate controller for advanced local serving. The Studio tab connects to it, lists detected GPUs, tracks usage, exposes logs, and lets you author and save serving recipes.

Cloud endpoints

The Cloud tab stores endpoint credentials locally in the browser and runs a lightweight reachability test against /v1/models or /models. It is a registry for models you have already deployed elsewhere.

Endpoints / commands

Model Lab jobs

Local Engine

Local Studio

JSON request / response examples

Create a training job

Response:

Launch a local runtime

Response:

Chat with a running runtime

Stream chunk:

Error codes