Jan

Jan provides a desktop interface for running language models locally and working with them through conversations. Its broader ecosystem includes model connections, a local API server, and agent tooling. The local workflow is useful for users who want to choose their model and keep inference on their own machine, while cloud connections remain a separate option.

Features and what they are useful for

• Download and manage supported local models through the desktop workflow.
• Chat with a selected model and organize instructions or files through the supported workspace features.
• Expose a local compatible API for applications that need to call the model.
• Connect documented providers or tools when a task requires cloud inference or capabilities beyond local text generation.

Who it suits

Jan suits technically curious users, developers, and people evaluating local AI for everyday work. It is particularly useful when a graphical interface makes model selection easier than managing a command-line server alone. Users should distinguish Jan Desktop from the separately documented Jan Agent and choose the component that fits the intended task.

A practical workflow

Download a model that fits your machine and test a short document-summary request. Check speed, memory use, and the quality of the response before moving to a larger model. If a local application needs inference, enable the documented local API and test a simple request. Keep cloud providers disabled for a workflow intended to remain local, and verify where any connected tool sends its data.

Limitations and things to check

Local inference depends on available memory, model size, architecture, and supported hardware. A smaller model may be convenient but less capable for complex reasoning or tool use. Local execution also does not make every connected workflow private: remote providers and external tools can process data elsewhere. Review the selected model's license and each connection rather than treating the desktop application's open-source status as a universal deployment guarantee.

Pricing and access

Jan's desktop software is available through its official downloads and documentation. Running local models uses your own hardware and storage, while external provider connections may introduce separate usage charges. Check the current installation requirements, model support, and component documentation before building a workflow around a particular API or agent capability.

Frequently asked questions

Can I use Jan without a cloud API key?

Supported local models can run on your machine without a cloud provider key.

Is Jan Agent the same as Jan Desktop?

The official documentation distinguishes the desktop workspace from separately distributed agent tooling.

Official sources

Jan official website · Official product guide