Skip to content

Platform availability

Pyre shares the same core library across Android, desktop, web/PWA, and self-hosted hubs, but not every platform has the same provider, browser, or hosting responsibilities.

Feature area Android Windows Linux Web/PWA
Chat, characters, personas, presets, lorebooks, memory, Creator Yes Yes Yes Yes, via hub
Group chat, Party Mode, persona party, Guide, regex rules Yes Yes Yes Yes
BYOK direct provider connection Yes Yes Yes No, uses hub proxy
Anthropic-native direct API Yes Yes Yes No
Provider management, model browsing, smart fallback Yes Yes Yes Hub/server side only
OS-secure key storage Android Keystore Credential Manager Secret Service Browser stores no keys
Discover / BotBooru Embedded in-app browser Embedded WebView2 External browser Embedded via hub proxy; external standalone
BotBooru lorebook Download JSON import Yes Yes Via file/URL after external download Yes via hub proxy
Generation keep-alive Foreground service No No No
Tray, window persistence, single-instance, toasts, shortcuts No Yes Yes No
LAN/web hub No Yes Yes No
Self-host hub No Desktop hub / experimental headless source path Experimental Docker/source path Connects to it
Sync client Yes Yes Yes Yes
QR pairing Scan Show Show Request desktop allow / token
Provider key sync Opt-in encrypted Opt-in encrypted Opt-in encrypted Excluded
LLM debug log viewer Yes Yes Yes No
Installable PWA No No No Yes

Note

Web/PWA is a zero-secret surface. It gets the synced library and can chat through the hub, but the API key and direct provider controls stay on the native or self-host side.

See also