Your mail, on your terms, for your whole team
OneMail gives a team one client for every mailbox it already has, and gives your administrators the controls they expect: single sign-on, directory provisioning, roles and rules.
01
SAML single sign-on
Sign in through Okta, Entra ID or Google Workspace. The identity provider is registered for your organisation, and the sign-in button appears in the app.
02
SCIM provisioning
Create and deactivate accounts from your directory. Deprovisioning revokes the person's sessions and blocks them from signing back in.
03
Roles that mean something
Owner, admin and member. Admins see the organisation's rules and analytics, manage members, and own the billing; members see their own mail.
04
Rules for the whole team
An organisation rule is written once and reaches every member, so the team files mail the same way without anyone copying a rule by hand.
05
An API and an MCP server
A versioned REST API with scoped keys, and an MCP server that lets your own agents browse the mailbox and act on it. Both are switches you turn on per deployment.
06
Run it yourself
Docker Compose, Kubernetes with the bundled Helm chart, or AWS with Copilot, ECS or a generated Terraform configuration.
Where your data sits
In a self-hosted deployment the mail itself, the credentials and the local index stay in your infrastructure. What leaves is what you send it to: the model provider you configure for the assistant, the mail server that holds the mailbox, and whatever you connect with Slack, Telegram or the API.
Free to run · SSO, SCIM and the API are deployment switches