A calm email client for mail you host yourself.
Imbox reads your Gmail, your Outlook and any other mailbox, and puts all of it behind one quiet screen. New senders wait for your yes or no before they reach you. People come first. Newsletters and receipts stay out of the way. An optional AI assistant helps when you ask it to, and never sends anything without you.
You run it yourself, on a small Linux server. It has one owner, a black-and-white design, and a separate layout for phones that you add to your home screen.
The Imbox, where mail from people lands, with what is waiting for your reply at the top:
Your mail, sorted by who it is from
- The Screener. The first time someone writes to you, they wait in the Screener. You choose once where their mail goes, and the choice applies to every account you have connected.
- Two places. The Imbox holds mail from people. Updates holds newsletters, long reads, receipts and confirmations.
- Working through mail. Reply Later and Set Aside keep things you are not ready to answer. Bubble Up brings a thread back at a time you pick. Bundles fold a busy sender into one row.
- One inbox for every account. The composer has a From picker, with the addresses grouped by domain.
- Away mode. Set a return date and mail waits quietly. Imbox can send a short notice that you approve first.
Finding things
- Search matches every word you type, in any order, and puts the best match first. Each result says where the words were found. You can narrow it with
from:,to:,has:attachment,in:feed,is:unread,before:,after:andfilename:. - Contacts. Each person has a page with what is waiting on you, what you are waiting on, a chart of messages over time, and the files you have exchanged.
- Files. Every attachment in one place, with a first-page preview for PDFs.
Privacy
- Tracking pixels are removed when mail arrives. Other remote images stay hidden until you show them.
- Very little leaves your server. Two things happen on their own, a check for new versions and the pictures of people who write to you, and each has a switch in Settings. Everything else needs a feature you turn on. The
/privacypage of your own install lists every outside address it can contact.
Calendar
- Weeks, days and a year view. Google Calendar (two ways), subscribed
.icsfeeds, and a calendar for each mailbox that fills from email invitations.
AI, only when you ask
- An assistant at the bottom of every page (
Cmd+J) that can search and read your mail and write drafts in your tone. - A daily brief, summaries of long threads, and suggestions in the Screener.
- Bring your own model: Anthropic, OpenAI, xAI, OpenRouter, Gemini, or any OpenAI-compatible server.
- Agents that handle a mailbox for you, with strict limits. Mailboxes for outside AI agents, with their own API keys and webhooks.
Your own mail server
- Connect a Stalwart server and manage its domains and mailboxes from Imbox.
It runs on one Linux machine, or anywhere that runs containers: Node.js and PostgreSQL, with Caddy in front for HTTPS. About 2 CPUs and 4 GB of memory is enough to start. The Self-hosting guide covers a server, and Docker is below.
The short version for your own server, on a fresh Debian or Ubuntu machine with a domain name pointing at it:
sudo IMBOX_DOMAIN=imbox.example.com bash deploy/setup.sh # on the server: installs everything
bash deploy/deploy.sh user@imbox.example.com ~/.ssh/key # on your computer: builds and shipsThe one-line way, on a fresh Debian or Ubuntu server (x86_64) with ports 80 and 443 free. It installs Docker if needed, and sets up Imbox, PostgreSQL and Caddy with automatic HTTPS:
curl -fsSL https://imbox.lol/install.sh | sudo bashWith no domain it uses <your IP>.sslip.io, which gets a real certificate without any DNS setup. For your own domain, point its DNS at the server and add IMBOX_DOMAIN=mail.example.com after sudo. Run it again to update. Read the script first if you like; its header lists every option, and IMBOX_DRY_RUN=1 shows what it would do without doing it. The image it pulls is fr3on/imbox on Docker Hub, so that repository has to be public for other people's servers.
Or with Docker, anywhere that runs containers:
cp .env.example .env # set POSTGRES_PASSWORD, APP_URL and SESSION_SECRET
docker compose up -d # Imbox on 127.0.0.1:8787, with its own PostgreSQLdocker-compose.yml pulls the image from ghcr.io. The same image is published on Docker Hub as fr3on/imbox (tags latest and <short commit>). To run that one, change image: in docker-compose.yml to fr3on/imbox:latest, or use the build: . line next to it to build from this checkout. The text for the Docker Hub page is in docs/dockerhub.md (a full compose file, the settings, and how to update); it is pasted into Docker Hub by hand.
Open your address, create the owner login, then add a mailbox.
Imbox is developed on both GitHub (fr3on/imbox) and GitLab, and the same checks run on either, so a fork works on both with no setup.
- GitHub:
.github/workflows/has the pull request checks (ci.yml), the release, Docker image and desktop builds. Pull requests use the issue and pull request templates in.github/. - GitLab:
.gitlab-ci.ymlruns the same checks on every branch and merge request: the type check and the linter, the tests as parallel shards (each with its own PostgreSQL), and the self-hosted build with its end-to-end tests. Templates are in.gitlab/. - Maintainer-only jobs: the image build, the Docker Hub publish and the deploy jobs in
.gitlab-ci.ymlonly exist on the maintainer's own GitLab server (CI_SERVER_HOST), so a fork's pipeline runs the tests and nothing that needs a private registry or server. On that server, the Docker Hub publish and the productiondeployare manual buttons; the Devtron hand-off runs by itself onmain.
| Read this | To |
|---|---|
| Getting started | Install Imbox and connect your first mailbox |
| Self-hosting | Set up a production server, Docker, backups, and restore |
| Updating | Update, run migrations, and roll back |
| Configuration | Every environment variable and setting, in one place |
| Mailboxes | Connect Gmail, Outlook, IMAP and domain mailboxes |
| Stalwart | Run a mail server from the app |
| Browser extension | Screener count on toolbar, quick triage, side panel, and notifications |
| Desktop app | Native desktop shell for macOS, Windows, and Linux |
| Calendar | Continuous calendar, Google sync, and RSVPs |
| AI | The assistant, providers, memory, agents, privacy |
| Agent mail | Mailboxes and an API for outside AI agents |
| API | How the app and clients talk to the backend server |
| Development | Run it locally, architecture, and tests |
| Design | The look and the rules behind it |
| Security | Threat model, protection, and vulnerability reporting |
Bug reports, fixes and ideas are welcome. CONTRIBUTING.md takes you from a clone to a merge request, and the Code of Conduct applies to everyone. For a security problem, see SECURITY.md.
Hono on Node.js with PostgreSQL. React 19, Vite, Tailwind v4 and shadcn/ui. Mail comes in over IMAP, through the Gmail and Microsoft Graph APIs, or, for a Stalwart server you run, straight from it.
MIT. See LICENSE. Imbox is an independent project, not affiliated with HEY, Basecamp or 37signals; see NOTICE.
