The desktop for mail and governed AI
Your inbox tells you what arrived. OneDesk tells you what matters. A native desktop for mail, calendar, contacts and tasks, with AI that never grants itself authority.
exampleSummarise today’s mail→native records on this device· not passed to the model
native desktop · no OneDesk server
Security-kernel checks between content and a model. The first refusal wins.
Review and send, then Confirm send, before any message leaves.
Master key in the operating-system credential store. Every other secret sits in an encrypted vault.
OneDesk servers between your device and your mail provider.
Properties of OneDesk’s design, not performance measurements. Response times depend on your mail provider and the model you configure.
Commitments begin in email, decisions get buried there, customer requests arrive there, and operational risk quietly accumulates. Conventional mail clients organise messages. They do not reliably show ownership, urgency, dependencies or policy.
Mailbox content does not become model input just because an account is connected. Chat answers from native records on the device, and model inference over connected mail content stays off until the required security analyses are in place.
On the device, encrypted. The operating-system credential store holds one master key; every other secret, including mail tokens and model keys, sits in an encrypted vault under it.
A person, every time. AI prepares drafts; sending is a two-step confirmation, and a device-wide kill switch stops every AI path at once.
| Capability | Desktop mail clients | AI assistants for mail |  |
|---|---|---|---|
| Mail, calendar, contacts and tasks in one native desktop | ✓ | varies | ✓ |
| AI summaries and exact reply drafts | varies | ✓ | ✓ |
| Every send confirmed in two steps, including drafts that AI prepared | varies | varies | ✓ |
| One kernel decides what may reach a model, and its default answer is no | — | varies | ✓ |
| Your choice of model, including local Ollama or LM Studio | — | varies | ✓ |
| A device-wide AI kill switch | — | varies | ✓ |
| No vendor server between your device and your mailbox | varies | varies | ✓ |
Category comparison, not a claim about any specific product. “Varies” means some products in the category offer it.
OneDesk is a Tauri 2 and Rust desktop application with a React renderer. Mail flows between the device and your own provider without passing through an Onega server.
Mail, Chat, Cases and Radar are different views of the same communication context, not separate products.
Hello, the revised terms are attached. Could you confirm them by Friday?
Chat answers questions about your mail, calendar and tasks from native records on the device. Those records are not silently passed to the language model.
Example conversation.
Designed to turn messages into owned work with status, priority, SLA, evidence and resolution history.
Built for shared inboxes and service teams.
Designed to show demand, flow, risk, capacity, approvals and cost before service fails.
Built for team leads who own queues, SLA accountability and workforce planning.
example · service desk
Calendar, contacts and tasks are tied to the account. The calendar refreshes every two minutes while it is open; calendars and contacts refresh in the background every fifteen minutes while OneDesk runs.
Generic IMAP has no standard task protocol, so Tasks show as unavailable rather than pretending to be connected.
There is no OneDesk administrator login and there are no default credentials.
One place decides whether content may reach a model, and its default answer is no. People keep the last word on everything that leaves.
The first refusal wins. A probabilistic detector can restrict content but can never clear it. An operator can open Kernel posture to see the tiers, which analyses are provisioned and why recent decisions were refused.
exampleSummarise connected mail with the model→refused at tier 05· required analyses not provisioned
The kill switch is the first item in OneDesk’s persistent footer. OneDesk writes the stop to the operating-system secure store, then refuses every new inference and cancels local requests already running. To restart, you complete a separate review and type ALLOW AI FEATURES; stopped work is never replayed.
AI features runningAll AI stopped on this device. Restarting needs a separate review.
Demonstration control. It does not contact a device.
Translation is the one path by which mail content can reach a model. OneDesk builds a plain-text extract, removes protected values and URLs, runs the checks for that extract and binds a receipt to the single request.
Chat never sends. A request that says “send” still produces a draft.
Model inference over connected mail content and autonomous replies stay switched off until the required malware, data-loss, prompt-injection, URL and attachment analyses are provisioned. Translation is the one narrow exception: a checked plain-text extract bound to a receipt for that request.
Profile, account and scheduling state is encrypted at rest. The operating-system credential store holds one master key, and every other secret sits in a vault under it.
The operating-system credential store holds exactly one OneDesk item: a random 32-byte master key created on first launch. Every other secret lives in an encrypted vault under it; a copy of the vault file on its own is ciphertext.
Profile, account and scheduling state lives in SQLCipher-encrypted databases, including the write-ahead log and journal. A missing or locked key never opens an unencrypted database.
OneDesk runs. Secrets stay encrypted under the master key.OneDesk refuses to run rather than store secrets in plain text.
Demonstration control. It does not contact a device.
Removing an account deletes its credential and OneDesk metadata from the device. It does not delete mail held by the provider or revoke organisation-wide consent.
Your mail, calendar and contact providers and the model endpoint you configure. During account setup only, public configuration records for the mailbox domain; only the domain is sent.
The React interface runs under a strict content-security policy, and mail is shown as safe text.
Microsoft and Google sign-in opens in the system browser with the address prefilled. OneDesk never asks for those passwords.
Choose a provider, then Verify and connect, fetch the available models and choose one. The key goes straight from the native process to the verified endpoint, is never shown again and stays out of logs, browser storage and ordinary settings files.
OneDesk’s OpenAI-compatible gateway connection is designed to let an organisation route every model call through OneVeer, so one policy, one redaction layer and one audit trail can cover the whole stack. The pairing is scoped and demonstrated per engagement; it is not pre-wired. About OneVeer
OneDesk installs per user on each desktop. Consent, credentials and network destinations are known before a pilot starts.
OneDesk asks for delegated permissions only. ProfilePhoto.Read.All requires administrator consent.
# Microsoft 365 · delegated permissions User.Read Mail.ReadWrite Mail.Send Calendars.ReadWrite Contacts.ReadWrite Tasks.ReadWrite offline_access ProfilePhoto.Read.All # administrator consent
A native desktop application, installed per user. There is no server, database or container to run for OneDesk itself.
Built for Windows, macOS and supported Linux; the versions and architectures for your pilot are agreed during scoping.
Mail, calendar, contacts and tasks access are requested together. Workspace administrators may block third-party apps.
The operating-system credential store must be available and unlocked. If it is not, OneDesk refuses to run rather than store secrets in plain text.
Short answers to the questions evaluators ask first.
Not because an account is connected. Chat answers questions about mail, calendar and tasks from native records on the device and does not silently pass them to the model. Model inference over connected mail content stays switched off until the required security analyses are in place; the one exception is translation of a checked plain-text extract, bound to a receipt for that single request. General questions you type into Chat can go to the model you configured.
OneDesk has no backend service. Its state sits in encrypted SQLCipher databases on the device, with no plaintext fallback. Secrets sit in an encrypted vault whose single master key is held by the operating-system credential store. Mail stays with your provider.
No. Chat prepares drafts; even a request that says send produces a draft. Sending needs a person to choose Review and send and then Confirm send. Autonomous replies fail closed.
Use the kill switch in the persistent footer. It stops every AI execution path on that device and survives restarts and profile restores.
Connection types include direct providers; Azure OpenAI and Foundry, Amazon Bedrock and Google Vertex AI; OpenRouter or any OpenAI-compatible gateway; and local Ollama or LM Studio, which need no key on the local machine. A custom gateway must use HTTPS unless it runs on the same machine. OneDesk is designed to route through OneVeer when inference must stay on your hardware; that pairing is scoped per engagement.
Your mail, calendar and contact providers; the model endpoint you configure; and, during account setup only, public configuration records for the mailbox domain: DNS, the Thunderbird autoconfig service and the domain's own autoconfig host, with Cloudflare DNS-over-HTTPS as a fallback. Only the domain is sent.
OneDesk holds no certifications, and we do not claim GDPR or AI Act compliance as a product property. We document the data flow and sign a data-processing agreement for each deployment. Report suspected vulnerabilities to support@onega.dev with Security in the subject line. There is no bug bounty.
OneDesk is licensed together with a pilot delivered by Onega Forward, our forward-deployed engineering team.
A workflow map and measured baseline, a data-flow map, a risk register with the EU AI Act classification, acceptance criteria and a fixed-price pilot proposal. You may stop at that point.
One workflow, one team and one integration, evaluated on a holdout sample, followed by supervised operation and a handover pack.
AI inside your walls.
See OneDesk with your own mailboxes, your model provider and your tenant’s consent policy.
Email sales@onega.dev for a pilot or licensing. Product questions: help@onega.dev. Security questions: support@onega.dev.
© 2026 Onega. OneVeer, OneDesk and OneMail are proprietary software. Service provider: Onega, Essen, Germany.
