Organizes your inbox, pre-drafts replies, and tracks follow‑ups - so you reach inbox zero faster. Open source alternative to Fyxer, but more customisable and secure.
Website
·
Discord
·
Issues
To help you spend less time in your inbox, so you can focus on what matters most.
- AI Personal Assistant: Organizes your inbox and pre-drafts replies in your tone and style.
- Cursor Rules for email: Explain in plain English how your AI should handle your inbox.
- Reply Zero: Track emails to reply to and those awaiting responses.
- Bulk Unsubscriber: One-click unsubscribe and archive emails you never read.
- Bulk Archiver: Clean up your inbox by bulk archiving old emails.
- Cold Email Blocker: Auto‑block cold emails.
- Email Analytics: Track your activity and trends over time.
- Meeting Briefs: Get personalized briefings before every meeting, pulling context from your email and calendar.
- Smart Filing: Automatically save email attachments to Google Drive or OneDrive.
Learn more in our docs.
![]() |
![]() |
|---|---|
| AI Assistant | Reply Zero |
![]() |
![]() |
| Gmail client | Bulk Unsubscriber |
To request a feature open a GitHub issue, or join our Discord.
We offer a hosted version of Inbox Zero at getinboxzero.com.
The fastest way to self-host Inbox Zero is with the CLI:
npx @inbox-zero/cli setup # One-time setup wizard
npx @inbox-zero/cli start # Start containersFor complete self-hosting instructions, production deployment, OAuth setup, and configuration options, see our Self-Hosting Docs.
git clone https://github.com/elie222/inbox-zero.git
cd inbox-zero
docker compose -f docker-compose.dev.yml up -d # Postgres + Redis
pnpm install
npm run setup # Interactive env setup
cd apps/web && pnpm prisma migrate dev && cd ../..
pnpm devSee the Contributing Guide for more details including devcontainer setup.
View open tasks in GitHub Issues and join our Discord to discuss what's being worked on.
Docker images are automatically built on every push to main and tagged with the commit SHA (e.g., elie222/inbox-zero:abc1234). The latest tag always points to the most recent main build. Formal releases use version tags (e.g., v2.26.0).




