Internal utility runner
Pulsar with Ollama
Use an optional CPU-friendly Ollama service for internal titles, summaries, prompt optimization, scheduler summaries, and diagnostics.
Key considerations
Internal only
The utility model is not shown as a user chat choice.
CPU-friendly role
Move lightweight support work away from the primary chat runner.
Optional service
Deploy the utility profile only when the environment requires it.
Architecture at a glance
Separate utility work from user inference
Titles, summaries, prompt optimization, scheduler summaries, and administrative diagnostics do not always need the same GPU model used for interactive chat.
Keep the model out of the user picker
The Ollama utility service is configured as an internal dependency. Product workflows call it for approved support tasks without presenting it as a general chat model.
Recommendations are not arbitrary recovery
Utility output may support diagnostics and safe self-healing recommendations, but infrastructure changes remain predefined, policy-owned, and operator-visible.
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.