The fastest path from SDK install to shipped local AI
Start with native SDKs, keep inference in your app process, and use CLI or REST tools only when they help your development workflow.
One SDK lifecycle
Initialize the manager, choose a model alias, download and cache it, load it, then call chat or audio clients from your app.
Hardware handled for you
The SDK picks and registers execution providers so apps can target NPU, GPU, or CPU without custom device plumbing.
Offline app runtime
The runtime and cached models stay local so user workflows keep running without a network.
Native SDKs
Start in Python or JavaScript; ship production apps in C# and Rust too.
Native first, REST when needed
Use SDK clients in-process, or start the optional OpenAI-compatible server for frameworks like LangChain.
Data Privacy
Prompts, audio, and responses stay on the user's device.