Bring your own API key when local is not enough.
Some tasks need a provider model. BYOK makes sense when the user wants to choose the provider and pay through their own account instead of using a company-hosted middle layer.
At a glance
Phos is a BYOK AI app for Android that lets users bring provider keys while keeping local and local-server modes available.
How Phos handles it
Three clear routes
Local model
Local model mode remains the private default for prompts that should stay on the phone.
Local server
Local server mode gives a self-hosted alternative for stronger models on your own machine.
Bring your own key
BYOK mode sends prompts to the provider behind your key. Phos stores the key locally and does not sell hosted inference.
Who this is for
Built for people with real private work to do.
Users with Gemini, OpenRouter, Groq, or OpenAI-compatible keys.
Developers who want provider flexibility on Android.
Privacy-minded users who still need an online fallback sometimes.
Plain comparison
The point is control, not a louder chatbot.
These pages are for people comparing real options. Phos should win when someone wants privacy, local control, no account wall, and an assistant that still feels good to use.
| Feature | Phos | Typical cloud chatbot | Raw local app |
|---|---|---|---|
| No login | Yes. Open the app and start. | Usually requires an account. | Often yes, but setup can be technical. |
| Local mode | Yes. Supported through local model paths. | No. Prompts go to the platform. | Yes, if the model loads on the device. |
| Own API key | Yes. Use your provider key when you choose. | Usually no. | Sometimes. |
| Memory control | User controlled memory with delete, export, and reset paths. | Platform controlled or account tied. | Varies. |
| Everyday workflows | Think through, draft message, study, and plan day. | General chat first. | Usually just a model prompt box. |
The honest BYOK privacy model
BYOK is not a privacy force field. It avoids Phos-hosted inference and gives provider choice, but the selected provider still sees the request.
When BYOK is useful
Use BYOK for tasks where model quality matters more than full local execution: long reasoning, specific provider features, multimodal support, or models not practical on the phone.
Why people remember Phos after trying it
Phos is not only a privacy checklist. The first-use loop is designed to feel calm: open the app, choose a way to think, let the mascot help with local setup when needed, and keep memory under your control. That product feel is the part a comparison table usually misses.