Local model runner
Pulsar with LM Studio
Connect an LM Studio OpenAI-compatible endpoint for local labs, evaluation environments, smaller deployments, and model testing.
Key considerations
Evaluation friendly
Use locally managed models without changing the Pulsar workspace.
OpenAI-compatible
Configure the endpoint and model through the supported runner path.
Operator verified
The installer and admin workflows probe reachability and model availability.
Architecture at a glance
A practical path for labs and smaller environments
LM Studio is useful when teams need local model testing or a smaller private runner without operating the same production GPU serving stack used by vLLM.
The workspace remains consistent
Chat, tools, scheduler, library, and governance do not need a separate product experience. Operators change the approved runner endpoint and model while the user workflow remains Pulsar.
Understand the operating tradeoff
Capacity, process lifecycle, remote reachability, and hardware behavior remain responsibilities of the team operating the LM Studio host. Production requirements should be reviewed before promoting a lab endpoint.
Private deployment consultation
Review Pulsar against your environment.
Bring the infrastructure, security boundaries, model runners, and use cases. The Pulsar team will map the appropriate deployment path.