Desktop-first
Local where it counts — central where it helps.
CompanyWizard comes as a web interface and as a desktop app. For most cases we recommend the desktop client: it keeps data local on your own machine yet stays fully connected to the central team features. The web stays the right choice when location-independent access or round-the-clock automation matter most.
The browser is convenient — but it moves everything to a server
Many LLM chats run in the browser today. That is convenient, but it shifts data, access and processing onto a server. For a tool that works with company knowledge, that is not always what you want.
The usual alternative — everything local — tends to cost the team connection. CompanyWizard offers both routes and resolves exactly this trade-off.
Data sovereignty without giving up the centre
With the desktop app, data can stay fully local, including local indexing via a built-in SQLite-Vec database. Local data does not mean giving up shared work: through shared vaults, LDAP sign-in and messaging you keep using the central features.
On top comes local flexibility with tools: over the stdio transport you embed MCP servers as a local process — your own Python or Node scripts that a pure web interface cannot reach. OAuth tokens and access live locally and are not visible to others.
What the desktop client keeps local
-
Data & index
Documents and the vector index stay on your own machine — the content does not leave it.
-
Local tools (beta)
MCP servers over the stdio transport: your own scripts and tools as a local process.
-
Private access
OAuth tokens and connected MCPs live locally, not visible to others.
-
Statistics & messages
Usage statistics and chat/messaging messages in a local SQLite database.
-
Sign-in without a server
An OTP fallback allows local sign-in even when the server API is momentarily unreachable.
Web interface or desktop app?
| Criterion | Web interface | Desktop app |
|---|---|---|
| Installation | None, just a browser | One-time install per machine |
| Access | From anywhere, mobile too | Bound to your own machine |
| Data storage | On the server | Fully local possible |
| Local tools (stdio MCP, beta) | Not possible | With a local Python/Node environment |
| OAuth tokens & MCP access | Server-side | Local, not visible to others |
| Sign-in on server outage | Not possible | OTP fallback, local |
| Background automation | Stronger (server-side) | Only while the app is open |
What this means for you
- Full local data sovereignty — while staying connected to shared vaults, LDAP and messaging.
- Local stdio MCPs (beta) open up your own tool landscape, which the web cannot reach.
- Private access: your connections to third-party systems do not travel over a shared server.
- You stay productive offline or when the central infrastructure is down.
Honestly: when the web is the better choice
-
Location-independent access without installation.
If you work from changing devices, on the go, or without a local install, the browser serves you better. The desktop client is bound to the machine it runs on.
-
A low barrier to entry.
For less technical users the web is the simpler start. Local MCPs with your own Python/Node environment are an advantage for power users, not a must for everyone.
-
Round-the-clock automation.
Scheduled agents in desktop mode only run while the app is open. For automation around the clock, the server-hosted web mode is the better fit.
-
Central maintenance.
Updates and configuration can be rolled out centrally on the web. The desktop client is installed and updated per machine.
Sounds right for your organisation?
In a 30-minute demo we show the concept on your concrete use case — no obligation, with concrete suggestions at the end.