Audience 01
AI engineers
Uses the product where the cost of an unscoped action is higher than the cost of setup.
Workspace & infrastructure · Concept
Where the work actually changes.
LocalModels is aimed at AI engineers, developers, enterprise platform teams.
01
Who it is for
Three audiences, one boundary model.
Audience 02
developers
Needs the same permission model for people and agents.
Audience 03
enterprise platform teams
Adopts it to replace a patchwork of tools with one reviewable surface.
02
Use cases
Each row maps a capability to the operational change it is meant to produce.
| Capability | Operational change | Status |
|---|---|---|
| Model catalog and compatibility discovery | Makes an existing action reviewable. | Specified |
| Quantization and device-aware deployment | Removes an ad hoc step from the workflow. | Specified |
| Inference endpoint management | Turns a manual control into an explicit contract. | Specified |
| Evaluation and routing | Makes an existing action reviewable. | Specified |
| SDK, API, MCP and CLI access | Makes an existing action reviewable. | Specified |
03
Migration
How a team would move from the status quo without a big-bang cutover.
Step 01
Map the current path
Name the tools, owners and handoffs that the product replaces. Nothing is removed yet.
Step 02
Run one capability
Pick a single scoped capability and run it alongside the old path, with evidence compared side by side.
Step 03
Retire the old path
Remove the previous tool only when the new record is complete enough to audit.